eodash / eodash/eodash_catalog
Replicate GeoDB handler logic to tipg-ingested time series data
- Dominant language
- Python
- Stars
- 3
- Forks
- 3
- Avg merge
- 14m
- Merged PRs (30d)
- 5
Description
It would be useful to have a new collection type to match our way how we ingest data to tipg to remove the need to generate the TimeEntries manually https://github.com/GTIF-Austria/public-catalog/blob/4ed39b46c786c66e7dbd14ff17735ad8228ae6c3/collections/mobility_daily_traffic.json#L29
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the requested collection type with the GeoDB handler logic and the referenced collections/mobility_daily_traffic.json example, especially its TimeEntries configuration. Determine the entry point for collections ingested through tipg and define what metadata can be generated automatically; done means the new type handles tipg-ingested time series without manually generated TimeEntries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100