Sam, I think what Roman is suggesting here is very different than other imports and does not require the same amount of community interaction. If they were doing more than adding tags to existing primitives I would suggest something closer to what you want. As it stands, though, they aren't modifying the location or tagging of existing stuff so I think they're in the clear to upload small groups of changes.<div>
<br><div class="gmail_quote">On Tue, Oct 26, 2010 at 4:14 PM, Sam Vekemans <span dir="ltr"><<a href="mailto:acrosscanadatrails@gmail.com">acrosscanadatrails@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
Speaking from experience (1), OpenStreetMap is not designed to handle<br>
an extract, where the syste is closed.<br>
<br>
<br>
You need to work wth local mappes in the region (contact them<br>
directly) and find someone willing to help.<br>
<br>
<br>
Manually go through the map, and do the conversions one at a time.<br>
<br>
<br>
Have a Mapping party, and host it via tinychat/skype so you can attend remotly.<br>
<br>
<br>
If your interested in a 2-way map, try using <a href="http://geocommons.com" target="_blank">geocommons.com</a> where you<br>
can submit your data.<br>
<br>
<br>
Also, another option is to use <a href="http://geonames.org" target="_blank">geonames.org</a> as this will be of use for<br>
you. (CCBY data, and totally independent of OSM<br>
<br>
<br>
Have a great mapping party. :)<br>
<br>
<br>
The moment data is in OSM, it is part of the community project, so you<br>
cannot take control of the data in the map.<br>
<br>
<br>
Many others, are manually making the changes.<br>
<br>
<br>
Cheers,<br>
Sam<br>
<br>
<br>
(1) With the Canada Import, Natural Resources Canada provides data as<br>
.osm files, they cannot except osm changes back, as their dataset is<br>
mixed sources, and they need to own the data.<br>
<div><div></div><div class="h5"><br>
On 10/26/10, Hardgrave, Roman <<a href="mailto:rhardgrave@mapquest.com">rhardgrave@mapquest.com</a>> wrote:<br>
> Hello,<br>
> We are considering doing a translation project to add some westernized names<br>
> to roads and places in several Asian cities. We're planning to start with<br>
> Beijing and see how it goes. We wanted to get feedback on our plan from the<br>
> community before we got started.<br>
><br>
> The idea is to add name:en attributes to any Node or Way that has existing<br>
> data in the name attribute. Also, if the existing name attribute contained<br>
> westernized names (rather than native), we'd move that data from the name<br>
> attribute to the name:en attribute.<br>
><br>
> We'll be providing our translators a spreadsheet where they can add/move the<br>
> data. Here's the step by step process on how we're planning to extract and<br>
> then import the data back into OSM.<br>
><br>
> 1) Export the osm files out of the master OSM data given a bounding box<br>
> -Use JOSM, XAPI or the OSM web based export given a bounding box<br>
> 2) Run a script to chew through the osm file and look for any nodes and ways<br>
> that have a name attribute but not a name:en attribute. For those that fit<br>
> the bill, capture the following data into a csv:<br>
> a) Node or Way<br>
> b) Node or Way Id<br>
> c) Version<br>
> d) Name Native<br>
> 2a) Possibly add functionality to the script to look for westernized<br>
> charactersets in the native field and either flag it or move it<br>
> automatically<br>
> 3) Give the csv to translator. They translate (via Excel) and then export<br>
> out a csv:<br>
> a) Node or Way<br>
> b) Node or Way Id<br>
> c) Version<br>
> d) Name Native<br>
> e) Name English<br>
> 4) Download the osm data again to get latest set<br>
> 5) Reform the osm data file with the new translated fields by inserting xml<br>
> tags for the native and english language attribute for nodes/ways, matching<br>
> by ID<br>
> a) Would check first that the Version is the same before updating<br>
> b) Ones with different Versions would be retrieved for manual<br>
> inspection/resolution<br>
> 6) Upload via JOSM<br>
><br>
><br>
> We have the resources lined up to get started on this soon. We want to make<br>
> sure our plan and process look good. Thank you for any feedback you can<br>
> provide.<br>
><br>
><br>
> Roman Hardgrave<br>
> Senior Sales Engineer<br>
> MapQuest<br>
> <a href="mailto:rhardgrave@mapquest.com">rhardgrave@mapquest.com</a><br>
><br>
> Try out the new MapQuest <a href="http://new.mapquest.com" target="_blank">new.mapquest.com</a><br>
><br>
><br>
> _______________________________________________<br>
> Imports mailing list<br>
> <a href="mailto:Imports@openstreetmap.org">Imports@openstreetmap.org</a><br>
> <a href="http://lists.openstreetmap.org/listinfo/imports" target="_blank">http://lists.openstreetmap.org/listinfo/imports</a><br>
><br>
<br>
<br>
</div></div><font color="#888888">--<br>
Twitter: @Acrosscanada<br>
Blogs: <a href="http://acrosscanadatrails.posterous.com/" target="_blank">http://acrosscanadatrails.posterous.com/</a><br>
<a href="http://Acrosscanadatrails.blogspot.com" target="_blank">http://Acrosscanadatrails.blogspot.com</a><br>
Facebook: <a href="http://www.facebook.com/sam.vekemans" target="_blank">http://www.facebook.com/sam.vekemans</a><br>
Skype: samvekemans<br>
IRC: irc://<a href="http://irc.oftc.net" target="_blank">irc.oftc.net</a> #osm-ca Canadian OSM channel (an open chat room)<br>
@Acrosscanadatrails<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org">Imports@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/imports" target="_blank">http://lists.openstreetmap.org/listinfo/imports</a><br>
</div></div></blockquote></div><br></div>