-
Notifications
You must be signed in to change notification settings - Fork 0
Locations
Daniel Santillan edited this page Feb 6, 2024
·
2 revisions
Locations allow defining points of interest within some of the provider types. A Typical example would be a WMS layer that has global coverage but only has data over some specific cities. In order to allow highlighting these regions the wanted locations can be specified and described.
Locations can be used for Sentinel Hub and Sentinel Hub WMS Resources.
Locations are required for Sentinel Hub WMS
resources!
Element | Type | Description |
---|---|---|
Identifier | string | REQUIRED. Identifier used for the location |
Country | string | 2 letter country identifier (ISO 3166-1 alpha-2) |
Name | [string] | Descriptive name of location |
Point | [number, number] | Longitude, Latitude values (EPSG:4326 projection) |
Bbox | [number, number, number, number] | Bounding box specified as minlong, minlat, maxlong, maxlat values (EPSG:4326 projection) - REQUIRED when using Sentinel Hub WMS resource |
Times | [string] | List of datetimes strings to be used - REQUIRED when using Sentinel Hub WMS resource |
Example configuration:
Locations:
- Identifier: Tulare
Country: US
Name: Tulare Lake
Point: [-119.70, 35.90]
Bbox: [-120, 35.72, -119.4, 36.2]
Times: [
'2023-01-01', '2023-01-06', '2023-01-21', '2023-01-26'
]
- Identifier: Aral
Country: ['UZ', 'KZ']
Name: Aral Lake
Point: [58.581, 45.303]
Bbox: [57, 43.24, 62.29, 47.72]
Times: [
'2017-04-07', '2017-08-05', '2017-08-20', '2017-08-25'
]