We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It makes the 'available-assets' endpoint more convenient to use.
Major, since most apps use bounding boxes to retrieve assets on a map.
Add bounding box fields as arguments on the available-assets endpoint
- name: northEast in: query description: "optional: bounding box northEast (lat+lon) parameter to limit the results. (See Google Maps LatLngBounds)" required: false example: northEast=10.12400,51.123123 schema: type: string - name: southWest in: query description: "optional: bounding box southWest (lat+lon) parameter to limit the result. (See Google Maps LatLngBounds" example: southWest=10.12400,51.123123 required: false schema: type: string
The text was updated successfully, but these errors were encountered:
edwinvandenbelt
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
It makes the 'available-assets' endpoint more convenient to use.
Urgency
Major, since most apps use bounding boxes to retrieve assets on a map.
Describe the solution you'd like
Add bounding box fields as arguments on the available-assets endpoint
Possible Implementation
The text was updated successfully, but these errors were encountered: