More Attributes for each Route Link
More link attributes, like speed limit or slope, can be retrieved directly in the response. This is an alternative to calling PDE along the route, for select use cases. Use request parameter
&attributes=... list of PDE layers and attributes out of each layer ...
When to retrieve attributes directly in the route match call and when to fetch them afterwards from PDE?
In general, a matched route spans a few PDE tiles only, because the major part of a route is on functional class 1 roads (motorways) that are stored in PDE layers with large tiles. Hence, after a route match, the distinct set of tiles to load from PDE should rarely exceed 20 or 30, resulting in a few PDE requests, because each PDE request can ask for multiple tiles of multiple layers. The advantage of using PDE is that the retrieved full tile content can be cached for up to a month, and hence repeated transmission is avoided, if the assets are repeatedly driving in similar areas, which is usually the case.
However, asking for the attributes directly in the route match request is more simple on client side, and only the data of the links along the route are actually transferred. Where this is important, attributes should be fetched directly with the route match call.
ADAS_ATTRIB_FCn BASIC_HEIGHT_FCn DISTANCE_MARKERS_FCn LANE_FCn LINK_FCn LINK_ATTRIBUTE_FCn LINK_ATTRIBUTE2_FCn LINK_TMC_FCn ROAD_ADMIN_FCn ROAD_GEOM_FCn SPEED_LIMITS_FCn ROAD_NAME_FCn ROAD_ROUGHNESS_FCn ROUNDABOUT_FCn SPEED_LIMITS_FCn SPEED_LIMITS_COND_FCn SPEED_LIMITS_VAR_FCn TOLL_BOOTH_FCn TOLL_LINK_FCn TRAFFIC_PATTERN_FCn TRAFFIC_SIGN_FCn TRUCK_SPEED_LIMITS_FCn TRUCK_RESTR_FCn TURN_RESTR_FCn