Geocoding

Geocoding means matching addresses to the correct location (latitude and longitude) on the map.

 

Feature description	Core classes	Wrapper classes
Geocodes an address that is given in a single field. The parts of the text string can be in any order. The result set also includes POIs and landmarks that have similarities in the name or address with the input text.	searchFree	Map24.GeocoderServiceStub. geocode
Geocodes an address that is specified in separate fields such as city, street, etc. This operation can be used to return results of higher quality than those returned by the free map search. Furthermore, using the qualified map search may help to avoid ambiguities.	searchQualified	Map24.GeocoderServiceStub. geocode
Geocodes multiple addresses with one request. For example, this can be useful for geocoding addresses that are stored in an address database.	geocodeAddresses	-
Searches for the intersections between two or more streets. The response contains the coordinates of the intersections.	geocodeIntersections (since version 2.3)	-

Reverse Geocoding

Reverse Gecoding is the opposite operation of geocoding. From the input of a single coordinate (for example a user's mouse click or a GPS signal) it searches surrounding map objects and provides a textual description of the position.

 

Feature description	Core classes	Wrapper classes
Returns the name and the geometry type (POINT, POLYLINE, or POLYGON) of each map layer of the used map. This information is needed for the reverseGecodePoints operation.	getMapConfiguration	-
Searches for map objects in specified map layers. It is possible to search both in base map and DMap layers. The search is performed within a radius around the given map coordinates.	reverseGeocodePoints	-
Searches for surrounding map objects in the country, city, street and postal code layers.	reverseGeocodeAddresses	Map24.GeocoderServiceStub. reverseGeocode

Routing

The routing feature allows calculating a route between two locations and, optionally, via additional stops. The generated route information consists of a graphical representation (polyline) of the route and a turn by turn detailed route description. The mapping client can render the geographical representation of the route together with the map data so that the route is displayed on the map.

 

Feature description	Core classes	Wrapper classes
Calculates a route from the given input parameters. The response contains the RouteID to identify the route on the server in subsequest requests, the geometry of the route, and optionally a detailed route description.	calculateRoute	Map24.RoutingServiceStub. calculateRoute
Returns an already calculated route including all additional information such as a detailed route description.	fetchRoute	-
Returns the coordinates of each route segment of a calculated route. For example, this operation can be used to display additional information such as icons along the route.	fetchRouteLinks	-
Returns the route's geometry consisting of the shape points of each route segment.	fetchRouteShape	-
Returns information about the link in the routing network that is closest to the given coordinate. A link in the routing network is typically a line that leads from one junction to the next junction.	linkInfo	-

Remote Controlling Mapping clients and data integration

With the so-called Maplet Remote Control (MRC) commands you can e.g.

• Change the map view,
• Display an icon or label on the map to mark a location,
• Display a geometric shape such as a polygon on the map,
• and much more.

Feature description	Core classes	Wrapper classes
Remote controls a mapping client. This operation is used sending the above mentioned MRC commands that are used for controlling mapping clients or pushing custom map data on a mapping client.	mapletRemoteControl	Several functions of Map24.MapApplication (e.g. SetMapView), and the direct subclasses of Map24.MapObject (e.g. Map24.Location)
Returns the IDs of all map layers that are contained in a MapTP client session. For some MRC commands you need to know these IDs, for example in order to define which map layers should be visible with the ControlLayer command. This command is not supported in the HTTP GET interface.	getMapletLayers	-
Returns the state of a mapping client that is stored on the server. For example, the server stores the history of MRC commands that were performed during a Map24 session. This command is not supported in the HTTP GET interface.	getMapletSession	-

Proximity Search

Proximity search allows searching for MapTP Locations as well as custom locations. MapTP Location are POIs that are provided from map vendors. If your map data contains POIs from different map vendors, it is possible to return POIs from a specific map vendor only. Custom locations are part of a custom map (DMap). Custom locations can be added to the map with the MapTP Map Service. To narrow down your search you can specify various search filters.

 

Feature description	Core classes	Wrapper classes
Returns the location layers that can be accessed with the used MapTP ID. The returned layer IDs can be used in a findCustomerLocations request to specify the layers in which the search is perfomed.	getLocationLayers	Map24.ProximityServiceStub. getCustomerLocationLayers
Allows to search for locations witin a given search radius around a geographic coordinate.	findByPoints	Map24.ProximityServiceStub.findCustomerLocations (allows to specify attributes and a search radius)
Allows to search for locations witin a polygonal area.	findInPolygons	-
Allows to search for locations witin a specified corridor along a route that has been calculated with the calculateRoute function.	findInRouteCorridor	-