Geoscience Reference
In-Depth Information
In order to solve most of the problems related to the use case scenario
listed above, we propose a fully interoperable system with the following
components:
•
Subsystem for Location Integration: using specified algorithms for geo-
graphic and place names' integration such as Euclidian and Levenshtein
distances and a semantic ontology reasoner via Protégé for their seman-
tic details integration.
•
Subsystem for Cartographic Integration: using a new type of geo-
ontology, named CartOntology, for formalizing explicit knowledge
about our domain of interest (touristic points of interests POI) and
adjusting the map conflation, semantically and visually, based on the
user profile's ontology, his geographic zone or context information and
the graphical semiology constraints.
This paper is structured as follows: Section 2 provides a description of the
problems being raised from the use case scenario. Section 3 presents an
overview of the related works. In Section 4, we discuss and evaluate our
contribution. Section 5 details all the implemented solutions for location
and cartographic integrations. Section 6 concludes the work with some
perspectives.
2- Our Case Study-Limitations
When a person is moving in an unknown area and making a search, only
maps can provide desired information in a precise and concise way.
Google Maps, Bing, Via Michelin, Mappy, OpenStreet-Map, and many
others are cartographic publishers trying to visualize the geographic infor-
mation on 2D/3D base-maps. However, most of them are still retrieving
data from one single GDB. What if this GDB is not updating its informa-
tion very often (Google street view case) or had been hacked and many
details were changed? Collecting information from many GDBs is trust-
worthy and more accurate if we know already how to deal with some
inconsistencies between homologous objects, candidates for integration.
The scope of our work is to ensure location and cartographic integrations
for LBS information supplied by many providers. In other words, homolo-
gous objects should be integrated to avoid duplicated icons on the mobile
