Search ndvi_anomaly on 29th February 2000

Cloud cover percentage [0, 100] from:

Cloud cover percentage [0, 100] to (exclusive):

Landsat collection category, such as T1 or T2:

Time when dataset was created (processed) From

Time when dataset was created (processed) to (exclusive)

Coordinate reference system field:

How much data is in the scene from:

How much data is in the scene to (exclusive):

ID of a dataset type:

Derived product version number:

The ground sample distance from:

The ground sample distance to (exclusive):

Sun azimuth from:

Sun azimuth to (exclusive):

Sun elevation from:

Sun elevation to (exclusive):

File format (GeoTiff, NetCDF):

Dataset UUID:

User who indexed the dataset:

When dataset was indexed:

Instrument name:

Label:

Latitude range from:

Latitude range to (exclusive):

Longitude range from:

Longitude range to (exclusive):

Full metadata document:

Metadata type name of dataset:

ID of a metadata type:

Platform code:

Product family code:

African regional area:

Spatial reference code from the provider. For Landsat region_code is a scene path row '{:03d}{:03d}.format(path,row)'. For Sentinel it is MGRS code. In general it is a unique string identifier that datasets covering roughly the same spatial region share. :

Landsat root mean square error from:

Landsat root mean square error to (exclusive):

Landsat root mean square error in X from:

Landsat root mean square error in X to (exclusive):

Landsat root mean square error in Y from:

Landsat root mean square error in Y to (exclusive):

The satellite orbit state, either ascending or descending:

The satellite relative orbit from:

The satellite relative orbit to (exclusive):

Acquisition time range From

Acquisition time range to (exclusive)

Dataset URI:

Add field

No results.

Return to ndvi_anomaly on 29th February 2000 overview

ndvi_anomaly: Monthly NDVI Anomalies produced by Digital Earth Africa.

Products

2000

February

29th

No results.