Hi Apollinaris,
found a problem in the osm data. there was a short bridge with the name of
the exit instead of the motorway name. the turn instruction was exactly as
expected according to your implementation.
OK.
I have another interesting one here
Hi all.
If a riverbank intersect a landuse, the riverbank should be drawn on top of
the landuse.
See the attachment for an example.
Pls excuse my bad english...
--
* Matteo Gottardi | matg...@tin.it
* ICQ UIN 20381372
* Linux - the choice of a GNU generation
* GPG Fingerprint:
* B9EE 108F 52C8
Hi Matteo,
If a riverbank intersect a landuse, the riverbank should be drawn on top of
the landuse.
See the attachment for an example.
(Why) can't you define a multipolygon that cuts out the riverbank from the
landuse?
I am afraid that mkgmap would become a lot more complex if it allowed a
I have successfully built contour map for Spain using srtm2osm -
splitter - mkgmap. I combine srtm img's and regular map img's with
mkgmap. Up to here everything goes fine. The problem now is that major
and medium contour lines are shown at any zoom level in MapSource and
gps, not taking into
0 In article 4b7175d1.3000...@madasafish.com,
0 Dave F. URL:mailto:dave...@madasafish.com (Dave) wrote:
Dave Does mkgmap make use of the layer tag?
As far as we know (correct me if I'm wrong), the Garmin units (and thus
their maps) don't have a concept of layer in the data - only in the
Hopefully, this patch will fix Marco's routing problem in Rome. The bug
is ancient (almost as old as Rome) but it hasn't shown itself much
before now because it only causes a problem when one of the routing
tables gets to a certain size which only occurs when there are quite
a few turn
