-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support proj:wkt2
if proj:epsg
is null
#67
Comments
I was intentional to only use I think there are a number of places where we'd have to change logic to switch I'm open to a PR doing this, but I'd also like to hear your thoughts on the design. CRSs are a mess that I'm hesitant to wade into without a good plan. As I've said in other places, my extremely strong preference would be for some other library (geoxarray?) to define the data model and provide all the utility functions (like our current |
This is an important issue for us. Some reference systems that are frequently used are not defined by an EPSG number such as all those defined with an ESRI: code (https://spatialreference.org/ref/esri/). EPSG doesn't have, for example, an equal area projection for North or South America. |
Yes, does ESRI:102008 work? Never had cause to use this one. |
I think only EPSG codes are recognized by stackstac, so I wouldn't know how to enter an ESRI: code. Just entering 102008 doesn't work. |
As an example, see this Landsat Albers scene from the Landsat Collection 2 STAC API:
https://ibhoyw8md9.execute-api.us-west-2.amazonaws.com/prod/collections/landsat-c2l2alb-sr/items/LC08_L2SR_082024_20210806_20210811_02_A1_SR
I hacked stackstac to accept any CRS string in the
epsg
keyword rather than requiring an EPSG code which is basically just handing it along here:stackstac/stackstac/prepare.py
Line 515 in c431e09
Would be good to follow the same logic here that the new GDAL STAC Item driver does:
OSGeo/gdal#4138
which allows for:
![image](https://user-images.githubusercontent.com/1416900/129248946-a4d99589-b5e0-4430-b5f2-51324275ca4f.png)
Rather than drop the epsg code may be better to add deprecation warning, and add a new
crs
keyword. When parsing the STAC it can then construct the right CRS based on what is available for the Item/Asset.@gjoseph92 I'm happy to issue a PR for this, lmk if I should, don't want to duplicate work if you had already been working on this.
The text was updated successfully, but these errors were encountered: