Traffic API Developer's Guide

Request Flow Availability

Flow availability requests allow you to see what traffic flow coverage exists in the current (version 6.0.63.0) Traffic API. You can construct a request to obtain the coverage for an entire customer profile or for the customer profile in a specific map view. This article demonstrates the both types of request.

Flow Availability by Profile

User Story

The user wants to obtain information about the traffic coverage available for the NTdefault profile at zoom level 10. The information is to be delivered in XML

Request Summary

The following list summarizes the elements required to create a request matching the user story and shows, in square brackets, how those elements are used in the request example below. Note that the request example also uses the authentication parameters.

Resource: flowavailability [flowavailability.xml], the resource and resource extension indicating the required response data format, here XML (to indicate JSON, use flowavailability.json)
Parameters: profile [profile=NTdefault], the identifier of the customer profile
  zoom [zoom=10], the map zoom level

Request

A request matching the user story is formulated as follows:

https://traffic.cit.api.here.com/traffic/6.0/flowavailability.xml
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&profile=NTdefault
&zoom=10

Response

Because the request is simply based on the profile, with no restrictions, the response is too large to display here, but it contains XML data similar to those shown in the next example (under Response).

Flow Availability by Map View

User Story

The user wants to obtain information about traffic flow coverage for the default customer profile in a certain map view at zoom level 10.

Request Summary

The following list summarizes the elements required to create a request matching the user story and shows, in square brackets, how those elements are used in the request example below. Note that the request example also uses the authentication parameters.

Resource: flowavailability [flowavailability.xml], the resource and resource extension indicating the required response data format, here XML (to indicate JSON, use flowavailability.json), but see also the note below the table)
Parameters: mapview [mapview=50.73818,7.09992;50.73736,7.10123] , the geographic coordinates of the map view defined (the coordinates of the top-left and bottom-right corners of the map view)
  profile [profile=NTdefault], the identifier of the customer profile
  zoom [zoom=10], the map zoom level
Note: Note that the JSON output is not finalized and potentially subject to change. Also, please note that XML and JSON output are provided in a non-formatted way. Output has been formatted for this document for better readability only.

Request

A request matching the user story is formulated as follows:

https://traffic.cit.api.here.com/traffic/6.0/flowavailability.xml
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&mapview=50.73818,7.09992;50.73736,7.10123
&profile=NTdefault
&zoom=10

Response

The XML response contains the XML data similar to the excerpt shown below.


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<traffic_flow_availability:GetTrafficCoverageType
  xmlns:traffic_flow_availability="http://www.navteq.com/lbsp/LBSP-Traffic-GetCoverage/4">
  <Request>
    <MetaInfo>
      <VerboseMode>-1</VerboseMode>
    </MetaInfo>
    <MapView>
      <Bounds>
        <TopLeft>
          <Latitude>50.73818</Latitude>
          <Longitude>7.09992</Longitude>
        </TopLeft>
        <BottomRight>
          <Latitude>50.73736</Latitude>
          <Longitude>7.10123</Longitude>
        </BottomRight>
      </Bounds>
      <Zoom>10</Zoom>
    </MapView>
    <Profile>NTdefault</Profile>
  </Request>
  <Response>
    <MetaInfo>
      <MapVersion>LBSP_WORLD_2013Q1_ECC</MapVersion>
      <ModuleVersion>6.0.24.1</ModuleVersion>
      <InterfaceVersion>6.0</InterfaceVersion>
      <Timestamp>2013-08-15T14:56:41.829+00:00</Timestamp>
    </MetaInfo>
    <Profile>NTdefault</Profile>
    <MapView>
      <Bounds>
        <TopLeft>
          <Latitude>50.73818</Latitude>
          <Longitude>7.09992</Longitude>
        </TopLeft>
        <BottomRight>
          <Latitude>50.73736</Latitude>
          <Longitude>7.10123</Longitude>
        </BottomRight>
      </Bounds>
      <Zoom>10</Zoom>
    </MapView>
    <Region>
      <TmcTableId>E0D01</TmcTableId>
      <Country3>DEU</Country3>
      <Country2>DE</Country2>
      <Name>Germany</Name>
    </Region>
  </Response>
</traffic_flow_availability:GetTrafficCoverageType>
  

You cannot use this account to purchase a commercial plan on Developer Portal, as it is already associated to plans with different payment methods.

To purchase a commercial plan on Developer Portal, please register for or sign in with a different HERE Account.

Something took longer than expected.

The project should be available soon under your projects page.

Sorry, our services are not available in this region.

Something seems to have gone wrong. Please try again later.

We've detected that your account is set to Australian Dollars (AUD).
Unfortunately, we do not offer checkouts in AUD anymore.
You can continue using your current plan as normal, but to subscribe to one of our new plans,
please register for a new HERE account or contact us for billing questions on selfservesupport@here.com.