We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As a developer and user there should be a single place to access geometry data
med
low
Remove in-memory storage of locationReferences in geodataframe b/c duplicative with geometry field. Transfer to/from geometry instead.
The text was updated successfully, but these errors were encountered:
Currently fixed in branch.
Sorry, something went wrong.
Implemented in v1 branch. Allows location references to be there as optional and will validate them to their data model.
e-lo
Successfully merging a pull request may close this issue.
User Story
As a developer and user there should be a single place to access geometry data
Status
Priority
med
Level of Effort
low
Resolution Ideas
Remove in-memory storage of locationReferences in geodataframe b/c duplicative with geometry field. Transfer to/from geometry instead.
The text was updated successfully, but these errors were encountered: