<div dir="ltr">Thank you all again for the assistance on this project, and especially Michael Patrick for turning me on to the <a href="http://www.vcgi.org/dataware/?page=./search_tools/search_action.cfm&query=theme&theme_id=018-9999">VCGI TransRoad_RDS</a> data.<br>
<div class="gmail_extra"><br></div><div class="gmail_extra">I've made some progress on this project and am <a href="https://wiki.openstreetmap.org/wiki/Vermont_road_surfaces">documenting it in the OSM wiki</a>. At this point I've done the data mapping sufficiently to generate a table of each way OSMID to its new surface tag and visualization of the proposed tag additions:<br>
<div style="margin-left:40px"><a href="http://www2.adamfranco.com/surface/vermont-proposed-surfaces.kmz">http://www2.adamfranco.com/surface/vermont-proposed-surfaces.kmz</a><br></div></div><div class="gmail_extra"><br></div>
<div class="gmail_extra">I've also contacted the VCGI about their data licensing and am waiting on a response.<br><br></div><div class="gmail_extra">At this point I have come up with a few questions for the community that I hope to get answered before moving further:<br>
<ul><li>As I've <a href="https://wiki.openstreetmap.org/wiki/Vermont_road_surfaces#Tag_mapping">described in the wiki</a>, the VCGI data separately identifies "Soil or graded/drained earth" and "unimproved/primitive" surfaces. While the <a href="https://wiki.openstreetmap.org/wiki/Key:surface">OSM Wiki describes</a> a number of possible surface values, the Potlatch editor only lists Sand, Gravel, Dirt, and Grass as options for unpaved surfaces. "Soil or graded/drained earth" seems like it maps well to "Dirt", but "unimproved/primitive" seems like it would map better to "earth" or "ground" rather than one of the options presented by Potlatch.<br>
<br>Should I use the "earth" or "ground" value or limit myself to one of those suggested by Potlatch?<br><br></li><li>Is there a preferred process for scripting tag additions/updates? <br><br>Reading through the <a href="https://wiki.openstreetmap.org/wiki/JOSM_file_format">JOSM</a> and <a href="https://wiki.openstreetmap.org/wiki/OsmChange">osmChange</a> wiki pages it sounds like I can't just add/update a single tag, but rather must download the full set of tags for a way, add/update the tag I'm interested in, then upload the full set of tags.<br>
<br>Should I plan to script doing this for each way separately (to avoid stepping on any changes that happen during the import) or is it better to do this for a region in bulk? What has worked well in the past for adding tags?<br>
<br></li><li>As far as I can tell, I'm the only user who has added surface tags in Vermont and the VCGI data is more precise in distinguishing between gravel, graded soil, and unimproved/primitive surfaces than I was able to be. I would like the import to override the surface tags I've added, but don't want to step on other mappers toes. Is there any way to find out if others have added surface tags in Vermont?<br>
<br></li><li>My <a href="https://wiki.openstreetmap.org/wiki/Vermont_road_surfaces#Way.2FShape_Matching">process of mapping from</a> the source data to the OSM ways doesn't get all roads mostly due to differences in how ways are split into segments, but the process successfully maps the surfaces for 74% of ways in the state:<br>
<br><div style="margin-left:40px">Ways with surfaces matched: 21446<br>Ways with surfaces mixed: 2210<br>Ways with surfaces not found: 5382<br></div><br>As far as I can tell from numerous spot-checks, the process is always erring on the side of skipping ambiguous results and I haven't found any cases yet where a grossly-wrong tag would be applied. Does anyone have any feedback on this process? <br>
</li></ul><p>Best,<br>Adam<br></p></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 22, 2012 at 8:02 PM, Adam Franco <span dir="ltr"><<a href="mailto:adamfranco@gmail.com" target="_blank">adamfranco@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Thank you all for the great feedback and advice! It looks like this project is potentially feasible but that I have many things to learn and figure out to make it happen. I'll be in touch after I've figured out how to work with the VCGI data and then get proper usage permission. Thanks again and happy holidays!<br>
<div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra">Best,<br></div><div class="gmail_extra">Adam<br></div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 21, 2012 at 9:47 AM, Andrew Guertin <span dir="ltr"><<a href="mailto:andrew.guertin@uvm.edu" target="_blank">andrew.guertin@uvm.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>On 12/20/2012 05:03 PM, Adam Franco wrote:<br>
> * Has anyone located a good source for state or national road surface data?<br>
> The TIGER data doesn't seem to include surface information as far as I can<br>
> tell.<br>
<br>
</div>The VCGI EmergencyE911_RDS file has a field for this. Unfortunately,<br>
58773 out of 64302 values (91%) are "Unknown".<br>
<br>
The VCGI license doesn't explicitly give the permissions needed for OSM,<br>
but when I asked to use the town boundaries layer they gave permission.<br>
(I still need to get around to that...)<br>
<div><br>
> * Is this a project that the OSM community in Vermont, the broader region,<br>
> or nationally (assuming data is available) would support? I'd rather not do<br>
> a lot of work to prepare it if there is no desire for inclusion in the data<br>
> set.<br>
<br>
</div>I'd support it.<br>
<br>
_______________________________________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org" target="_blank">Talk-us@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
</blockquote></div><br></div></div></div></div></div>
</blockquote></div><br></div></div>