| ASCENDING_DESCENDING |
STRING |
Describes whether the satellite travel direction was ascending towards the north pole, or descending towards the south pole. |
ASCENDING, DESCENDING |
sat:orbit_state |
https://github.com/stac-extensions/sat |
| TRACK_NUMBER |
INT |
The track describes a path the satellite will follow over the earth similar to longitude; each path has an assigned number. Combined with a frame number it identifies a specific piece of ground. May also be referred to as relative orbit or path number. |
10, 109, 11, 17, 18, … |
sat:relative_orbit |
https://github.com/stac-extensions/sat |
| FRAME_NUMBER |
INT |
The designated frame or scene as defined by the mission or project. A frame typically describes a fixed geometry over the Earth at a fixed location. |
13, 139, 14, 140, 141, … |
nisar:frame_number |
|
| FREQUENCIES |
STRING |
The frequencies found in the data product (A, B, or both). NISAR is a dual-frequency mission. |
A, B |
-> discard |
https://github.com/stac-extensions/sar |
| FREQUENCY_A_POLARIZATION |
STRING |
Polarization of Frequency A. Radar transmissions are polarized, with components normally termed vertical (V) and horizontal (H). Vertical means that the electric vector is in the plane of incidence; horizontal means the electric vector is perpendicular to the plane of incidence. |
HH, HV, VV |
sar:polarizations AND nisar:a_polarizations |
https://github.com/stac-extensions/sar |
| FREQUENCY_B_POLARIZATION |
STRING |
Polarization of Frequency B. Radar transmissions are polarized, with components normally termed vertical (V) and horizontal (H). Vertical means that the electric vector is in the plane of incidence; horizontal means the electric vector is perpendicular to the plane of incidence. |
HH, HV, VV |
nisar:b_polarizations |
|
| FREQUENCY_A_POLARIZATION_CONCAT |
STRING |
Concatenated list with plus signs of the frequency A polarization. |
HH, HH+HV, VV |
-> discard |
|
| FREQUENCY_B_POLARIZATION_CONCAT |
STRING |
Concatenated list with plus signs of the frequency B polarization. |
HH, HH+HV, VV |
-> discard |
https://github.com/stac-extensions/sar |
| FREQUENCY_A_RANGE_BANDWIDTH |
INT |
The range bandwidth of frequency A. |
20, 40, 5 77 |
sar:bandwith (transformed in ghz) and nisar:a_bandwith |
https://github.com/stac-extensions/sar |
| FREQUENCY_B_RANGE_BANDWIDTH |
INT |
The range bandwidth of frequency B. |
5 |
nisar:b_bandwith |
|
| RANGE_BANDWIDTH_CONCAT |
STRING |
Concatenated list with plus signs of the frequency A and B range bandwidth. |
20+5, 40+5, 5, 5+5 |
-> discard |
|
| FULL_FRAME |
STRING |
Indicates if the frame coverage is either full or partial. |
FALSE, TRUE |
nisar:full_frame (converted to boolean) |
|
| JOINT_OBSERVATION |
STRING |
Indicates whether the granule was observed jointly with the L-Band and S-Band instrument. For interferometric products this value is True if either the reference or secondary granule is a joint observation. |
FALSE, TRUE |
nisar:joint_observation (converted to boolean) |
|
| ORBIT_TYPE |
STRING |
The accuracy or fidelity of the orbit ephemeris data used to produce the product, where FOE=Forecast Orbit Ephemeris, NOE=Near real-time Orbit Ephemeris, MOE=Medium precision Orbit Ephemeris, and POE=Precise Orbit Ephemeris. |
MOE |
nisar:orbit_type (or is it more about product timeliness categroy?) https://nisar-docs.asf.alaska.edu/orbit-ephemeris/ |
https://github.com/stac-extensions/processing |
| PROCESSING_LEVEL |
STRING |
Indicates how much processing has been done to the data. Examples include L0 (Level 0), L1 (Level 1), L2 (Level 2). |
L1, L2, L3 |
processing:level |
https://github.com/stac-extensions/product |
| PRODUCT_TYPE |
STRING |
Indicates the type of product. |
RSLC, GSLC, GCOV, … |
product:type |
https://github.com/stac-extensions/product |
| PRODUCT_TYPE_DESC |
STRING |
Description of the product type. |
Range Doppler Single Look Complex, … |
-> discard |
|
| PRODUCT_VERSION |
STRING |
Version of the product. |
1.0.2 |
processing:version |
https://github.com/stac-extensions/processing |
| PRODUCTION_PIPELINE |
STRING |
Indicates whether the product was created as part of nominal data processing, urgent response processing, or customized on-demand processing. |
PR |
processing:lineage (could also be the software) |
https://github.com/stac-extensions/processing |
| PROCESSING_CENTER |
STRING |
Processing center of the granule. |
JPL |
processing:facility |
https://github.com/stac-extensions/processing |
| STACK_ID |
STRING |
An ASF generated identifier to allow grouping of data over a specific location. |
005_077_D, 005_A_013, … |
nisar:stack_id |
|
| INPUT_RCID |
STRING |
The radar configuration mode of the input Level 0B granule(s). |
148, 151, 153, … |
nisar:input_rcid |
|
| REFERENCE_ZERO_DOPPLER_START_TIME |
DATETIME_STRING |
Zero doppler start time of the reference acquisition. |
2025-10-17T12:48:36Z, … |
insar:reference_datetime |
https://github.com/stac-extensions/insar |
| REFERENCE_ZERO_DOPPLER_END_TIME |
DATETIME_STRING |
Zero doppler end time of the reference acquisition. |
2025-10-17T12:48:57Z, … |
-> discard |
|
| SECONDARY_ZERO_DOPPLER_START_TIME |
DATETIME_STRING |
Zero doppler start time of the secondary acquisition. |
2025-10-29T12:48:36Z, … |
insar:secondary_datetime |
https://github.com/stac-extensions/insar |
| SECONDARY_ZERO_DOPPLER_END_TIME |
DATETIME_STRING |
Zero doppler end time of the secondary acquisition. |
2025-10-29T12:48:58Z, … |
-> discard |
|
| ORBIT_NUMBER |
INT |
The absolute orbit number. |
1073 |
sat:absolute_orbit |
https://github.com/stac-extensions/sat |
| LOOK_DIRECTION |
STRING |
The direction the instrument was looking (LEFT or RIGHT). |
LEFT |
sar:observation_direction |
https://github.com/stac-extensions/sar |
| CRID |
STRING |
Composite Release ID, A version identifier to identify the version of the software and the environment of the software development. It is maintained by ISRO-NISAR Data Product Generation Software, and is part of the filename and part of product for all Level-1 and Level-2 products |
X05010 |
processing:software |
https://github.com/stac-extensions/processing |
| PGE_VERSION |
STRING |
Product Generation Executable version. |
R05.00.8 |
processing:software |
https://github.com/stac-extensions/processing |
| SAS_VERSION |
STRING |
Science Algorithms Software version. |
ISCE3 0.25.7 |
processing:software |
https://github.com/stac-extensions/processing |
| PRODUCT_COUNTER |
INT |
Product Counter is used to version data products that are generated multiple times. The counter starts with 001 and increments for subsequent generation of the same granule of any particular product type. It is reset to 001 upon deployment of a new CRID, or change in product accuracy, or product coverage. Product Counter is referred to as CTR in the file naming conventions. The CTR will be incremented based on full file naming convention which includes the CRID |
1 |
nisar:product_counter (not clear to me if this includes a deprecation of the previous one) |
|
| PGE_NAME |
STRING |
Product Generation Executable name. |
INSAR_L_PGE |
processing:software (trouble to find documentation on it, but it might be the indicator which software "stack" is used for the processing) |
https://github.com/stac-extensions/processing |
Hello,
I wanted to know if there are any plans from NASA and/or ASF to come up with an official STAC mapping for the new upcoming satellite. Currently there are no properties exposed in the CMR stac endpoint. Would be nice to see if there is a working together with the STAC community to define an offical mapping to make it easier for others.
As we have an internal STAC catalog I already did some mapping of the properties of the umm json response to stac properties. I probably miss a few or there is something to improve. Looking forward to any feedback