radiantearth
Google Earth Engine extension (gee:)
The Earth Engine extension needs to eventually get more formal.
- Some parts maybe should migrate to other extensions.
- That which is already in other extensions should get dropped.
- What remains should get properly documented.
Currently, there are these tags:
- gee:bitmask
- gee:cadence
- gee:classes
- gee:climatological_interval
- gee:estimated_range
- gee:extra_dois
- gee:footer
- gee:offset
- gee:properties
- gee:revisit_interval
- gee:scale
- gee:schema
- gee:terms_of_use
- gee:type
- gee:unit
- gee:visualizations
- gee:wavelength
Two comments from when I last checked out the GEE STAC catalog:
- Is there a reason you use
gee:wavelengthinstead ofeo:full_width_half_max? - It seems like STAC items aren't served with any compression? Any reason not to serve JSON files with gzip or brotli compression?
- gee:bitmask: That could be solved by the raster or file extension, where you can give values.
- gee:cadence: Not sure. Is that the similar to gee:revisit_interval?
- gee:classes: I'm starting a classification extension soon, we can collaborate on that.
- gee:extra_dois: What is that? You could probably use sci:doi in summaries?
- gee:offset: I guess that is the same as in raster?
- gee:revisit_interval: I'm also interested in that. Maybe something to be integrated into timestamps? What values do you support in that field?
- gee:scale: Will be added to the raster extension, I think
- gee:schema: Seems GEE specific
- gee:terms_of_use: Why not use license and links?
- gee:type: seems GEE specific
- gee:unit: Will be added to the raster extension, I think
- gee:visualizations: Maybe the new composite / virtual assets extension covers your use case?
- gee:wavelength: Why not use the fields in eo:bands?
For all others I'm not sure what the fields are used for.
Some of what is currently in gee: extension fields should become fields from the Classification Extension Specification
https://github.com/stac-extensions/classification/issues/12
@schwehr We discussed this issue in STAC Working Session that the gee extension can be created if needed, but it is encouraged to utilize existing fields/tags wherever possible. Closing this issue.
