Here's an example of a "curated bot update", of the type I feel can work well for things like USPS Blue Box data, or public transit routes in the future.
Once a month I run script that loads http://www.ncdc.noaa.gov/oa/radar/nexrad.kmz. and compares it to a XAPI or Overpass query. The data is OSM licence compatible, though I don't really import it directly. If there's a difference I get an email like: <?xml version="1.0" encoding="UTF-8"?> <osm version="0.6" generator="osmsync"> <changeset> <tag k="source:website" v="http://www.ncdc.noaa.gov/oa/radar/nexrad.kmz"/> <tag k="source" v="osmsync:noaa:nexrad"/> <tag k="note" v="Prepared for human review by osmsync: official NOAA NEXRAD weather radar stations"/> <tag k="conflation_key" v="source:pkey"/> <tag k="bot" v="yes"/> </changeset> <node action='add' lat='30.337' lon='-89.82599999999999' id='-1' > <tag k='website' v=' http://www.ncdc.noaa.gov/nexradinv/chooseday.jsp?id=KLIX'/> <tag k='name' v='KLIX'/> <tag k='source:pkey' v='KLIX'/> <tag k='man_made' v='monitoring_station'/> <tag k='monitoring_station' v='radar'/> <tag k='radar' v='NEXRAD'/> <tag k='source' v='osmsync:noaa:nexrad'/> <tag k='operator' v='NOAA'/> </node> </osm> If any nodes are modified, they appear as modify or delete records. I load the dot-osm file into josm, work around a changeset bug in josm, select all points and activate the TODO plugin, visit each spot, move the spot to the huge white ball that is the radar dome, check for duplicates and merge any hand mapped tags, upload. A similar lather-rinse-repeat with MapRoulette could work through an update from USPS in a few weeks. (though it's harder, because the blue boxes are generally not visible on the satellite maps). ---------------- This is not regional mapping, but rather "single interest mapping".
_______________________________________________ Imports-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports-us
