DGGS/API
< DGGS
A API vem sendo padronizada dentro do padrão DGGS, pela OGC. Atualmente pela norma "OGC API - Discrete Global Grid Systems - Part 1: Core", https://docs.ogc.org/DRAFTS/21-038.html
Requirements
- 1. ...
- 4.
/req/data-retrieval/zone-data
Retrieving data for a single DGGS zone (célula).- 4.A. HTTP GET operation at a resource path ending with "…/dggs/{dggrsId}/zones/{zoneId}/data".
- 4.B. The operation SHALL include a templated link to this resource path in the Core "…/dggs/{dggrsId}" resource link templates, and regular link in the "…/dggs/{dggrsId}/zones/{zoneId}" resource links.
- 4.C. The response of the HTTP GET operation SHALL have a status code of 200.
- 4.D. The content of the response SHALL be a data packet corresponding precisely to the area covered by the DGGS zone.
- 4.E. The selection of an encoding for the response SHALL be consistent with HTTP content negotiation.
- 4.F. The "…/dggs/{dggrsId}" resource SHALL include a defaultDepth property indicating the implementation’s default depth for when the zone-depth parameter is omitted.
- 4.G. Unless a zone-depth parameter is specified, the response SHALL return a data packet consistent with this defaultDepth property.
- ...
- 31.
req/zone-uint64
Requirements Class 64-bit Binary Zone List
- 32.
/req/zone-uint64/content
.- 32.A. ...
- 32.B. The 64-bit integer identifiers SHALL be the one defined by the DGGRS.
- 32.C. "The endianness of the returned count and zones integers SHALL be little endian".
Explain: A big-endian representation has a multibyte integer written with its most significant byte on the left; a number represented thus is easily read by English-speaking humans.