Return correct geojson for polygons and geotrace data #2348
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
FrankApiyo
force-pushed
the
return-correct-geojson-for-polygons-and-geotrace-data
branch
3 times, most recently
from
84689f7
to
b360227
Compare
DavisRayM
previously approved these changes
Jan 9, 2023
FrankApiyo
changed the title
FrankApiyo
force-pushed
the
return-correct-geojson-for-polygons-and-geotrace-data
branch
5 times, most recently
from
709ce49
to
f1695e1
Compare
KipSigei
previously approved these changes
Jan 25, 2023
FrankApiyo
force-pushed
the
return-correct-geojson-for-polygons-and-geotrace-data
branch
from
f1695e1
to
fa619e3
Compare
KipSigei
approved these changes
Jan 27, 2023
FrankApiyo
deleted the
return-correct-geojson-for-polygons-and-geotrace-data
branch
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.
Changes / Features implemented
Steps taken to verify this change does what is intended
Side effects of implementing this change
Before submitting this PR for review, please make sure you have:
Closes #2350