Felix,
there is nothing to check. The flood blocker works only in
multipolygon mode. It is not possible to implement that for the
polygon mode.
Where do you think is the advantage of the polygon mode?
WanMil
The advantage is:
a) Speed (if you use --transparent and then gmt to set the
Felix Hartmann (extremecar...@gmail.com) wrote:
[snip]
--- in principal there is no speed advantage - [snip]
Maybe it's just me, but I find the polygon version of generate-sea
much faster than the multipolygon version - at least twice as fast if
not more.
The multipolygon version
On 19.12.2010 18:17, WanMil wrote:
Felix,
there is nothing to check. The flood blocker works only in
multipolygon mode. It is not possible to implement that for the
polygon mode.
Where do you think is the advantage of the polygon mode?
WanMil
The advantage is:
a) Speed (if you use
Am 17.12.2010 16:49, schrieb Felix Hartmann:
On 17.12.2010 16:45, WanMil wrote:
Thanks Felix,
I tested it now with:
extend-sea-sectors,close-gaps=6000,floodblocker,fbgap=60,fbthres=200,fbratio=0.6,land-tag=natural=background
No errors and sea polygons came back, but the floodblocker
Felix,
there is nothing to check. The flood blocker works only in
multipolygon mode. It is not possible to implement that for the
polygon mode.
Where do you think is the advantage of the polygon mode?
WanMil
The advantage is:
a) Speed (if you use --transparent and then gmt to set the
Felix Hartmann (extremecar...@gmail.com) wrote:
[snip]
--- in principal there is no speed advantage - [snip]
Maybe it's just me, but I find the polygon version of generate-sea
much faster than the multipolygon version - at least twice as fast if
not more.
--
Charlie
On 08.12.2010 20:50, WanMil wrote:
On 05.12.2010 15:48, WanMil wrote:
I committed r1746 to the coast branch.
The floodblocker rules which OSM elements are used to detect land
and as
sea areas can now be configured in the special style
resources/styles/floodblocker.
If this style marks a
I tested the floodblocker on the Benelux abstract from
http://planet.openstreetmap.nl/
The options in my mkgmap args file were:
generate-sea: multipolygon,floodblocker,land-tag=natural=background
The parameter fbgab gives an error (I'm using java under windows).
I tried different settings for
On 17.12.2010 11:54, Minko wrote:
I tested the floodblocker on the Benelux abstract from
http://planet.openstreetmap.nl/
The options in my mkgmap args file were:
generate-sea: multipolygon,floodblocker,land-tag=natural=background
The parameter fbgab gives an error (I'm using java under
Sorry Felix, but I have read your message.
you wrote:
I just noted, the multipolygon mode does not work. The floodblocker does
not seem to show any effect
I used multipolygon, because Wanmil adviced me to do so, because otherwise the
floodblocker didn't work.
So, I did, and I noticed the
On 17.12.2010 12:09, Minko wrote:
Sorry Felix, but I have read your message.
you wrote:
I just noted, the multipolygon mode does not work. The floodblocker does
not seem to show any effect
I used multipolygon, because Wanmil adviced me to do so, because otherwise
the floodblocker didn't
Thanks Felix,
I tested it now with:
extend-sea-sectors,close-gaps=6000,floodblocker,fbgap=60,fbthres=200,fbratio=0.6,land-tag=natural=background
No errors and sea polygons came back, but the floodblocker blocks still too
much.
I've tried it with other fb numbers but it still gives the same
On 17.12.2010 13:19, Minko wrote:
Thanks Felix,
I tested it now with:
extend-sea-sectors,close-gaps=6000,floodblocker,fbgap=60,fbthres=200,fbratio=0.6,land-tag=natural=background
No errors and sea polygons came back, but the floodblocker blocks still too
much.
I've tried it with other fb
The parameter fbgab gives an error (I'm using java under windows).
I tried different settings for fbthres,fbratio but no sea came back on my map.
Minko,
the parameter is fbgap instead of fbgab. Sorry for the misspelling!
WanMil
___
mkgmap-dev
Thanks Felix,
I tested it now with:
extend-sea-sectors,close-gaps=6000,floodblocker,fbgap=60,fbthres=200,fbratio=0.6,land-tag=natural=background
No errors and sea polygons came back, but the floodblocker blocks still too
much.
I've tried it with other fb numbers but it still gives the same
Thanks Felix,
I tested it now with:
extend-sea-sectors,close-gaps=6000,floodblocker,fbgap=60,fbthres=200,fbratio=0.6,land-tag=natural=background
No errors and sea polygons came back, but the floodblocker blocks still too
much.
I've tried it with other fb numbers but it still gives the same
On 17.12.2010 16:45, WanMil wrote:
Thanks Felix,
I tested it now with:
extend-sea-sectors,close-gaps=6000,floodblocker,fbgap=60,fbthres=200,fbratio=0.6,land-tag=natural=background
No errors and sea polygons came back, but the floodblocker blocks
still too much.
I've tried it with
Thanks Wanmil,
Those images explained very well what exactly happens.
So what I can do is to add more coastline to the benelux osm data
to prevent that this coastline is intercepting itself.
I have to merge osm data (German coastline) to the osm data from the Benelux
extract.
How does this work
That will be great! I suppose somebody already uses this option?
Is there a German coastline available?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
: WanMil wmgc...@web.de
Aan: Development list for mkgmap mkgmap-dev@lists.mkgmap.org.uk
Verzonden: Vrijdag 17 december 2010 18:30:48
Onderwerp: Re: [mkgmap-dev] Configurable flood blocker
Thanks Wanmil,
Those images explained very well what exactly happens.
So what I can do is to add more
* @Steve: Can you check if my changes to the ElementSaver class and my
coastfile loading mechanism feels good for you? Maybe you want to
simplify some things?
Yes it looks fine to me. Anyway it is more important to get useful
features working for people.
I'd merge it back, seems everyone
On 05.12.2010 15:48, WanMil wrote:
I committed r1746 to the coast branch.
The floodblocker rules which OSM elements are used to detect land and as
sea areas can now be configured in the special style
resources/styles/floodblocker.
If this style marks a ways as garmin type 0x01 the way is on
On 05.12.2010 15:48, WanMil wrote:
I committed r1746 to the coast branch.
The floodblocker rules which OSM elements are used to detect land and as
sea areas can now be configured in the special style
resources/styles/floodblocker.
If this style marks a ways as garmin type 0x01 the way is on
On 08.12.2010 20:50, WanMil wrote:
On 05.12.2010 15:48, WanMil wrote:
I committed r1746 to the coast branch.
The floodblocker rules which OSM elements are used to detect land
and as
sea areas can now be configured in the special style
resources/styles/floodblocker.
If this style marks a
On 05.12.2010 15:48, WanMil wrote:
I committed r1746 to the coast branch.
The floodblocker rules which OSM elements are used to detect land and as
sea areas can now be configured in the special style
resources/styles/floodblocker.
If this style marks a ways as garmin type 0x01 the way is on
I committed r1746 to the coast branch.
The floodblocker rules which OSM elements are used to detect land and as
sea areas can now be configured in the special style
resources/styles/floodblocker.
If this style marks a ways as garmin type 0x01 the way is on land
whereas 0x02 is used for sea. Now
I have committed an improved version of the flood blocker to the coast
branch.
It is configurable in some parts (please refer to the help file to the
exact config options).
What are the improvements now ?
1. I observed that in many good sea polygons there are some highways
which are located
27 matches
Mail list logo
