[osmosis-dev] Problems importing osm files to API bd

Egoitz Ormaetxea egoitz.ormaetxea at gmail.com
Sat Mar 5 10:39:08 GMT 2011


Thanks, I will try the clipIncompleteEntities and completeWays solutions.

Where can I see all the modifiers of the osmosis command? Tried "man
osmosis" or "osmosis help", but it only shows some examples.



> When you perform a bounding box extract, if nodes lie outside the bounding
> box, but are referenced by ways inside the bounding box they will not be
> included in the file.  This is due to the way Osmosis processing works
> because it finishes processing nodes before it sees the ways.
>
> You have several options here:
> 1. Drop the constraint from the database.  This might lead to other issues.
> 2. Add the clipIncompleteEntities=true option to the --bounding-box task.
> This will modify the ways so that they no longer reference the problematic
> ways.  Obviously they will no longer be identical to the original ways from
> the input planet file.
> 3. Add the completeWays=true option to the --bounding-box task.  This will
> include the missing nodes, but will slow down processing enormously.
>
> You've already tried option 1 which gives you errors in JOSM.  I suspect 3
> will be too slow.  That leaves you with 2.  Note that 2 modifies the ways
> which may or may not be appropriate for you.
>
> Brett
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmosis-dev/attachments/20110305/12db4273/attachment.html>


More information about the osmosis-dev mailing list