Expand capability of geojson class #694
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vtnate
commented
Jan 15, 2025
| pass | ||
|
|
||
|
|
||
| # TODO: Inherit from GeoJSON Feature class, move to its own file |
There was a problem hiding this comment.
I'm now importing this class back into urbanopt_geojson, not inheriting. Is that the right pattern we should use?
nllong
approved these changes
Jan 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Any background context you want to provide?
The urbanopt-des repo has a geojson parsing class as well as the one in the GMT. Combining them should DRY up some code. Updating the uo-des version is accomplished in urbanopt/urbanopt-des#8.
What does this PR accomplish?
How should this be manually tested?
CI is sufficient