NYCPlanning / NYCPlanning/data-engineering

DE<>GIS: COLP Packaging

Open
#351 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

db-colp
Dominant language
Python
Stars
43
Forks
3
Avg merge
23h 3m
Merged PRs (30d)
44

Description

Automate the transformations that GIS applies to COLP, as outlined here

Macro Steps:

  • Pull from publishing folder on Digital Ocean
  • Apply transformations
  • Validate Data
  • Output to new bucket

Individual Transformations to call out:

  • (Item 4) "XLSX: Convert csv to xlsx. IMPORTANT:This must be done carefully to avoid corrupting data that must retain leading zeros" (AR note: I assume this will happen automatically when we automate this. But maybe not)
  • (Item 6) "Confirm/Review data schema is the same as previous version
    No missing geographic values (i.e. Borough, CD, etc)
    No blank values in feature class, should be “null” instead "
  • (Item 8) Generate README pdf from sharepoint. Should this reside in (perhaps) markdown in our github repo?
  • (Item 10) "update GDB and SHP metadata, Import metadata from previous version to GDB, Update citation publication date to last day of month (i.e. 6/30/2022)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked GIS Open Data Update Cycle Instructions and the unchecked macro steps: pull from the publishing folder, apply transformations, and output to a new bucket. Then review Item 10 for GDB and SHP metadata requirements. Done means the listed transformations are automated while preserving the validated schema and geographic values.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.