Santa Cruz County, California: Difference between revisions

[[user:DanHomerick]] imported the Stream.shp layer of the [http://sccftpmap.co.santa-cruz.ca.us/File%20Download%20Site/Hydrography/Shapefiles/Hydrography.zip Hydrography] dataset from the [http://gis.co.santa-cruz.ca.us/ Santa Cruz GIS site] in October 2009. He used the Java program [http://redmine.yellowbkpk.com/projects/list_files/geo shp-to-osm-0.6.1] to convert the data from Shapefile format to OSM format and [https://svn.openstreetmap.org/applications/utils/import/bulk_upload_06 bulk_upload.py] to upload it. Since, at the time of the import, shp-to-osm does not connect line segments he used the Validator plugin in JOSM to merge overlapping nodes. This connected many stream segments correctly, but left some unconnected at import time. Existing rivers were not programatically deleted, instead preferring to rely on manual verification before their deletion. Many imported streams were initially pointing the wrong direction (a way with a stream/river tag should point downstream). Work is underway to correct issues with the import: corrections to wrong-direction waterways are mostly complete as of Feb. 2010. However, as of May 2014, JOSM's Validator plugin reports many unconnected stream endpoints where they conjoin other streams. A note about the tags used: many of the streams were listed as type "swale" (a low lying area) in the original dataset. These were translated as {{key|waterway||stream}} + {{key|intermittent||yes}} + {{key|note||swale}} for the upload, but in many cases, especially near the mouth of a stream, a swale may not actually have intermittent flow. As {{key|intermittent||yes}} now appears to affect the Mapnik rendering (with a dashed light blue line), the tag should be deleted on ways where it is inaccurate.