-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
CRS correctness #80
Comments
Perhaps error with a way to opt out if it is another defined CRS, and accept when there is no CRS or CRS WGS84.
|
Error with manual override sounds best to me. But do we attach the crs following the old api if users force it? |
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. |
Yeah easier for us for sure. I guess people can use GDAL if they want the old standard and to actually write the crs. |
#sdsl23
We should at least warn if you provide a spatial thing with a (defined?) crs other than wgs84.
The text was updated successfully, but these errors were encountered: