Hi,
Works on (old) etrex Vista Cx !
Le 06/05/2014 17:03, nwillink a écrit :
> I'm glad that works!
>
> On 06/05/2014 20:42, Stéphane MARTIN [via GIS] wrote:
>> Hi,
>>
>> Le 06/05/2014 14:08, nwillink a écrit :
>> > Latest NT Topo TYP files use both 0x13 and 0x109 for buildings.
>> > Interestingl
Hi Minko
The plot thickens as lines 0x10900 ,10901,10902 are also used as 'backups'
for 0x20,0x21,0x22, ie contours.
--
View this message in context:
http://gis.19327.n5.nabble.com/Building-vs-way-in-default-style-tp5805279p5805489.html
Sent from the Mkgmap Development mailing list archive at
Interesting, type 0x10900 displays the contours of the buildings on a Dakota
and Oregon.
See https://www.dropbox.com/sh/ly8vyjamajxw1s9/QWBW9cxmWt/type_109.bmp
On Mapsource and Basecamp it's the same almost invisible white area as 0x13
though, but on the newer GPS units it's definitely an improve
I'm glad that works!
On 06/05/2014 20:42, Stéphane MARTIN [via GIS] wrote:
> Hi,
>
> Le 06/05/2014 14:08, nwillink a écrit :
> > Latest NT Topo TYP files use both 0x13 and 0x109 for buildings.
> > Interestingly, only 109 seems to be visible.
> > So, I wonder why 0x13 has been included perhaps for
Hi,
Le 06/05/2014 14:08, nwillink a écrit :
> Latest NT Topo TYP files use both 0x13 and 0x109 for buildings.
> Interestingly, only 109 seems to be visible.
> So, I wonder why 0x13 has been included perhaps for some compatibility
> reason.
That is the solution.
0x10900 works fine on etrex30.
Tha
Latest NT Topo TYP files use both 0x13 and 0x109 for buildings.
Interestingly, only 109 seems to be visible.
So, I wonder why 0x13 has been included perhaps for some compatibility
reason.
--
View this message in context:
http://gis.19327.n5.nabble.com/Building-vs-way-in-default-style-tp5805279p
Hi,
Thanks all.
I'll watch it.
Le 06/05/2014 05:16, Minko a écrit :
> This issue can simply be solved by using a TYP file.
> You can grab the default style typ file that we use in Lambertus generic OSM
> maps:
> https://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Ftyp%2Fosm
This issue can simply be solved by using a TYP file.
You can grab the default style typ file that we use in Lambertus generic OSM
maps:
https://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Ftyp%2Fosm%20generic%253Fstate%253Dclosed
The strange thing is that Garmin doesn't seem
On Mon, May 05, 2014 at 12:58:58PM -0700, GerdP wrote:
Hi Steph,
I think mkgmap creates a shape for the building and another one for
the water. It seems that without a type file the water has higher priority.
It is possible to detect that situation and cut the shape of the building
out of the sh
Hi Steph,
I think mkgmap creates a shape for the building and another one for
the water. It seems that without a type file the water has higher priority.
It is possible to detect that situation and cut the shape of the building
out of the shape for the water, but that will require a lot of CPU, so
Hi all,
I don't know if it's an issue...
A map compiled with the default style gives a not very nice rendering
for "Barrage Vauban" in Strasbourg (identifier 40 217 747 in OSM).
https://tuxdomain.darktech.org/osm-garmin/view.php?file=France/Barrage_Vauban.osm
Building is not rendered. Just the w
11 matches
Mail list logo
