[Imports] TMC LCL - help needed

[Sam Vekemans]

On Thu, Oct 8, 2009 at 6:27 PM, andrzej zaborowski <balrogg at gmail.com>wrote:

> 2009/10/8 Sam Vekemans <acrosscanadatrails at gmail.com>:
> > Step 1: Data conversion
> > -using eithor 'shp-to-osm.jar' or 'shp2osm.py' or 'mp2osm' or 'other'
> > we make a conversion script
> > -1 person is in charge of editing this script (as users will submit
> > errors) (just as for other programs)
> >
> > Step 2: data sharing
> > -the person that is running the conversion script would make these
> > .osm files available to the community so people can see it.
> > -available on a server somewhere like mediafire.com
> >
> > 3 -data import
> > eithor a.1 use josm and copy the features over
>
> Note that just a copy & paste will discard the relations so I don't
> think this should be recommended, (relations tend to take lots of work
> to add manually if you have imported all the members but not the
> relations).
>
> The "Merge layers" option in JOSM is also not really usable because it
> can take really long (several days) for two layers with 100k nodes.  I
> use a little bash script for quick merging .osm files generated by
> JOSM, it's at http://www.openstreetmap.pl/balrog/bulkupload/osm-merge
>
> My usual process is the following:
>
> 1. Convert the data to .osm
>
1a. Using sh-to-osm.jar and editing the rules.txt file
or using  shp-to-osm and editing the script with the right tags
or using mp2osm and edit the script, or whatever program is out there to
convert the source file.

1b.  Upload these .osm files to a server somewhere
1c.  Share on your local talk list where others can find these files


> 2. load into JOSM
> 3. zoom in, because JOSM can't handle displaying lots of data at the
> same time, but it can easily hold lots of data in memory.
> 4. correct all the tags
> 5. download the area from OSM on a separate layer,
>

Yup, from  1-5 thats the basics.
and from 6-9, this varies depending on the type of data.
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')


> 6. go through all the data and spot duplicate ways, objects, whatever
> (this takes a long time to do).
> 7. each time you delete a way from one layer, mark all the crossings &
> connecting nodes with "mergeme=yes" tag.
> 8. save both .osm files, merge using the bash script, load into JOSM
> again, zoom in.
> 9. search for "mergeme=yes" (ctrl+f in JOSM) and for each search
> result: merge the crossings / endings of roads so they are continuous,
> then remove the tag, then repeat.
> 10. save to file, split into small changes and upload using your
> favourite upload script.
>

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.
.... but when dealing with a larger .osm file, then yes splitting it after
(saving it to file) makes sense too.


> Cheers
>


Yuppee, where getting somewhere :) Please confirm if you understood or
didn't understand :)

Sam

Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20091008/1322ea8a/attachment.html>