Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[REFACTOR] Don'e keep both locationreferences and geometry #328

Open
4 tasks done
e-lo opened this issue Apr 29, 2023 · 1 comment · May be fixed by #327
Open
4 tasks done

[REFACTOR] Don'e keep both locationreferences and geometry #328

e-lo opened this issue Apr 29, 2023 · 1 comment · May be fixed by #327
Assignees
@e-lo
Labels
enhancement New feature or request
Milestone
v1.0

Comments

@e-lo
Copy link
Collaborator

e-lo commented Apr 29, 2023 •
edited

User Story

As a developer and user there should be a single place to access geometry data

Status

  • Defined
  • Planned
  • Implemented
  • Tested

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.
@e-lo e-lo added the enhancement New feature or request label Apr 29, 2023
@e-lo e-lo added this to the v1.0 milestone Apr 29, 2023
@e-lo e-lo self-assigned this Apr 29, 2023
@e-lo e-lo linked a pull request Apr 15, 2024 that will close this issue
V1 Refactor RC #327
Draft
@e-lo
Copy link
Collaborator Author

e-lo commented Apr 15, 2024

Currently fixed in branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@e-lo e-lo

Labels
enhancement New feature or request
Projects
None yet
Milestone
v1.0
Development

Successfully merging a pull request may close this issue.

V1 Refactor RC wsp-sag/network_wrangler
1 participant
@e-lo