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.

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

Investigate ESRI Administrative Boundaries #219

Open
5 tasks
Tracked by #221
OhmSpectator opened this issue Jul 11, 2024 · 3 comments
Open
5 tasks
Tracked by #221

Investigate ESRI Administrative Boundaries #219

OhmSpectator opened this issue Jul 11, 2024 · 3 comments
Assignees
Labels
deploy Issues related to the deployment process enhancement New feature or request

Comments

@OhmSpectator
Copy link
Member

OhmSpectator commented Jul 11, 2024

Description

Explore the ESRI Administrative Boundaries as a potential data source for the "Track Your Regions" project. Given the issues encountered with GADM, it is crucial to evaluate alternative sources that might offer more accurate, up-to-date, and reliable geospatial data.

Requirements

List the specific, verifiable requirements for this task/enhancement. Each requirement should be clear and concise, allowing for straightforward verification from a Pull Request.

  • Check the license
  • Research the coverage and accuracy of ESRI Administrative Boundaries data.
  • Compare the data granularity with that of GADM.
  • Evaluate the frequency and reliability of data updates.
  • Assess the ease of integration with the current data model.
@OhmSpectator OhmSpectator added enhancement New feature or request deploy Issues related to the deployment process labels Jul 11, 2024
@OhmSpectator OhmSpectator self-assigned this Jul 11, 2024
@OhmSpectator OhmSpectator moved this from 🆕 New to 📋 Backlog in Track Your Regions Jul 11, 2024
@OhmSpectator OhmSpectator moved this from 📋 Backlog to 🆕 New in Track Your Regions Jul 11, 2024
@OhmSpectator
Copy link
Member Author

In the metadata it's said that Garmin was used as a source of this data:

Source citation:
Title: Admin_Boundaries, Country_Boundaries, Hydropolys
Alternate titles: World Base Map 2021
Citation date:
Date type: publication
Date: 2021-12-01T00:00:00
Edition: 2021
Cited responsible party:
Role: originator
Responsible party:
Organization:
Name: Garmin International, Inc.

@OhmSpectator
Copy link
Member Author

OhmSpectator commented Jul 11, 2024

Also from the metadata:

Process description: The following steps were performed by Esri: Extracted the file geodatabase (.gdb) feature class from the subset of World Base Map. Removed all first-level administrative subdivisions. Updated country names as needed. Ran the Erase tool using polygons from the World Base Map Hydropolys feature class to remove the areas that represent seas and large lakes that cross international borders. Added the fields COUNTRY and CONTINENT and coded them from source fields in the World Base Map Country_Boundaries feature class. Added the field ISO_CODE and coded it by combining the values of the fields ISO_CC and ISO_SUB. Added the field ADMINTYPE and coded it by removing the administrative types from the field NOTES. Added the fields LAND_TYPE and LAND_RANK and manually determined their values from the Shape_Area field. Deleted fields not needed. Dissolved on all fields to make multipart features for the fields LAND_TYPE and LAND_RANK.

@OhmSpectator
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy Issues related to the deployment process enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant