nationalparkservice / places-data

Data from the Places system.
http://www.nps.gov/npmap/tools/places/
13 stars 5 forks source link

BLCA/CURE data from IMR #212

Open chadlawlis opened 8 years ago

chadlawlis commented 8 years ago

From Darcee, 10/26.

Please replace all the data you currently have in Places with this data.

Points of interest, roads, trails, and parking. Buildings available later via FMSS. Data here.

jakecoolidge commented 8 years ago

Will seed this directly from REST services, following the ZION example.

jakecoolidge commented 8 years ago

We'll convert POILABEL as the name field (POINAME was used in Zion). I just spoke with Eric, and this is a field they're maintaining that's optimized for map display. In other words, this is the name that should appear in PT3 when a POI is clicked.

Also, BLCA and CURE are jointly managed, so the data for the two parks travel together in the REST service.

jakecoolidge commented 8 years ago

Seeding using this service

Tag conversions (attributes not converted were deleted)

POI

POINAME name POITYPE deleted after each unique value received appropriate tags

POILABEL alt_name UNITCODE nps:unit_code (values converted to lowercase) GEOMETRYID nps:source_system_key_value NOTES nps:notes added nps:source_system_key: GEOMETRYID added nps:source_system=ZION FeatureService POI

Trails

added highway:path UNITCODE nps:unit_code (values converted to lowercase) NOTES nps:notes TRLNAME name TRLALTNAME alt_name TRLUSE deleted after adding appropriate uses

added nps:source_system=ZION FeatureService Trails No Multipart primary key not provided

Roads

added highway:road (road classifications not provided) RDNAME name added nps:source_system=ZION FeatureService Roads primary key not provided

Parking

added amenity:parking Name name GEOMETRYID nps:source_system_key_value added nps:source_system=ZION FeatureService Parking added nps:source_system_key=GEOMETRYID