You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only change in 1.0.0-beta2 that we need to worry about is support for null geometries. The specific case to allow them that's mentioned in best practices is "in progress" satellite data. GeoTrellis doesn't decode null as a geometry, though maybe it should? I'd strongly prefer to pretend this never happened, continue to require a geometry and bbox, (you can provide Null Island and update with the transactions extension in Franklin if you really need this or fill in with your existing metadata, if that's how it's supposed to work, for static catalog). At least that's my preference over "both required or both null".
The text was updated successfully, but these errors were encountered:
The only change in 1.0.0-beta2 that we need to worry about is support for
null
geometries. The specific case to allow them that's mentioned in best practices is "in progress" satellite data. GeoTrellis doesn't decodenull
as a geometry, though maybe it should? I'd strongly prefer to pretend this never happened, continue to require a geometry and bbox, (you can provide Null Island and update with the transactions extension in Franklin if you really need this or fill in with your existing metadata, if that's how it's supposed to work, for static catalog). At least that's my preference over "both required or both null".The text was updated successfully, but these errors were encountered: