I have tried mkgmap-r3819 now. I can confirm that it works properly with
multiple rules for the same garmin type and mixed skipFilter values.
I also switched to using --precomp-sea alone. The docs are pretty misleading
in this point. :-(
Maps look nice now. Thanks for the support.
bye, Nop
I definitely did not have a regular rule for natural=sea in my style. I need
to check whether there was a rule added by code in my tooling. (or in mkgmap
code)
Is the observation correct, that the SeaGenerator creates many simple
polygons, individually tagged as natural=sea, but not connected by
Hi Gerd,
Gerd Petermann wrote
> The default style contains this line:
> natural=sea { add mkgmap:skipSizeFilter=true; set mkgmap:drawLevel=2 }
> [0x32 resolution 10]
>
> which in fact tells mkgmap to skip the size filter for the polygons
> generated by precomp-sea.
Thank you, that was the
After playing around some more I think I found the reason for the problem. It
appears that there is a conflict between the --min-size-polygon= parameter
and sea generation from the precompiled files.
For larger Values of --min-size-polygon, the tearracing becomes worse. For
smaller values it
Hello,
I am trying to switch to --precomp-sea instead of generating the coastline
directly from OSM data.
For higher zoomlevels this works fine. For lower zoomlevels (scale in
basecamp >=5km) the coastline appears heavily terraced/pixellated. Playing
with parameters like poly reduction did not
The patch works fine. Tested it on a map with 680 tiles. The original mkgmap
crashes, the patched version processes the data without a problem.
When you have checked in the patch, please let me know which revision that
is.
bye
Nop
--
View this message in context:
Did anybody put this one-line fix into mkgmap?
bye
Nop
--
View this message in context:
http://gis.19327.n5.nabble.com/mkgmap-crashes-if-nodes-are-missing-tp5711811p5714755.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
Just an idea that struck me, not a real solution, but a quick improvement:
At the moment mkgamp drops all the data in the area when it cannot be
subdivided. It would be at least some improvement if it would just drop some
data that exceeds the maximum content of an area instead of everything.
Hi!
I have been trying to build a map of portugal for a while, but it never
quite works out. There is no exception, but mkgmap shows a large number of
messags like this:
Area too small to split at
http://www.openstreetmap.org/?mlat=38.59838mlon=-7.34522zoom=17 (reduce
the density of points,
Hi!
WanMil wrote:
The only possible solution is to split the polygon so that it contains
less points (either by selecting the splitter split points or by
changing the osm data). But that's a try and error solution.
Thanks for the information. In that thread you have been discussion
I have just read a report by another user who got the same error message. In
my case the object in question was a large and very compilcated lake with
1000+ nodes. In his case it was a large forest polygon.
Is there a limit to the maximum size of a polyline that mkgmap/garmin format
can handle,
Hi!
Trying to build a map of Portugal and Spain, I encountered an error with a
particular lake in portugal with a very complex outline. I tried it with
different parameter sets, but the error is persistent and always along the
border of this lake. Did this occur with other maps, too? Any ideas
Hi!
I am experiencing a bug with the description parameter in mkgmap 1625 (which
is listed as the current stable version).
When I use a description in quotation marks, e.g. --description=My own map
then mkgmap throws a NullPointerException.
When the spaces are removed, e.g.
Johann Gail wrote:
I do not know, what causes this message. But I assume it is the question
if the device should route over streets (with routing information) or if
it should show only the straight line to the destination. This is was I
understand with 'beeline'. The line which flies a
You can't google the message as it is my translation from German. I don't
know which words an English Garmin device would show.
No, there was no change to the device. I used to get this message when I
used --route for experimental reasons. But I am definite that --route is not
on the command
Hi!
I am getting the error message area too small to split when running
mkgmap. What does this mean?
The tiles are created and at first glance, the map looks ok. I did not use
the splitter but just handed over some osm data.
Can someone explain what mkgmap is trying to tell me?
bye
Yes, the node count is less than in other areas that give no error.
--
View this message in context:
http://gis.638310.n2.nabble.com/area-too-small-to-split-what-does-it-mean-tp5634558p5636797.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
No ideas where this message comes from?
--
View this message in context:
http://gis.638310.n2.nabble.com/Strange-request-with-later-versions-of-mkgmap-tp5620986p5629952.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
___
Hi!
Thanks for your answer.
Charlie Ferrero wrote:
By default I think that for POI types that can accept address
information (0x2a00-0x32ff, afair), mkgmap looks for any addr: tags
and uses them to populate the address fields, plus it looks for a
phone tag and adds this too.
Do
Hi!
I would like to put some detail information with POIs to be shown in the
details view for the POI on the device. After searching the list, I gather
that it can be done but to be honest I did not understand how to do it and
how to control what information is added to the POIs.
Can you help
Hi!
aighes wrote:
you can add address-informaton and phonenumber by setting --index. Usefull
combination would be --location-autofill=1.
Yes, I found the hint that I can activate something with --index.
But what gets added to the details? How can I control what is added? And how
would
Hi!
Steve Ratcliffe wrote:
Its not deliberate certainly. Do you have an example. You need to
quote any value that has a semi-colon in, but I think you always had to.
The rule
shop=Bäckerei [0x2A05 resolution 24]
will produce an error
Error in style: Error: (points:50): Stack size
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
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
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 in the planetfile, that caused
a whole tile in the Alps
You can use MapComposer as a type file editor (but not to change existing
type files).
The tool MapTk also contains a pretty good typ file editor.
bye
Nop
--
View this message in context:
http://n2.nabble.com/typfile-editor-tp4880173p4886923.html
Sent from the Mkgmap Development
Hi!
Just to let you know. Encouraged by your statements, I tried to do the
German coast along the baltic sea with --generate-sea=multipolygon. The map
was made up of 3 tiles.
The result was rather disillusioning. In about 1/4 of the coast it looked
good, on half of the coast the water was
Hi!
I am working on sea polygons once again. After reading through the many
generate-sea-related topics I am still not sure what the current state of
the art is on the matter.
- What is the current recommended command line option/combination that works
for you? What other techniques do you
Hi!
According to the wiki, the last revision of mkgmap recommended as
more-or-less stable is 1188. Which is rather ancient, of course. :-)
As there have been quite some interesting changes recently, especially
around multipolygons, I'd like to raise the question again: In your
experience, is
31 matches
Mail list logo
