NYCPlanning / NYCPlanning/data-engineering
Zoning Map Amendments geometries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
the CEQR data product build fails because it expects all records in dcp_zoningmapamendments to be multipolygons. but one record is a Geometry Collection
for now, pinned the version in CEQR data hub to 20250430
the lates version of
dcp_zoningmapamendmentsis20251031. we get it fromedm-publishing/datasets/and we have the latest version archivedthe
Inwood Rezoningrecord has a geometry type ofST_GeometryCollection. every other record isST_MultiPolygonthe Geometry Collection has two geometries in it and they somehow seem identical on a map: Polygon and LineString. I wouldn't have guess that a LineString could render as a polygon
in the Feature Layer(bytes, feature page, geojson page), the record seems to just have the Polygon geometry
Originally posted by @damonmcc in #2069
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 CEQR data product build and comparing the archived 20251031 dcp_zoningmapamendments record for Inwood Rezoning with the 20250430 version and the linked feature and GeoJSON pages. Done means the build accepts the current dataset without pinning to 20250430 and the record has the intended geometry type.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100