The tiling is defined by the user when ingesting the data in the collection. Sets the order of overlapping tiles from which the output result is mosaicked. Alternatively, in the response if querying a collection using the BYOC API. You can see the computed resolution limit for a collection in the collection details in your dashboard. Adding or removing tiles from a collection will recompute its limit. Note, only overviews which are at least 256 pixels in either width or height are used for this computation. ![]() This is to allow for more zoomed out viewing. If this resolution is higher than 500 meters per pixel, the limit is set at 500 meters per pixel. Request resolution limitįor the limit, we take five times the median resolution of the lowest resolution overview of all tiles in the collection. Use byoc- for BYOC, and batch- for Batch as the value of the parameter in your API requests. Endpoint Locationsįor data in AWS buckets in EU-Central-1 regionįor data in AWS buckets in US-West-2 regionīatch is only available from the endpoint /api/. You also need to access data from the correct endpoint. ![]() In all cases collection id is needed, which can be obtained from your dashboard. Accessing dataĭata is accessed using Sentinel Hub APIs, just like any other data you are used to. Bring Your Own COG (BYOC) and Batch data is data ingested by Sentinel Hub users using BYOC API and Batch API, respectively.
0 Comments
Leave a Reply. |