-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NGD Feature Collection Items results is completely random? #65
Comments
Hi @wwwhatley. The image you have provided demonstrates a vanilla JS call to the NGD Features API (there are a separate set of examples which use the By default the API will only return a maximum of 100 features per request. In order to receive all the features within the bounding box you would need to send multiple requests (in a process referred to as "paging"). Each GeoJSON response will have a links property to define the self [current set of 100 features] + next [next set of 100 features] + prev [previous set of 100 features] URIs to help with this process. NOTE: The prev URI will only appear from the second page of results. The next URI will not appear on the final page of results (to indicate that the full set of requests have been made). The example shown demonstrates a single request for the first 100 features (without any paging). The follow code snippet demonstrates how you could page through the requests (up to a limit of 5000 features):
The |
I've tested this endpoint a bunch of different ways:
https://api.os.uk/features/ngd/ofa/v1/collections/${collectionId}/items?key=${apiKey}&bbox=${extent.join(',')}&bbox-crs=http://www.opengis.net/def/crs/EPSG/0/3857
The results are completely random? Attaching image from OS' code sandbox:
Not understanding why only some buildings are selected, it should be all within the bounding box, limited to 100, not sporadic.
The text was updated successfully, but these errors were encountered: