The problem is not fixing the occasional problem with coastlines.
When I encounter a coastline problem, I recreate that area with much smaller
map tiles so I can narrow down the flooded area to a small region. Usually
the problem can be found and fixed within an hour.
My problem is that people
Felix Hartmann wrote:
Only solution I think is to make --route default and
compulsory for the moment. Else people will create maps that havoc other
maps without realising.
I strongly advice against this. The problem has been around a very long time
and nobody noticed, so I don't think
On 25.05.2010 11:58, NopMap wrote:
Felix Hartmann wrote:
Only solution I think is to make --route default and
compulsory for the moment. Else people will create maps that havoc other
maps without realising.
I strongly advice against this. The problem has been around a very
On 25.05.2010 11:53, Alexander Atanasov wrote:
Hi Felix,
On Tue, May 25, 2010 at 2:02 AM, Felix Hartmann
extremecar...@googlemail.com wrote:
Just got to test it. Good try but ain't work. Still crashing
Mapsource/Basecamp. Only solution I think is to make --route default and
On Thu, 2010-05-20 at 22:57 -0700, NopMap wrote:
Hi!
I have been playing around with generated sea polygons. The algorithm works
remarkably well - but I have been experiencing trouble due to inconsistent
use of natural=coastline in the data.
There was an invalid use of natural=coastline
Yesterday germany had no coastline-problems ;)
An easy way for correcting the errors would be the possibility to open the
splitted osm-Files. Then you can fix the error direct (and afterwards in
osm-database). There is no waiting for next planetfile.
Now I draw in Mapsource rectangels of the
Hello,
this will crash, if you wont divide planetfile-id-numbers and your own
id-numbers. The easiest way would be an negative id-number. But Nops
composer doesn't support negative id-numbers.
cu,
aighes
--
View this message in context:
aighes (h.scholl...@googlemail.com) wrote:
Yesterday germany had no coastline-problems ;)
An easy way for correcting the errors would be the possibility to open the
splitted osm-Files. Then you can fix the error direct (and afterwards in
osm-database). There is no waiting for next
Felix Hartmann wrote:
Routable maps are in no way bigger than non routable maps (if there is
no routable information inside, of course if you use the same style that
is routable and compile it without --route it gets smaller, if you
remove all road_class and road_speed from style, there
Hi!
garvanamp;maew wrote:
I am not sure this question was answered completely, so I scrolled back
to the original post. I recall on reading the osmosis wiki that it can
merge OSM files.
osmosis --rx 1.osm --rx 2.osm --merge --wx merged.osm
Have you tried this?
I do not think that
No, I'm fixing norwegian coastline. Typical errors are fake lakes next to the
coastline or lakes tagged as natural=coastline and not as natural=water.
cu,
aighes
--
View this message in context:
http://gis.638310.n2.nabble.com/Maintaining-generated-sea-polygons-tp5082865p5098599.html
Sent from
11 matches
Mail list logo
