midas-network / midas-network/midas-data
Geographical information
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 3
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 2
Description
In the ontology, we currently have:
- geographical resolution: Level of details of the location: ADMIN0, ADMIN1, Country, State, … (can be multiple).
- geographical scope: Name of the location in English at country or ADMIN1 level corresponding from GEONAMES (if more than 10 different countries possible "Earth" can be used).
The resolution definition can be used and might not to be updated, also if we use geonames, do you need to add each level as subclasses?
For the scope, do we need to use another definition as we not going to limit to earch, continent, country or admin 1 places, and we can use geonames for it
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ontology's current definitions for geographical resolution and geographical scope, then compare the proposed use of GeoNames with the stated country, continent, and ADMIN1 limits. Done means reaching a decision on the scope definition and whether geographical levels should be represented as subclasses, with the ontology updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100