-
Notifications
You must be signed in to change notification settings - Fork 0
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
Make empty CRS possible #29
Comments
What is the engineering CRS? Do you have a reference? |
engineering CRS means it can be anything, but is metric (distances in Euclidian space, not angles). See e.g. Iliffe & Lott |
Thanks, that goes on my reading list. |
So to calarify: we need no-arg constructors that insert the engineering crs for epsg/wkt/proj etc ? |
The engineering CRS (wkt in geopandas issue) needs to be inserted when you write a GPKG using GDAL and you want to avoid that GDAL sets a long/lat, geodetic coordinates CRS to the GPKG, which it does by default. Whether you want to use that WKT more general is up to you; R/sf uses an |
Yeah sorry was unclear, that was more a technical question for @evetion about the issue as Im not sure what is actually actionable here. Users/other packages like ArchGDAL/Rasters can already construct such a wkt to pass to gdal manually, the question is if the idea is to make that easy with no-arg constructors. So e.g. |
Yeah, so either always use the eng.crs. when unknown, or use an NA one (unknown) and only set eng.crs when writing to file? Relates to #30 as well (spherical/cartesian) as type parameter. |
#sdsl23
And set it to the engineering crs?
The text was updated successfully, but these errors were encountered: