Discovery API: Image meta-data

Output Format

Supported output formats are JSON (JavaScript Object Notation), GeoJSON and KML.

JSON

JavaScript Object Notation (JSON) format is the default output format for imagery metadata.
It can be requested explicitly using the URL parameter “of=json”.
This format is easy to use regardless of the technology you use. Despite its relationship to JavaScript, it’s language-independent, with parsers available for many languages.

API Multi Catalog - Figure 6 – A sample JSON output  
Figure 6 – A sample JSON output

Web browsers usually don’t display JSON very nicely. Some handy plug-in can help with this.
Try searching the internet using keywords like "[firefox | chrome | safari …] plugins json prettifier.

For example, the Chrome plug-in “JSON Prettifier” makes it easy to view JSON documents unformatted, in a code style and or as a table:

API Multi Catalog - Figure 7 - JSON output formatted in a code style  
Figure 7 - JSON output formatted in a code style

API Multi Catalog - Figure 8 - JSON output formatted in a tabular style  
Figure 8 - JSON output formatted in a tabular style

Firefox JSONView helps in the same way. Embedded links are clickable making it easy to access associated quicklooks for instance:

API Multi Catalog - Figure 9 - JSON output formatted using Firefox JSONView plug-in  
Figure 9 - JSON output formatted using Firefox JSONView plug-in

GeoJSON

As stated by Wikipedia, GeoJSON is an open format for encoding a variety of geographic data structures. It is so named because it is based on JSON (JavaScript Object Notation). In fact, every GeoJSON data structure is also a JSON object, and thus JSON tools can also be used for processing GeoJSON data. See the previous chapter for browser prettifiers for instance.

Spatial data format types supported in GeoJSON include points, polygons, multi-polygons, features, geometry collections, and bounding boxes, which are stored along with feature information and attributes.

Airbus Defence and Space Simple Catalog API results come as a collection of polygons. No “CRS” (coordinate reference system) is provided since we use WGS-84 geoid.

GeoJSON imagery properties (acquisitionDate, orientationAngle…) are strictly identical to JSON properties.

API Multi Catalog - Figure 10 – A sample GeoJSON output  
Figure 10 – A sample GeoJSON output

KML

KML is the file format used to display geographic data in Earth browsers such as Google Earth, Google Maps, ArcGIS Explorer, Microsoft Virtual Earth, etc.
KML is an XML-based language. KML files specify a set of features (placemarks, images, polygons, 3D models, textual descriptions, etc.) that allows defining the appearance and layout of geospatial data and text.
KML 2.2 became an official OGC (Open Geospatial Consortium) standard on April 14, 2008.

Unlike GeoJSON or JSON, KML is focused on displaying geographic features. Imagery metadata are mixed with rendering tags making it a less suitable solution for application integration:

API Multi Catalog - Figure 11 – KML imagery description  
Figure 11 – KML imagery description

Nonetheless, switching a request to output KML is of great help for debugging a query due to Google Earth ease-of-use.

In addition, query results embed a form to interactively request the API:

API Multi Catalog - Figure 12 – KML results little interactive form  
Figure 12 – KML results little interactive form
This form pops up when you click the “Search” link, head of the results KML tree. Just fill in the fields and click “submit” to request the API.

Output metadata (JSON and GeoJSON)

JSON and GeoJSON output are made of three parts:

  • Some information about the request processing. Since we request three different catalogs something can go wrong with one while we correctly get the two other results. So you’re notified of the complete or partial nature of the global result ;
  • The core metadata, identical whatever the imagery acquisition platform ;
  • Optional specific SPOT 1-5 metadata;

Core metadata (JSON and GeoJSON)

Table 1: Core Metadata (JSON and GeoJSON)

Attribute Description
Query processing information
code Request status code. Possible values are:
{“OK”;”PartialContent”; ”InvalidRequest”;”InternalServerError”}
See below for more explanation about their meaning.
The http status code is not used to report applicative issues (such as an underlying catalog unavaibility).
message A “plain-English” explanation of the status code.
featuresNumber Number of returned items.
featuresCollection The list of selected features.
Core metadata:
identifier Unique and efficient imagery internal id
productId Business id, nicknamed “A21 code” for SPOT.
metadataUrl A link to the feature metadata (JSON description).
imageUrl A link to the feature quicklook (a sub sampled image).
imageName For future use.
acquisitionDate The ISO 8601 formatted date of acquisition of the scene or datastrip.
satellite The name of the satellite which shot this scene or datastrip.
resolution The resolution of the image expressed in meters within a [0.5; 30.0] range.
incidenceAngle The incidence angle of the acquisition (given in degrees)
sensorFamily The sensor family. Panchromatic sensors produce black and white images and multispectral sensors produce color images.
productType Unified sensor code (native & combined) : A ; B ; HMX ; I ; J ; M ; MI ; P ; PA ; PX ; S ; THR ; THX ; X ; XS.
archivingStation The alphanumerical code of the station holding the full-resolution image of the acquisition.
receivingStation The alphanumerical acronym of the station archiving the full-resolution image of the acquisition.
cloudCoverPercentage The cloud coverage percentage of the scene (or datastrip).
snowCoverPercentage The snow coverage percentage of the scene (or datastrip), usually either 0 or 100, no intermediate value, 100 may mean some snow. There’s no snow quotation for many old SPOT scenes).
shift Shift along the track of the scene (SPOT 1-5 specific).
minShift The minimum allowed shift for the scene (SPOT 1-5 specific).
maxShift The maximum allowed shift for the scene (SPOT 1-5 specific).
wktCenter The geodetic position (WKT format) of the centre of the acquisition (using WGS-84 coordinates).
sunAzimuth The azimuth of the sun (given in degrees).
sunElevation The elevation of the sun (given in degrees).
orientationAngle Scene or datastrip main axis azimuth (given in degrees).
wktBounds The location of the four corners (WKT format) of the acquisition (using WGS-84 coordinates):
Upper Left ; Upper Right ; Lower Right ; Lower Left.
wktFootprint The polygon representation (WKT format) of the acquisition footprint (using WGS-84 coordinates).
qualityQuotes Technical quality quotation of the acquisition (ex. “EGPU”), “E” stands for Excellent, “G” for Good, “P” for Poor, “U” for Unusable.
extendedData SPOT specific. Extended data when explicitly requested. See below.

In almost all cases some results are to be returned even if an error has occurred.
In case of error the status code warns you that something went wrong (it is not set to “OK”). The "Message" attribute gives you some clues to pinpoint the problem (for instance an invalid criterion value) and its impact on the completeness of the results.

Pay attention that a misspelled key is silently ignored (for instance “at=circle” instead “zt=circle” makes the geographical filter to be ignored).
In case of a “PartialContent” result status (loose criteria select too many scenes) the most recent scenes for each satellite family are provided.
When the server encounters a critical error that it cannot deal with an http 500 response status code is provided.

SPOT 1/5-specific metadata (JSON and GeoJSON)

Two profiles of specific metadata are available:
Calibration parameters;
Advanced technical parameters.

They are available when the “odf” (“Output Definition Format”) key value is either “Calibration” or “TechParams” (please note this option only applies for search requests, it’s not available on a feature link).

  • SPOT 1-5 calibration parameters (“odf=Calibration”)
    They differ according the scene nature: native (i.e. real satellite acquisition) or combined (i.e. ground-processed pan-sharpened scene).
    We recommend that you refer to SPOT 1-5 official technical description for an exact definition of the following attributes:

Tableau 2 - Combined Scene Calibration Attributes

Conbined scene calibration attribute Comment
sceneType “combined” or “native”
a21 Null.
a21pp Unified SPOT 1-5 scene business identifier (“product id”).
orientationAngle Scene main axis azimuth (given in degrees).
cloudMaskAvailable “true” or “false”
nbOfAvailableBandsQuicklook Range. 0 to 4.
snowMaskAvailable “true” or “false”
minDynThreshold Minimal value of the combined reference scene quicklook image histogram for each spectral band. Range: 0 to 255.
maxDynThreshold Maximum value of the combined reference scene quicklook image histogram for each spectral band. Range: 0 to 255.
quicklookAvailable “true” or “false”
saturationPercentage Null.

 

Tableau 3 - Native Scene Calibration Attributes

Conbined scene calibration attribute Comment
sceneType “combined” or “native”
a21 SPOT 1-5 scene business identifier (“product id”).
a21pp Null (semantically equal to a21 for native scenes). 
orientationAngle Scene main axis azimuth (given in degrees).
cloudMaskAvailable “true” or “false”
snowMaskAvailable “true” or “false”
nbOfAvailableBandsQuicklook Range. 0 to 4.
minDynThreshold Minimal value of the combined reference scene quicklook image histogram for each spectral band. Range: 0 to 255.
maxDynThreshold Maximum value of the combined reference scene quicklook image histogram for each spectral band. Range: 0 to 255.
quicklookAvailable “true” or “false”
saturationPercentage Percentage of quicklook image pixels whose value is equal to 255, for each spectral band.
absoluteCalibrationCoeffs[]: Provided for each spectral band:
absCalibrationModelField
analogicGainField
See SPOT 1-5 technical documentation
gainNumber Provided for each spectral band.

 

  • SPOT 1-5 advanced technical parameters (“odf= TechParams”)
    They differ according the scene nature: native (i.e. real satellite acquisition) or combined (i.e. ground-processed pan-sharpened scene).
    We recommend that you refer to SPOT 1-5 official technical description for an exact definition of the following attributes:

Tableau 4 - Combined Scene Technical Parameters

Conbined scene technical parameters Comment
sceneType “combined” or “native”.
a21 Null.
a21pp Unified SPOT 1-5 scene business identifier (“product id”).
avgCloudCoverQuote Cloud coverage quotation: “A” (0 to 5%),” B” (5 to 17.5%),”C” (17.5 to 50%),”D” (50 to 87.5%), “E” (more than 87.5%).
avgQualityQuote “E” (Excellent),” G” (Good), “P” (Poor), “U” (Unusable).
avgSnowCoverQuote “0” (no snow), “1” (some snow).
cloudCoverQuotes Scene octant cloud quotation, using the “A” to “E” quotation.
daliDataInsertionDate The ISO 8601 formatted date of insertion of the scene into DALI.
daliDataModificationDate The ISO 8601 formatted date of last modification of the scene metadata into DALI.
imagingOrbit Integer value.
instrument Instrument name.
instrumentNb Instrument number.
K K coordinate of the scene on the KJ reference grid (linked to the satellite orbit).
J J coordinate of the scene on the KJ reference grid (linked to the satellite orbit).
maxCloudCoverQuote Scene cloudier octant quotation, using the “A” to “E” grading.
mirrorStep Integer value.
satelliteNumber Satellite number (1 to 5).
sensorCode One char sensor code.
snowCoverQuotes Scene octant snow quotation, using the “0” / “1” quotation.
combination Combination code: “MI” (SPOT 4 10m color), “THR” (SPOT 5 2.5m B&W), “THX” (SPOT 5 2.5m color), “HMX” (SPOT 5 5m color).

 

Tableau 5 - Native Scene Technical Parameters

Conbined scene technical parameters Comment
sceneType “combined” or “native”.
a21 SPOT 1-5 scene business identifier (“product id”).
a21pp Null (semantically equal to a21 for native scenes). 
avgCloudCoverQuote Cloud coverage quotation: “A” (0 to 5%),” B” (5 to 17.5%),”C” (17.5 to 50%),”D” (50 to 87.5%), “E” (more than 87.5%).
avgQualityQuote “E” (Excellent),” G” (Good), “P” (Poor), “U” (Unusable).
avgSnowCoverQuote “0” (no snow), “1” (some snow).
cloudCoverQuotes Scene octant cloud quotation, using the “A” to “E” quotation.
daliDataInsertionDate The ISO 8601 formatted date of insertion of the scene into DALI.
daliDataModificationDate The ISO 8601 formatted date of last modification of the scene metadata into DALI.
imagingOrbit Integer value.
instrument Instrument name.
instrumentNb Instrument number.
K K coordinate of the scene on the KJ reference grid (linked to the satellite orbit).
J J coordinate of the scene on the KJ reference grid (linked to the satellite orbit).
maxCloudCoverQuote Scene cloudier octant quotation, using the “A” to “E” grading.
mirrorStep Integer value.
satelliteNumber Satellite number (1 to 5).
sensorCode One char sensor code.
snowCoverQuotes Scene octant snow quotation, using the “0” / “1” quotation.
archivingDate The ISO 8601 formatted date of insertion of the telemetry into the direct receiving station inventory.
receivingOrbit Integer value.
receivingStation The alphanumerical code of the station that received the full-resolution image of the scene.
segmentType i.e. acquisition, calibration…
transStartUt The ISO 8601 formatted date of the beginning of the transmission of the imagery telemetry at the direct receiving station.
transmissionChannel See SPOT technical documentation.
transmissionMode See SPOT technical documentation.

 

Search request

