Search and retrieve map content using following resources:
Quadkey search allows specifying a bounding box with a single parameeter value. Note that quadkeys assume a Mercator projected map display. and row information for a tile into one value.
In a quadkey, each bit further divides the world map into 2 halfs, alternating between a horizontal and a vertical cut. The bit string is passed in base-4 format which packs pairs of bits together into one digit. The length of a quadkey string equals to the zoom level of the tile.
For example, if you had a quadkey for a column with 35210, a row with 21493, and a zoom level of 16, then the quadkey value is 1202102332221212.
The access to map data is optimized for spatial access, i.e. for access via coordinates. For accessing custom data by filter expressions or search phrases indexes can be created on storage level. To specify those the names of the attributes can be postfixed with an index type.
Currently two types of indexes are supported:
|Type of Index||PostfixMarker||Purpose||Availability for Storage Types|
|Order||o||Creates an index on the order of the selected attribute. These can improve the search speed if filter expressions with relations such as < or > are used.||updatable, readonly|
|Text||t||Creates a trigram text index allowing a fault tolerant search with possibly incomplete search words.||updatable|
|All||*||Any of the mentioned indexes will applied. This includes future enhancements if the data is uploaded again.||Indices are created as available (see above)|
To add an ordering index on the column "Name" the header of the uploaded content will change from
with '\t' as the 'tab'-character.
To enable fault tolerant text search on all text columns the header would change to:
This section clarifies the three (3) different functions HLS Router Isoline Routing, Search along Route Isoline and WSE Pickup along Route.
HLS Router offers Isoline and Reverse Isoline functions. As shown in the figure, the result is a polygon covering all road links that can be reached from the given location (left polygon) within a certain amount of driving time (or distance). Similarly, all road links from where the given location (middle polygon) can be reached within a certain amount of driving time (or distance).
The rightmost polygon in the figure shows that the main purpose is map display, because it is not guaranteed that each link covered by the spanning polygon is actually within reach. The red link outlines a motorway with exits on both ends but not within the isoline polygon. A car driving on this motorway cannot reach the location within the time/distance limit. Fleet Telematics Custom Locations offers accuracy on a link level.
An Isoline along a Route is a buffer along a route path. This buffer covers either of following:
The detour is measured from the exit on the route to the center of the link. The detour to return onto the route is disregarded. The idea is, that this function is a first step, followed by a second step to select links/POIs and a third step to compute the final route.
Isolines along a Route are accurate on a link level, as the following figure shows (left).
The right side of the figure shows how Isolines along a Route can be used to obtain a link-level-accurate version of HLS Router's Isoline function (but not yet for its Reverse Isoline function): Define a very short route (almost a point) around the location.
Routing with optional pick & drop points identifies which optional way points along a route are worth being met. The goal is optimization of the overall route driving cost, including the cost per kilometer (driver cost) and the cost per hour (vehicle cost) for the route including all detours to pick up and drop off goods or persons. The figure shows an example: Is it worthwhile to pick up one of the persons (or both) on my route from (0) to (1)? They want to be picked up where the face is shown and dropped off at where the reward $ is shown.
For more detail refer to section "Waypoint sorting, optional Pickup and Opening Times".
You can directly search on all "geometry" layers, i.e. layers whose map objects contain geometry. The "attribute" layers however contain no geometry, they just provide additional attributes to objects of a geometry layer.
For example, a road geometry layer contains the geometries, while a speed limit layer contains additional attributes to each map oject (road link) of the according road geometry layer.
Hence, perform the spatial search on the geometry layer, then take the resulting link ID(s) and tile ID(s) and fetch & match the according speed limit information from the "same" speed limit layer tiles and the link IDs therein.