WorldView (+ GeoEye)
WorldView provides high resolution optical imagery and is owned by Maxar. It is now possible to purchase, order and access WorldView data using Sentinel Hub (SH). Sentinel Hub orders WorldView data through European Space Imaging.
About WorldView data
Mission information
The WorldView constellations consists of four active satellites: WorldView-1 (data not available in SH), GeoEye-1 (GE01), WorldView-2 (WV02), and WorldView-3 (WV03). The WorldView-4 (WV04) satellite was operational from November 2016 to January 2019 and the data it acquired is available in SH. For more information on the specific missions check this brochure.
Basic facts
Property | Info |
---|---|
Spatial resolution | Varies from 0.3m to approx. 2m. SH supports 0.5 m for panchromatic band and 2 m for multispectral bands. |
Sensor | Multispectral Imagery, 5 bands are supported in SH: panchromatic, Blue, Red, Green and Near-Infrared band. |
Revisit time | From approx. 1 day to 3 days depending on the satellite. Note that the data is in general not acquired systematically. Archive data is available sporadically over an area of interest. In case you need systematic monitoring of a specific area, contact us to order tasking (different pricing conditions apply). |
Spatial coverage | Global |
Data availability | Since 2009 |
Measurement | Top of the atmosphere (TOA) reflectance |
Common usage/purpose | Land-cover maps, land-change detection maps, vegetation monitoring, defence, traffic, marine monitoring |
Attribution and use
The WorldView products are released under the license available here.
Purchasing WorldView Data
The process of purchasing of WorldView data in Sentinel Hub goes as follows:
- Check the pricing and conditions. If you would like to buy a bigger area, send us an e-mail and we will prepare a custom offer.
- Go to the "Billing" section in your SH Dashboard and buy the WorldView plan.
- Once the payment is processed, we will provide your data to European Space Imaging for a compliance check (only first purchase). Once we get a confirmation (usually the next working day), we will send you a confirmation and you will be able to proceed with ordering the data.
Ordering WorldView Data
To order WorldView data, please use our Third Party Data Import API. Minimum individual order is 5 km2 and smaller orders are not possible. Furthermore, if your area of interest intersects with multiple WorldView scenes, then each intersection must be greater than 5 km2. Orders below 5.1 km2 are billed as 5 km2 to simplify splitting your available quota between multiple orders.
SH uses the following settings when ordering WorldView data:
Provider's parameter / tool | The values used by SH for ordering | Description |
---|---|---|
productBands | 4BB | 4 band bundle, which contains panchromatic, red, blue, green and near IR bands. |
fullOverlap | true | All scenes intersecting requested AOI will be ordered. |
fullStrip | false | Data will be clipped to the AOI provided in the payload. |
productLevel | ORTHO | Map-ready 1:12,000 orthorectified products. |
productBits | 16 bit | Requested bit depth of data. |
productProjection | WGS84_UTM | Data is delivered to SH in UTM projection. |
productGsd | 0.5 m | Data is resampled so that the spatial resolution of panchromatic band is 0.5m and 2m for multispectral bands. |
We convert the DN we get from the provider to the top of the atmosphere reflectance and multiply them by a factor of 10000.
Note also that:
- The specified absolute horizontal positional accuracy of WorldView ORTHO products is 10.2 m CE90. Positional errors are greater for greater nadir angles and at the locations with low accuracy of the SRTM DEM, which is used for orthorectification. For more details check this report.
Once your order is successfully completed, the ordered data will be available in one of your TPDI collections. The tiles in the collection will correspond to WorldView scenes. To access the data, you will need the ID of this collection.
Accessing WorldView Data
Accessing WorldView data is similar to accessing BYOC data. All processing and filtering options listed there can be used. However, the settings specific for accessing WorldView data are listed below.
Endpoint Locations
Service | Notes |
---|---|
https://services.sentinel-hub.com/ | Contains the data purchased by individual user |
Filtering Options
collectionId
Use the id of the TPDI collection into which your WorldView data was delivered as a value of parameter input.data.type
in the process
API requests. See BYOC data access for more information.
Available Bands and Data
This chapter will explain the bands and data which can be set in the evalscript input object.
Any string listed in the column Name can be an element of the input.bands
array in your evalscript.
Name | Description | Resolution |
---|---|---|
Blue | Blue, 450 - 510 nm | 2m |
Green | Green, 510 - 580 nm | 2m |
Red | Red, 630 - 690 nm for WV02 and WV03, 655 - 690 nm for GE01 and WV04 | 2m |
NearIR1 | Near Infrared, 770 - 895 nm for WV02 and WV03, 780 - 920 nm for GE01 and WV04 | 2m |
PAN | Panchromatic, 450 - 800 nm | 0.5m |
dataMask | The mask of data/no data pixels (more). | N/A* |
*dataMask has no source resolution as it is calculated for each output pixel.
Units
The data values for each band in your custom script are presented in the units as specified here. In case more than one unit is available for a given band, you may optionally set the value of input.units
in your evalscript setup
function to one of the values in the Sentinel Hub Units
column. Doing so will present data in that unit. The Sentinel Hub units
parameter combines the physical quantity and corresponding units of measurement values. As such, some names more closely resemble physical quantities, others resemble units of measurement.
The Source Format
specifies how and with what precision the digital numbers (DN
) from which the unit is derived are encoded. Bands requested in DN
units contain the pixel values which are the result of ordering and preprocessing the data as explained in the chapter Ordering WorldView Data. Note that resampling may produce interpolated values. DN
is also used whenever a band is derived computationally (like dataMask); such bands can be identified by having DN
units and N/A
source format.
For WorldView bands, DN
are the default and only unit. Reflectance values can be obtained for optical and panchromatic bands using the simple formula: reflectance = DN / 10000
.
The Typical Range
indicates what values are common for a given band and unit, however outliers can be expected.
Band | Physical Quantity (units) | Sentinel Hub Units | Source Format | Typical Range |
---|---|---|---|---|
Optical and panchromatic bands | Scaled reflectance (unitless) | DN | UINT16 | 0 - 4000 Highly reflective pixels can have values above 10000. |
dataMask | N/A | DN | N/A | 0 - no data 1 - data |
Mosaicking
All mosaicking types are supported.