Allow skipping GeoJSON validation #681
Merged
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
approved these changes
Dec 16, 2024
|
at some point we should fix the issue that we have two GeoJSON classes. One in the GMT and one in URBANopt-DES. I think the only logically approach is to have UO-DES use the version in GMT... so we'd have to move some functionality over to GMT. Thanks for reviewing this so quickly! |
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?
In some cases, the GeoJSON can contain extra information that is not problematic with the generation of the DES systems.
What does this PR accomplish?
How should this be manually tested?
Code review should suffice