[OSM-talk] osmcut.c Some problems with my solution :-)

[Erik Johansson]

On Wed, Oct 29, 2008 at 8:28 PM, Michael Hufer <michael.hufer at gmx.de> wrote:
>> BTW in your osmcut it still says that ways are only written to the 4
>> first tiles that the way touches, is this still true? Doesn't seem
>> like what you want, or?
>
> I had only about 10 ways spanning more than 4 tiles in the whole germany.osm
> when I cut it into 0.5 degree tiles. All but one span more than 6 extra tiles
> (i.e. more than 10 tiles in all). Most were 'boundary' ways (e.g. the
> national boundary Poland/Germany) which is no great loss if not present in a
> map that ends on that boundary anyway :-).

ok! I don't use osmcut since I wasn't aware it existed, but I use my
own tool which splits on OSM slippymap tile boundaries that makes my
tiles smaller and hence I see more tiles per way. I have no real
numbers though.. :-)

Are you going to develop osmcut more?

> So to increase this number was not on my agenda as
>
> 1) the number of affected ways was/is small
>
> 2) the number of tiles would have to be increased substantially (from 4 to
> over ten) to reduce the number of ways affected. This would have greatly
> increased the memory consumption (more than doubled it for each node in the
> input file) for little extra gain.

It was important for me for me though.. ;-)

The fastest solution to your problem is either to fix the app that
uses your data so that it can read nodes interleaved with the ways.
This would make it possible to
1. read way
2. fetch nodes
3. write nodes
4. write way
5. goto 1.

Or to do what Frederik says.do a separate dump of nodes and ways and
then join them, I do this and it's trivial.

/emj