Perhaps.. I guess time will tell. :)
Lots of people are working on finding solutions, so im sure 1 will emerge. And there is also more than 1 'right answer' as each situation is different. and sometimes means looking at the problem from an 'outside of osm' approach. Cheers, Sam On 12/8/10, Ian Dees <[email protected]> wrote: > I don't think koordinates or geocommons offer what we need, though: a way > for a mapper to take the results of merging and use them while mapping in > JOSM or Potlatch. > > I don't think the right thing to do is to merge the data and then upload it > wholesale (i.e. with a script) into OSM. > > On Wed, Dec 8, 2010 at 10:41 AM, Sam Vekemans > <[email protected]>wrote: > >> I'm still early in the game, but it looks like koordinates.com could >> be the best holding house for this. >> .... all that needs to be done on koordinates.com side is to have the >> option to zoom into an area and export as .osm files. >> >> >> I'll be loading a bit more samples of shp files so to see what it's like. >> >> >> >> I think geocommons.com is planning on supporting .osm files as a >> export option.... its just too early to tell who will be the biggest >> and best :) >> >> >> If there is a 3rd .shp file website out their, i'd be happy to hear of it. >> >> >> cheers, >> sam >> >> >> p.s. on the new zealand mailing list, folks are wrattling their brains >> to get something. >> ... and for canvec it's the ommissions and remissions that can be done >> at canvec data source level. >> >> >> Still no breakthrough afaik ... >> >> On 12/8/10, Ian Dees <[email protected]> wrote: >> > With TIGER 2010 starting to roll out we need to think about how to offer >> > some way of comparing OSM with arbitrary datasets. >> > >> > Here are my thoughts so far: >> > 1) User uploads a shapefile >> > 2) User selects attribute(s) in the shapefile to use for matching with >> OSM >> > data (i.e. a road name or tiger identifier or something) >> > 3) System performs a geospatial match (including the attribute(s) the >> user >> > specified in step 2) on OSM data in the area of the shapefile >> > 4) System renders a map with three layers: a) data in reference but not >> > found in OSM, b) data in OSM but not found in reference, c) data in both >> > >> > Based on (4), mappers can modify the OSM data to more-closely match the >> > geometry or meta-data of the reference data set. A more complicated >> version >> > of this tool could allow the mapper to accept wholesale changes in >> geometry >> > or attributes into the OSM dataset (removing or manipulating the >> > existing >> > data). >> > >> > This is all pretty tricky, but I'd love to hear other people's opinions. >> > >> > On Wed, Dec 8, 2010 at 10:06 AM, Mike N. <[email protected]> wrote: >> > >> >> I have obtained a set of road centerlines from a US county that has >> >> been >> >> published in the public domain. I would like to use this to correct >> the >> >> OSM roads for that county, since the TIGER data was one of the "poor >> >> alignments" that we are so familiar with. In addition, the road names >> >> have >> >> all been changed for E911 consistency. This file is likely even newer >> >> than >> >> the 2010 TIGER centerlines. >> >> >> >> I have used Ian's shp-to-osm to begin looking at the data. >> >> >> >> 1. Does anyone have a rules file for a typical municipal road >> >> centerlines shape file conversion? I started to develop this, but >> >> can't >> >> believe no one has done this before. >> >> 2. Is it good to preserve TIGER tags for untouched roadways, or just >> >> delete and replace them? The geometry is so far off that it is easier >> to >> >> delete and replace. >> >> >> >> Usual import disclaimers - >> >> >> >> Any relations will be preserved. >> >> Any existing road alignment edits will be preserved (such as for >> >> interstates) >> >> Any existing attribution will be preserved (speed limits, traffic >> lights, >> >> etc) >> >> Corrected data will be manually stitched to existing data at borders >> >> or >> >> pre-edited roads. >> >> >> >> >> >> >> >> _______________________________________________ >> >> Imports mailing list >> >> [email protected] >> >> http://lists.openstreetmap.org/listinfo/imports >> >> >> > >> >> >> -- >> Twitter: @Acrosscanada >> Blogs: http://acrosscanadatrails.posterous.com/ >> http://Acrosscanadatrails.blogspot.com >> Facebook: http://www.facebook.com/sam.vekemans >> Skype: samvekemans >> IRC: irc://irc.oftc.net #osm-ca Canadian OSM channel (an open chat room) >> @Acrosscanadatrails >> > -- Twitter: @Acrosscanada Blogs: http://acrosscanadatrails.posterous.com/ http://Acrosscanadatrails.blogspot.com Facebook: http://www.facebook.com/sam.vekemans Skype: samvekemans IRC: irc://irc.oftc.net #osm-ca Canadian OSM channel (an open chat room) @Acrosscanadatrails _______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
