![]() api/v1/catalog/collections/Ĭ/api/v1/catalog/collections/Ĭ Hub is a cloud based service providing easy access to global archives of analysis-ready Earth Observation data from all the major providers. The requested metadata will be returned as JSON formatted response to your request. To access Landsat BYOC or Batch product metadata you need to send search request to our Catalog API. Here is an example of a WFS GetFeature request: To query your tiles using WFS you need to set the WFS feature type ( TYPENAMES parameter) to byoc- for BYOC, and batch- for Batch, e.g. Once this is done the layer can be used via OGC API in the usual way. This should return the appropriate values based on bands that are defined in the collection. You should also enter a custom script in Data processing field. When adding a layer you should set Source to Bring Your Own COG and Collection id to the id of your collection. To access your data via OGC you need to create a layer in the Configuration utility in either an existing or new configuration. ![]() The only units available are digital numbers ( DN) so any unit conversions, if necessary, are the responsibility of your evalscript. Note also that for floating point rasters, NaN is always treated as no data. a pixel with data outside tile's cover geometry or a pixel with no-data within tile's cover geometry) will result in dataMask 0. In BYOC, dataMask value equals 1 only when a pixel is contained within cover geometry of a BYOC tile and when a pixel has data at the same time. The band names to use in you evalscript are also listed in each collection in your dashboard.ĭataMask is also available. Since collections contains your data this means that the available bands are the ones you have prepared. NEAREST - nearest neighbour interpolation BILINEAR - bilinear interpolation BICUBIC - bicubic interpolationĪs above except when the resolution is lower. Parameterĭefines the interpolation used for processing when the pixel resolution is greater than the source resolution (e.g. This chapter will explain the object of the process API. Similar to mostRecent but in reverse order. In case there are more tiles available with the same sensing time, the one, which was created later will be used. The pixel will be selected from the tile, which the most recent sensing time. 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įor the list of endpoints where batch collections are available, see here. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |