Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify pavementedge_carto delivery #56

Open
mattyschell opened this issue Jun 27, 2024 · 0 comments
Open

clarify pavementedge_carto delivery #56

mattyschell opened this issue Jun 27, 2024 · 0 comments

Comments

@mattyschell
Copy link
Member

The capture rules say that only 2 fields will be delivered for pavementedge_carto. They are VISIBILITY and STATUS.

VISIBILITY
Update from imagery, provided reference data
Description:
Only pavement edges that cross other pavement edges or building footprints need attribution. All others can be left as NULL.
Values will be either:
“Show” – for top pavement edge feature representing the roadway that is fully visible in the aerial imagery.
“Hide” – for pavement edge feature that is obscured by either pavement edge or building footprint feature that is above it.

STATUS
Calculated
Description
Field indicating the feature status as it fits into one of the following categories:
a) NEW. A feature captured for the first
time during the 2014 planimetrics update project.b) UPDATED. The feature existed previously but has been updated during the 2014 planimetrics update project.
c) UNCHANGED. The feature is unchanged
from the source planimetrics database.

What was actually delivered is Z_CENTER, Z_START, Z_END, and pos_yitz. pos_yitz was our internally generated column from 2016 planimetrics that we used to symbolize the NYC basemap. It looks like the vendor went ahead and updated this column correctly and pos_yitz is useable for cartographic symbolization in 2022 despite its odd name.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant