-
Notifications
You must be signed in to change notification settings - Fork 14
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 not associated with geometries? #114
Comments
Yes, there are no crs fields in the objects here. We could add them to most, but probably not to points. And I guess strings are not actually copied/inlined for every polygon they are attached to? Its just a pointer to the same string underneath? |
I think so? Strings are heap allocated, so presumably yes, and |
Yes, I just checked and the pointer to the strings is the same for multiple geometries initialized with the same CRS object. |
Maybe it's a bad idea, but we could just wrap every Shapefile geometry as a GI geometry when they're returned from |
Hmm maybe that will just work? But its a weird nested object in terms of default types. I think adding a field is better. |
I guess we would add a |
Ah right that's kind of annoying but yes probably And pass the crs through |
When loading a Shapefile with defined CRS, the individual geometries always have
GI.crs(geom) === nothing
, even thoughGI.crs(table) isa GeoFormatTypes.ESRIWellKnownText
. Would this need some form of refactor to store CRS in geometry as well?The text was updated successfully, but these errors were encountered: