Skip to content
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

CRS correctness #80

Open
evetion opened this issue Sep 18, 2023 · 4 comments
Open

CRS correctness #80

evetion opened this issue Sep 18, 2023 · 4 comments

Comments

@evetion
Copy link
Member

evetion commented Sep 18, 2023

#sdsl23

We should at least warn if you provide a spatial thing with a (defined?) crs other than wgs84.

@visr
Copy link
Member

visr commented Sep 18, 2023

Perhaps error with a way to opt out if it is another defined CRS, and accept when there is no CRS or CRS WGS84.

However, where all involved parties have a prior arrangement, alternative coordinate reference systems can be used without risk of data being misinterpreted."

@rafaqz
Copy link
Member

rafaqz commented Sep 19, 2023

Error with manual override sounds best to me.

But do we attach the crs following the old api if users force it?

@visr
Copy link
Member

visr commented Sep 19, 2023

I'd say no, at least not without explicitly opting in to writing the old standard, if we ever decide to support it. It's simpler for us to stick to the RFC standard.

@rafaqz
Copy link
Member

rafaqz commented Sep 19, 2023

Yeah easier for us for sure. I guess people can use GDAL if they want the old standard and to actually write the crs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants