NYCPlanning / NYCPlanning/data-engineering
PLUTO file metadata
Open
Nobody has claimed this yet.
db-pluto
GIS
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
GIS currently applies metadata to PLUTO files using code that requires an ESRI license. We'd like to apply the same metadata without that dependency and during the build so that GIS doesn't have to modify files DE generates.
success criteria
- all shapefiles have metadata applied to them during the build
- all FGDBs have metadata applied to them during the build
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 locating the GIS code that currently applies metadata to PLUTO files and the build steps that produce shapefiles and FGDBs. Trace how both output types are generated, then verify that metadata is applied during the build without requiring the ESRI-licensed dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100