SLE_ADM1 gbOpen #4232
Open
SLE_ADM1 gbOpen #4232
Conversation
This file contains hidden or 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
|
Hello! I am the geoBoundary Bot, and I just did an initial check on your submitted files. |
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.
Boundary data for SLE-ADM1 submitted through the geoBoundaries contribution form.
Name: Elizabeth Ott.
Affiliation: geoBoundaries.
Contact: ejott04@hotmail.com.are files validated before they are uploaded to GitHub? Are there protections to ensure that the only expected file types/content can be uploaded?
Notes about these data: Boundaries created from merging ADM2 boundaries together, and date is representative of ADM2 boundaries. Source listed (SimpleMaps) was used as a reference for region boundaries and names.