<div class="gmail_quote">This looks good. Some suggestions:</div><div class="gmail_quote"><br></div><div class="gmail_quote">1) Try to do it in geographically small regions. i.e. one city or smallish bounding box at a time</div>
<div class="gmail_quote">2) Use an obvious username</div><div class="gmail_quote">3) Make the turnaround time quick enough so as to reduce conflicts (this goes hand in hand with #1)</div><div class="gmail_quote"><br></div>
<div class="gmail_quote">On Tue, Oct 26, 2010 at 2:56 PM, Hardgrave, Roman <span dir="ltr"><<a href="mailto:rhardgrave@mapquest.com">rhardgrave@mapquest.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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>
</blockquote></div><br>