<br><div class="gmail_quote">On Thu, Oct 8, 2009 at 6:27 PM, andrzej zaborowski <span dir="ltr"><<a href="mailto:balrogg@gmail.com">balrogg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2009/10/8 Sam Vekemans <<a href="mailto:acrosscanadatrails@gmail.com">acrosscanadatrails@gmail.com</a>>:<br>
<div class="im">> Step 1: Data conversion<br>
> -using eithor 'shp-to-osm.jar' or 'shp2osm.py' or 'mp2osm' or 'other'<br>
> we make a conversion script<br>
> -1 person is in charge of editing this script (as users will submit<br>
> errors) (just as for other programs)<br>
><br>
> Step 2: data sharing<br>
> -the person that is running the conversion script would make these<br>
> .osm files available to the community so people can see it.<br>
> -available on a server somewhere like <a href="http://mediafire.com" target="_blank">mediafire.com</a><br>
><br>
> 3 -data import<br>
> eithor a.1 use josm and copy the features over<br>
<br>
</div>Note that just a copy & paste will discard the relations so I don't<br>
think this should be recommended, (relations tend to take lots of work<br>
to add manually if you have imported all the members but not the<br>
relations).<br>
<br>
The "Merge layers" option in JOSM is also not really usable because it<br>
can take really long (several days) for two layers with 100k nodes. I<br>
use a little bash script for quick merging .osm files generated by<br>
JOSM, it's at <a href="http://www.openstreetmap.pl/balrog/bulkupload/osm-merge" target="_blank">http://www.openstreetmap.pl/balrog/bulkupload/osm-merge</a><br>
<br>
My usual process is the following:<br>
<br>
1. Convert the data to .osm<br></blockquote><div>1a. Using sh-to-osm.jar and editing the rules.txt file<br>or using shp-to-osm and editing the script with the right tags<br>or using mp2osm and edit the script, or whatever program is out there to convert the source file.<br>
<br>1b. Upload these .osm files to a server somewhere<br>1c. Share on your local talk list where others can find these files <br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2. load into JOSM<br>
3. zoom in, because JOSM can't handle displaying lots of data at the<br>
same time, but it can easily hold lots of data in memory.<br>
4. correct all the tags<br>
5. download the area from OSM on a separate layer,<br></blockquote><div><br>Yup, from 1-5 thats the basics.<br>and from 6-9, this varies depending on the type of data. <br>If your dealing with roads, you might want to use OpenJUMP automatch as it does the same thing as manual, but automatically, and can be done for a large area. (but errors are guaranteed, so AutoMatch is just a 'helper')<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
6. go through all the data and spot duplicate ways, objects, whatever<br>
(this takes a long time to do).<br>
7. each time you delete a way from one layer, mark all the crossings &<br>
connecting nodes with "mergeme=yes" tag.<br>
8. save both .osm files, merge using the bash script, load into JOSM<br>
again, zoom in.<br>
9. search for "mergeme=yes" (ctrl+f in JOSM) and for each search<br>
result: merge the crossings / endings of roads so they are continuous,<br>
then remove the tag, then repeat.<br>
10. save to file, split into small changes and upload using your<br>
favourite upload script.<br></blockquote><div> </div><div>The split can (alternatively) happen before loading the .osm file instead, (i just recommend before rather than after, because my source is nice rectangle NTS tiles, where a single tile are can be loaded with (download and pan around 6 areas) josm downloads area (zooming out it will squawk). I have a .osm file that is the rechangle to use, which is available in the big .zip file.<br>
.... but when dealing with a larger .osm file, then yes splitting it after (saving it to file) makes sense too.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Cheers<br>
</blockquote></div><br><br>Yuppee, where getting somewhere :) Please confirm if you understood or didn't understand :)<br><br>Sam<br><br>Sam<br>