NYCPlanning / NYCPlanning/data-engineering
DE<>GIS: Flow for DO -> Bytes
Open
Nobody has claimed this yet.
GIS
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Currently, publishing to BYTES is a manual process involving email. This should be automated, either by having BYTES point straight to Digital Ocean, or by automating a push to wherever BYTES hosts data.
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
No files, tests, or entry points are named. Start by tracing the current email-based publishing process and documenting where BYTES hosts the data; done means publishing to BYTES is automated through an agreed DigitalOcean or hosting workflow.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100