Search requests allow spatial and attribute queries on the data held in the catalogs. Most commonly used criteria are acquisition date range, imagery technical quality, cloud percentage, resolution and geographical area of interest (AOI).
Each query results in a collection of “features”. Features are encoded in JSON (default format), GeoJSON or KML format.
A feature describes in a standardized way any satellite imagery regardless of its acquisition platform (SPOT, Pleiades or AstroTerra). Notwithstanding some extra platform specific properties can be requested using the parameter “odf”.

IMPORTANT:    The use of the API requires prior registration. You can get a key for your server IP address (or your e-mail) with the key generator page.  Don’t forget to provide this key as a part of the link or in the query string (sk={key}).
Before starting any industrial development don’t forget to have a look at the Good Practice section to avoid any unwanted unpleasant experience

Input criteria

Criteria are provided as key/value pairs, they are separated by ampersands.
Pay attention that a misspelled key is silently ignored (for instance “at=circle” instead “zt=circle” makes the geographical filter to be ignored).
Latitude and longitude are expressed in decimal number.
Decimal separator is always a dot.
Following are the accepted parameters (case does not matter):

Tableau 6 - Native Scene Technical Parameters

Key Parameter Name Type Values
(case sensitive
Default value Description
sk Sla Key String     Service Level Agreement Key uniquely identifying you.
of Output Format Enum {JSON ; KML; GEOJSON} JSON “Json” or “KML” or “GeoJson”. 
sd Start Date Date   Now – 1 hour Beginning of the date range of interest. Precisely, the requested scene centre date is at least later than the provided date.
All dates are assumed to be expressed as UTC time.
Dates should be formatted according ISO 8601 format (for instance “2009-02-17T23:59:59Z”).
ed End Date Date   Now End of the date range of interest.
Precisely, the requested scene centre date is prior than the provided date.
All dates are assumed to be expressed as UTC time.
Dates should be formatted according ISO 8601 format (for instance “2009-02-17T23:59:59Z”).
mc Max cloud coverage Double ]0;100] 100 Max cloud coverage percentage of the image. 
ms Max snow coverage Double ]0;100] 100 Max snow coverage percentage of the image (either 0 or 100, intermediate values are unreliable).
mi Max incidence Double ]-30.04;
30.04]
30.04 Max incidence (in degrees) of the acquisition (correlated to the satellite side-looking mirror angle). 
minr Min resolution Double [0.5;20.0] 2.5 Min resolution of the image in meters. Default value is 2.5.
maxr Max resolution Double [0.5;20.0] 20 Max resolution of the image in meters. Default value is 20.
zt Zone Type Enum {circle; rectangle; Polygon} Null. Specify the shape of the region of interest (if any).
By default the whole Earth is selected.
clon Circle centre longitude Double [-360 ; +360]   Longitude of the centre of the circle of interest.
clat Circle centre latitude Double [-180 ; +180]   Latitude of the centre of the circle of interest.
cr Circle radius Double ]0 ; 1000]   Radius in kilometers of the circle of interest.
nwlat Rectangle NW latitude Double [-180 ; +180]   Latitude of the North West corner of the rectangle of interest.
nwlon Rectangle NW longitude Double [-360 ; +360]   Longitude of the North West corner of the rectangle of interest.
selat Rectangle SE latitude Double [-180 ; +180]   Latitude of the South East corner of the rectangle of interest.
selon Rectangle SE longitude Double [-360 ; +360]   Longitude of the South East corner of the rectangle of interest.
pts Polygon points String long lat, long lat, long lat   List of points represented as longitude and latitude separated by commas.
Polygon must be closed (first and last points identical).
sc Station code String   Undefined Archiving station acronym. 
Results are restricted to scenes archived by this station.
sn Satellite name Enum {SPOT1; SPOT2; SPOT3; SPOT4; SPOT5; PHR1A ; PHR1B ; SPOT6} Undefined Satellite name. Enable filtering of the data for a particular satellite. 
sf Sensor family Enum {PANCHROMATIC; MULTISPECTRAL} Undefined Panchromatic for black and white images, Multispectral for color images.
fullness Scene fullness Enum {autoshift; completeOnly} completeOnly Incomplete SPOT 1-5 scenes are filled  with a black strip. By default such images are not returned. But some of them can be shifted until fullness. With "autoshift" these images are automatically shifted and provided.
qm Minimum quality Enum {E; G; P; U} E Minimum technical quality required for the scenes to be extracted.
odf Output definition format Enum {Basic; Calibration; TechParams} TechParams This parameter is optional. The default value is “Basic” and displays the results with the default level of detail.
Calibration adds additional information, such as calibration, scene orientation etc.
TechParams adds additional technical information.

 

Feature Links

URL pattern

Links like http://api.astrium-geo.com/catalog/data/features.svc/features/<id> gives you an instant access to the metadata of the “feature” whose identifier is <id>.

“Feature” URLs follow this pattern:

  • A service address: http://api.astrium-geo.com/catalog/data/features.svc/feature;
  • An imagery identifier (an alphanumeric string, see below for more information) ;
  • An optional output format: of=kml  for instance (preceded by an question mark) ;

Apart from a severe internal server error, the http response code is always 200 (OK).

IMPORTANT: Every request to the Simple Catalog API must contain the SLA Key corresponding to the IP address (or e-mail) of the caller. You must generate a SLA Key for your IP address (or e-mail) on the KeyGenerator page and add it as a parameter of every URL (sk={key}).

SPOT 1-5 identifiers

Two kinds of identifiers
SPOT 1-5 identifiers are divided into business identifiers (so-called A21, A21pp or A21++ code like “20422620611021103321X”) and internal identifiers (meaningless numbers like “S_35399813”). All of them can be used to designate a specific scene.
A21 ids are perennial while internal identifier shall only be used for instant processing (they are more efficient from a performance point of view but they can change in some rare situations).
SPOT 1-5 identifiers often come with a complementary “shift” value called “SAT” (see § “More about SPOT 1 to 5” for a comprehensive explanation).

SPOT 1-5 A21 scene ids

Internal identifiers are unique while an A21 id is unique for a given archiving station.
In other words, two receiving stations whose visibility circles overlap can “share” the “same” SPOT 1-5 scene and its A21 code.
When this happens, the description of the best and more complete redundant scene is provided.

A21 identifier looks like “20422620611021103321X”, which is better, wrote out as 2-042,262-061102-110332-1-X where:

  • 2 is the satellite number (scene acquired by SPOT 2);
  • 042, 262 are the coordinates of the scene on the KJ reference grid (linked to the satellite orbit);
  • 061102 is the acquisition date in YYMMDD format (i.e. November, 2  2006);
  • 110331 is the acquisition time in HHMMSS format (i.e. 11 hours, 03 minutes, 31 seconds UTC);
  • 1 is the instrument number (here: HRV1);
  • X is the spectral mode (here: X for multispectral).

For Experts. Disambiguation between the redundant scenes can be done using the scene datastrip number. Identifier syntax is then “S_54973830604292026421J_3906648” where 3906648 is the datastrip number is allowed.

SPOT 1-5 acquisitions are split into scenes. Due to a land based fixed grid boundary computation, SPOT 1-5 scenes often need to be shifted to center an area of interest (AOI).
This shift is called SAT (Shift Along the Track).
See § “More about SPOT 1 to 5 specific characteristics” for a comprehensive explanation.

The SAT value is concatenated to the scene id:

  • “_Shift0”: no shift;
  • “_Shift1”: 10% shift;
  • “_Shift9”: 90% shift.

The SAT value has to fall between the min and max values allowed for a given scene (not necessarily 0 and 9).

SPOT 1-5 internal ids (just for the record)

Internal identifier patterns are:

  • Combined scene: C_<number>_Shift<value> where value range is from 0 (0%, no shift) to 9 (90% shift) ;
  • Native scene: S_<number>_Shift<value> where value range is from 0 (0%, no shift) to 9 (90% shift) ;

Metadata resulting from search requests contain links using internal identifiers.

SPOT 1-5 examples (don’t forget to add “?sk=<your personal key>” to your  URLs)

Here are the some feature links:

  • Casual A21 designation, JSON output: 
    http://api.astrium-geo.com/catalog/data/features.svc/features/53164191202280210532U?sk...
  • A21 designation, GeoJSON output:
    http://api.astrium-geo.com/catalog/data/features.svc/features/53164191202280210532U?of=geojson&sk=...
  • Casual A21 designation with a 50% shift:
    http://api.astrium-geo.com/catalog/data/features.svc/features/50382491210231030371J_Shift5?sk=...
  • A21 and datastrip designation, JSON output: 
    http://api.astrium-geo.com/catalog/data/features.svc/features/S_54973830604292026421J_ 3906648?sk=...
    http://api.astrium-geo.com/catalog/data/features.svc/features/S_54973830604292026421J_ 3906648_Shift0?sk=...
  • Combined scene internal designation, JSON output, 10% shift:
    http://api.astrium-geo.com/catalog/data/features.svc/Features/C_22406667_Shift1?sk=...
  • Combined scene internal designation, GeoJSON output, no shift:
    http://api.astrium-geo.com/catalog/data/features.svc/Features/C_22406667_Shift0?of=geojson&sk=...
  • Native scene internal designation, JSON output, no shift:
    http://api.astrium-geo.com/catalog/data/features.svc/Features/S_36887839_Shift0?sk=...
  • Native scene internal designation, KML output, 10% shifted:
    http://api.astrium-geo.com/catalog/data/features.svc/Features/S_36887839_Shift1?of=kml&sk=...

Be careful, the SAT value of a SPOT scene must be between its min and max shift. Otherwise a “no data” result is provided.

PHR identifiers

A PHR identifier looks like “DS_PHR1A_201204040917388_FR1_PX_E018N04_0709_01211”.
It is made of 8 fields:

  • DS_PHR,
  • < satellite number>: either “1A” or “1B”,
  • < datastrip acquisition start time>: given in UTC time, 2012/04/04, 09h17m38’08 in this example,
  • <initial archiving center acronym>,  “FR1” for instance,
  • <spectral mode>, “PX” (order options indicate which product is asked: Panchromatic, Multispectral or Pan-sharpened),
  • <closest square degree of the strip center>, ex. “E018N04”,
  • <closest cell in the Pléiades Grid of the strip center>, ex. “0709”
  • <number of source frames>

The global pattern is:
DS_PHR<satellite number>_< UTC strip source acquisition start time, YYYYMMDDHHMMSSS>_<initial archiving center acronym>_<spectral mode>_<closest square degree of the strip center>_<closest cell in the Pléiades Grid of the strip center>_<number of source frames>

Example

Here are some possible feature links:

  • Casual designation, JSON output:
    http://api.astrium-geo.com/catalog/data/features.svc/features/DS_PHR1A_201204040917388_FR1_PX_E018N04_0709_01211?sk=...
  • Casual designation, GeoJSON output:
    http://api.astrium-geo.com/catalog/data/features.svc/features/DS_PHR1A_201204040917388_FR1_PX_E018N04_0709_01211?of=geojson&sk=...
  • Casual designation, KML output:
    http://api.astrium-geo.com/catalog/data/features.svc/features/DS_PHR1A_201204040917388_FR1_PX_E018N04_0709_01211?of=kml&sk=...

SPOT 6 identifiers

A SPOT 6 identifier looks like “DS_SPOT6_201302171114555_FR1_FR1_FR1_FR1_W016N11_01546”.
It is made of 10 fields:

  • DS_SPOT,
  • < satellite number>: at present 6, 7 coming soon;
  • < datastrip acquisition start time>: given in UTC time, 2013/02/17 11h14m55’05 in this example,
  • <initial image facility center acronym>,  “FR1” for instance,
  • <programmed image facility center acronym>,  “FR1” for instance,
  • <initial receiving station acronym>,  “FR1” for instance,
  • <programmed receiving station acronym>,  “FR1” for instance,
  • <spectral mode>, “PX” (order options indicate which product is asked: Panchromatic, Multispectral or Pan-sharpened),
  • <closest square degree of the strip center>, ex. “W016N11”,
  • <number of source frames>

The global pattern is:
DS_SPOT<satellite number>_<starting date of the segment acquisition, YYYYMMDDHHMMSSS>_<initial image facility center acronym>_<programmed image facility center acronym>_<initial receiving station acronym>_<programmed receiving station acronym>_<segment center coordinates rounded to the nearest degree values>_<number of source frames>

Example

Here are some possible feature links:

  • Casual designation, JSON output:
    http://api.astrium-geo.com/catalog/data/features.svc/Features/DS_SPOT6_201302171114555_FR1_FR1_FR1_FR1_W016N11_01546?sk=...
  • Casual designation, GeoJSON output:
    http://api.astrium-geo.com/catalog/data/features.svc/Features/DS_SPOT6_201302171114555_FR1_FR1_FR1_FR1_W016N11_01546?of=geojson&sk=...
  • Casual designation, KML output:
    http://api.astrium-geo.com/catalog/data/features.svc/Features/DS_SPOT6_201302171114555_FR1_FR1_FR1_FR1_W016N11_01546?of=kml&sk=...