-
Notifications
You must be signed in to change notification settings - Fork 29
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
New Feature: Non Geo Table Entities / Tables #62
Comments
Did you have a particular use case thats not supported at the moment? Tables should work, you can set the Feature to use an arbitrary geometry or the IGeometry type. It'd be similar to using a feature but not returning geometry from operations |
I am currently building an ORM on top of your library and not specifying the Geometry type would be useful is all because yes they do work, but not quite like id like.. Also ill own this one and would like to share the ORM feature with it if I can as well, look for a PR in the next little bit. |
I agree; it would be more intuitive and readable if one could say |
Incidentally, you cannot use A type that explicitly means "no geometry" and that implements IGeometry might be clearer than co-opting Extent or Point. Then to provide a friendly shorthand for the common case where geometry is not needed for the input or output, we could add something like |
In follow-up, I notice that the fork maintained by @dymaptic includes a NoGeometry implementation and some other features specific to tables (initially from commits by @hbindervitti) |
Need to abstract out the Feature to not include a IGeometry for basic table ops.
The text was updated successfully, but these errors were encountered: