CSCL - GR/GSS lion gdb postprocessing

Open
#2,054 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Start with the standalone Python script that JD will share and identify how it uses Esri packages. Review the pipeline entry point where this transformation should be incorporated. Done means reproducing the node outputs and street-name lookup, removing floating nodes, and generating the preferred-record and missing-segment reports described in the issue.

Written by the indexing model from the issue text.

Description

db-cscl

Questions

  • are there steps taken before this is run? Nope
  • is the gdb prior to postprocessing script needed/used in any way? Nope

Notes from meeting

What the tool does

  • main data outputs in gdb:
    • node feature class
    • node-streetname lookup table
  • CSCL has a lot of "floating" nodes
  • script deletes floating nodes, only keeps nodes which are connected to segments
  • generate streetname associated with Node
    • only take preferred streetnames
  • generate report of "Y" preferred lgc records with no b7sc
  • generate report of "missing" segments - exists in intersections table but not CSCL

Tool in this case is a standalone python script that uses esri packages. We will incorporate this transformation into the pipeline.

There is no documentation for this specific transformation, but JD will share the code

Dominant language
Python
Stars
2
Forks
0
Avg merge
13h 8m
Merged PRs (30d)
138

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from NYCPlanning/data-engineering

All issues in NYCPlanning/data-engineering

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.