GeoDaCenter / GeoDaCenter/data-and-lab
Sample data template
- Dominant language
- No language data
- Stars
- 1
- Forks
- 2
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
If you can use this template for the sample data (we'll use the same thing for the labs afterwards):
https://geodacenter.github.io/data-and-lab/
The webpage is in the branch "gh-pages":
https://github.com/GeoDaCenter/data-and-lab/tree/gh-pages
The idea is to add all of the sample data on our current page: https://spatial.uchicago.edu/sample-data
with the new data you put together (https://uchicago.app.box.com/folder/15959242415) and make it easier to access through the new template.
To query it, we need to categorize the data, e.g. by:
- map type (polygons or points, later also networks)
- time dimension present (cross-section or multi-year)
- year(s)
- rates (event and base)
- size (<100, <5,000, <50,000, 50k+)
- country
- city
- topic (e.g. crime, housing, health, agriculture, etc.)
- spatial resolution (e.g. address, block, tract, county, country, ...)
- GeoDa analysis type (ESDA, regression, averages chart, etc.: I can add this in the end)
- type of example (toy like columbus or real - I can add this in the end, too)
Once we have the tags, we can filter the datasets flexibly. If you can take a look at the repo and the data page (e.g.: https://geodacenter.github.io/data-and-lab/how-to-use/) and readme file to see what questions you have for implementing this, then we can meet and resolve them and decide which details to highlight in the summary (e.g. thumbnail images of the map and table). I also requested accounts for us on our new RCC server so we can store the data there.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the gh-pages branch, the existing data page, the how-to-use page, and the README in the data-and-lab repository. Clarify the dataset sources, tagging fields, summaries, and RCC storage plan with the maintainer before implementation. Done means the sample data is accessible through a filterable page using the agreed categories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- content, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100