Iterating features

Iterating over features is different from search in two ways:

  1. The results are ordered, no features are returned twice.
  2. Searches can be continued over several requests.

Search results can contain many features. The limit you explicitly set or the default limit will only return some of them. In this case, a root attribute handle is set in the response. The search can then be continued with the next feature in line by adding the value of the handle response attribute as a handle query parameter to the request.

GET /<Base path for the interactive API from the API Lookup Service>/layer/<Layer ID>/iterate
Host: <Hostname for the interactive API from the API Lookup Service>
Authorization: Bearer <Authorization Token>
Cache-Control: no-cache

Note

For authorization in a GET request you can also use an API Key as a query parameter instead of a bearer token in an authorization header.

{
    "type": "FeatureCollection",
    "features":
    [
      {
        "type": "Feature",
        "id": "BfiimUxHjj",
        "geometry":
        {
          "type": "Point",
          "coordinates":
          [
            -2.960847,
            53.430828
          ]
        },
        "properties":
        {
          "name": "Anfield",
          "@ns:com:here:xyz":
          {
            "createdAt": 1517504700726,
            "updatedAt": 1517504700726,
           },
           "amenity": "Football Stadium",
           "capacity": 54074,
           "popupContent": "Home of Liverpool Football Club"
          }
      }
  ]
}

results matching ""

    No results matching ""