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

GIN_ADM1 gbOpen #2958

Merged
merged 1 commit into from
Aug 31, 2023
Merged

GIN_ADM1 gbOpen #2958

merged 1 commit into from
Aug 31, 2023

Conversation

rohith4444
Copy link
Collaborator

Why do we need this boundary?

Anything Unusual?

@github-actions
Copy link

Hello! I am the geoBoundary Bot, and I just did an initial check on your submitted files.

I will automatically re-run my checks when you edit your Pull Request, and provide the new results in a comment just like this.
Once all of your files meet my programmed standards, I will flag your file for a manual human review.
=========== Submission Findings ===========

Full logs for fileChecks

Full logs for geometryDataChecks

Full logs for metaChecks

All checks have passed! I'll flag your boundary submission for a manual review by one of my humans.
Preview

@DanRunfola DanRunfola merged commit c8b2878 into wmgeolab:main Aug 31, 2023
4 checks passed
@rohith4444 rohith4444 deleted the aug_30_3 branch September 14, 2023 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@rohith4444 @DanRunfola