- What is CREODIAS?
- Computing & Cloud
- Data & Processing
- Pricing Plans
- Fight with COVID-19
- Examples of usage
- EO Data Access (R)evolution
- Land cover classification using remote sensing and AI/ML technology
- AI-based satellite image enhancer and mosaicking tools
- Monitoring air pollution using Sentinel-5P data
- Species classification of forests
- Enabling AI / ML workflows with CREODIAS vGPUs
- Satellite remote sensing analyses of the forest
- Satellite-based Urban Heat Island Mapping on CREODIAS
- Old but gold - historical EO data immediately available and widely used on CREODIAS
- CREODIAS for emergency fire management
- AgroTech project as an example of how CREODIAS can be used for food and environmental research
- Monitoring Air Quality of Germany in Pre vs During COVID Lockdown Period
- EO4UA
- Common Agricultural Policy monitoring with Earth Observation
- Applications of CREODIAS data
- Meteorological data usage on the CREODIAS platform
- Building added value under Horizon Europe with CREODIAS
- CREODIAS: Introduction to SAR Sentinel-1 data
- Land subsidence and landslides monitoring based on satellite data
- Satellite imagery in support of the Common Agriculture Policy (CAP) and crop statistics
- Useful tools for data processing, available on CREODIAS platform
- CREODIAS for hydrological drought modelling
- CREODIAS for managing Urban Heat Islands
- CREODIAS for Digitising Green Spaces
- CREODIAS for Air Quality
- Advanced data processors on CREODIAS
- CREODIAS for your application
- Solutions for agriculture with CREODIAS
- Earth Observation data for Emergency response
- Security Applications with Satellite Data
- Climate Monitoring with Satellite Data
- Water Analysis on CREODIAS
- CREODIAS for land and agriculture monitoring
- Solutions for atmospheric analysis
- Example of tool usage
- Processing EO Data and Serving www services
- Processing and Storing EO
- Embedding OGC WMS Services into Your website
- GPU Use Case
- Using the EO Browser
- EO Data Finder API Manual
- Use of SNAP and QGIS on a CREODIAS Virtual Machine
- Use of WMS Configurator
- DNS as a Service - user documentation
- Use of Sinergise Sentinel Hub on the CREODIAS EO Data Hub
- Load Balancer as a Service
- Jupyter Hub
- Use of CREODIAS Finder for ordering data
- ESRI ArcGIS on CREODIAS
- Use of CEMS data through CREODIAS
- Searching, processing and analysis of Sentinel-5P data on CREODIAS
- ASAR data available on CREODIAS
- Satellite remote sensing analyses of the forest
- EO Data Catalogue API Manual
- Public Reporting Dashboards
- Sentinel Hub Documentation
- Legal Matters
- FAQ
- News
- Partner Services
- About Us
- Forum
- Knowledgebase
Sentinel Hub Documentation
Sentinel Hub is a multi-spectral and multi-temporal big data satellite imagery service, capable of fully automated archiving, real-time processing and distribution of remote sensing data and related EO products, managed by Sinergise Ltd. For more information on Sinergise go to Third Party Services.
WFS request
The Sentinel WFS (Web Feature Service) service conforms to the WFS standard. It provides access to the geometric (vector) metadata about Sentinel-2 tiles. As with the WMS service, WFS is also only available via a user-preconfigured custom server instance URL.
The base URL for the WFS service:
http://services.sentinel-hub.com/ogc/wfs/{INSTANCE_ID}
The service supports many vector formats, including GML, XML, JSON and also raw HTML and plain text. Check GetCapabilities
for a list of all supported formats. It supports WFS version 2.0.0.
WFS URL parameters
Standard common WFS URL parameters (parameter names are case insensitive):
WFS parameter | info |
---|---|
SERVICE | Required, must be "WFS". |
VERSION | WFS version standard. Optional, default: "2.0.0". Supported values: "2.0.0". |
REQUEST | What is requested, valid values: |
TIME | (when REQUEST = |
In addition to the standard WFS request parameters the WFS service also supports many custom URL parameters. See Custom service URL parameters for details.
Standard GetFeature
request URL parameters:
WFS parameter | info |
---|---|
TYPENAMES | The name of the data to be returned. Valid value: "S2.TILE" (or appropriate data source for Landsat, Sentinel-1, etc.) as only the tile's metadata is returned. |
MAXFEATURES | The maximum number of features to be returned by a single request. Default value: 100. Valid range: 0..100. |
BBOX | The bounding box area for which to return the features. |
SRSNAME | The CRS in which the BBOX is specified. |
FEATURE_OFFSET | Offset controls the starting point within the returned features. |
OUTPUTFORMAT | The MIME format of the returned features. |
Standard DescribeFeatureType
request URL parameters:
WFS parameter | info |
---|---|
TYPENAMES | The name of the data to be returned. Valid value: "S2.TILE", as only the tile's metadata is returned. |
OUTPUTFORMAT | The MIME format of the returned features. |