Re: [mkgmap-dev] GRMN_TYPE
Hi Brad There are various resources on the internet that list type codes that have a defined Garmin meaning. I don't know of inaccuracies in mkgmap mapnic.txt, but it might not be complete and it might include less standard/common meanings. Most Garmin meanings from above are common to most devices but there are exceptions. Worst are the cases where a device simply won't render a particular type code, regardless of a supplied typ representation. The Garmin device "Find" mechanism relies on in-built ranges of point and line types, along with mkgmap building the required indexing data into the map image. Many of these can be gleaned from the default style. So yes, a Garmin device might do something different to what you expect. You need to experiment to find out when. Ticker On Tue, 2024-01-30 at 09:36 -0700, brad wrote: > So, if they don't have a comment they don't have a standard Garmin > usage? Do all garmin devices follow the standard garmin usage? I > think not, but I don't have solid evidence other than it seems like some > line types 0x06, 0x07, 0x18 won't show on a zumo XT. > > I'm trying to understand: when I use a typ code, and my own typ file, > when does garmin do something differently than what I expect? > > > On 1/30/24 02:39, Ticker Berkin wrote: > > Hi Brad > > > > Lines like this follow the type code and, as a comment, describe the > > standard > > Garmin usage, eg: > > > > ... > > [_polygon] > > type=0x02 > > ;GRMN_TYPE: Urban Areas/SMALL_CITY/Small urb...nts/Non NT > > String=Suburb > > String1=0x01,Résidentiel > > ... > > > > Ticker > > > > On Mon, 2024-01-29 at 17:43 -0700, brad wrote: > > > I was comparing a fairly new TYP file (r4905 mapnik.txt) with my own > > > (grown from Openfietsmap quite a while ago) and noticed there was > > > usually a line like this > > > > > > ;GRMN_TYPE: Roads/HIGH_SPEED_RAMP, RAMP/Highway ramp which is to be > > > driven at high speeds/Non NT, NT > > > > > > or > > > > > > ;GRMN_TYPE: // > > > > > > What is the meaning of this? > > > > > > Thx > > > Brad > > > ___ > > > mkgmap-dev mailing list > > > mkgmap-dev@lists.mkgmap.org.uk > > > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > ___ > > mkgmap-dev mailing list > > mkgmap-dev@lists.mkgmap.org.uk > > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > ___ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] GRMN_TYPE
So, if they don't have a comment they don't have a standard Garmin usage? Do all garmin devices follow the standard garmin usage? I think not, but I don't have solid evidence other than it seems like some line types 0x06, 0x07, 0x18 won't show on a zumo XT. I'm trying to understand: when I use a typ code, and my own typ file, when does garmin do something differently than what I expect? On 1/30/24 02:39, Ticker Berkin wrote: Hi Brad Lines like this follow the type code and, as a comment, describe the standard Garmin usage, eg: ... [_polygon] type=0x02 ;GRMN_TYPE: Urban Areas/SMALL_CITY/Small urb...nts/Non NT String=Suburb String1=0x01,Résidentiel ... Ticker On Mon, 2024-01-29 at 17:43 -0700, brad wrote: I was comparing a fairly new TYP file (r4905 mapnik.txt) with my own (grown from Openfietsmap quite a while ago) and noticed there was usually a line like this ;GRMN_TYPE: Roads/HIGH_SPEED_RAMP, RAMP/Highway ramp which is to be driven at high speeds/Non NT, NT or ;GRMN_TYPE: // What is the meaning of this? Thx Brad ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] GRMN_TYPE
Hi Brad Lines like this follow the type code and, as a comment, describe the standard Garmin usage, eg: ... [_polygon] type=0x02 ;GRMN_TYPE: Urban Areas/SMALL_CITY/Small urb...nts/Non NT String=Suburb String1=0x01,Résidentiel ... Ticker On Mon, 2024-01-29 at 17:43 -0700, brad wrote: > I was comparing a fairly new TYP file (r4905 mapnik.txt) with my own > (grown from Openfietsmap quite a while ago) and noticed there was > usually a line like this > > ;GRMN_TYPE: Roads/HIGH_SPEED_RAMP, RAMP/Highway ramp which is to be > driven at high speeds/Non NT, NT > > or > > ;GRMN_TYPE: // > > What is the meaning of this? > > Thx > Brad > ___ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Ranking of relations
Dear Gerd,
do you have an example of how it should look like?
I can only say, that with the code shown below I get an overlay map
showing the route relations in the desired order: icn on top of
everything and so on. With the order in the lines file and an
appropriate typ file I can manipulate the appearance as I want.
Regards,
Bernard
Am 29.01.2024 um 18:45 schrieb Gerd Petermann:
Hi Bernard,
I still think that you also have to collect the different network values and
use a regex to check if the list of values contains e.g. icn.
Gerd
Von: mkgmap-dev im Auftrag von Bernard Mai
Gesendet: Samstag, 27. Januar 2024 19:37
An: Development list for mkgmap; m...@tvage.co.uk
Betreff: Re: [mkgmap-dev] Ranking of relations
Dear Mike,
I looks like your suggestion did the trick. With the following lines in the
"relations" file I get the desired display of routes in my overlay map:
# bicycle routes
route=bicycle
{
apply
{set route='${route}';set
route_name='$(route_name),${name}'|'${name}';set
route_ref='$(route_ref),${ref}'|'${ref}';}
}
type=route & route=bicycle & network=icn{apply {add route_icn=yes;}}
type=route & route=bicycle & network=ncn{apply {add route_ncn=yes;}}
type=route & route=bicycle & network=rcn{apply {add route_rcn=yes;}}
type=route & route=bicycle & network=lcn{apply {set route_lcn=yes;}}
# mountainbike routes
route=mtb
{
apply
{add route_mtb=yes; add
route_mtb_name='$(route_mtb_name),${name}'|'${name}'; add
route_mtb_ref='$(route_mtb_ref),${ref}'|'${ref}';}
}
In the "lines" file I can adjust the zoom-level display and naming. For me the
following lines work well:
# bicycle routes
route_icn=yes
[0x10f01 resolution 18-20 continue]
route_icn=yes{name '${route_ref}'}
[0x10f01 resolution 20-23 continue]
route_icn=yes{name '${route_name}
(${route_ref})'|'${route_name}'|'${route_ref}'}[0x10f02
resolution 24]
route_ncn=yes
[0x10f01 resolution 20-22 continue]
route_ncn=yes{name '${route_ref}'}
[0x10f01 resolution 23 continue]
route_ncn=yes{name '${route_name}
(${route_ref})'|'${route_name}'|'${route_ref}'}[0x10f02
resolution 24]
route_rcn=yes
[0x10f03 resolution 21-22 continue]
route_rcn=yes{name '${route_ref}'}
[0x10f03 resolution 23 continue]
route_rcn=yes{name '${route_name}
(${route_ref})'|'${route_name}'|'${route_ref}'}[0x10f04
resolution 24]
route_lcn=yes
[0x10f05 resolution 23 continue]
route_lcn=yes{name '${route_name}'|'${route_ref}'}
[0x10f05 resolution 24]
# mtb routes
route_mtb=yes{name '${route_mtb_ref}'}
[0x10f06 resolution 23 continue]
route_mtb=yes{name '${route_mtb_name}
(${route_mtb_ref})'|'${route_mtb_name}'|'${route_mtb_ref}'}[0x10f06
resolution 24]
Now I can play around, as the display of these lines as overlay map on a Garmin
Epix watch is quite thin (even with lines up to 18 pixel width, having 6-7
pixel width used with a colour and the remaining pixels transparent to show the
route beside any way). In general, my experience is that specially on a watch
all bitmap lines are hard to see.
Many thanks and regards,
Bernard
Am 27.01.2024 um 16:11 schrieb m...@tvage.co.uk:
HI Bernard,
I can’t see why bicycle routes should be displaying in the wrong order, but if
an MTB route runs along a bicycle route and its relation is processed after the
bicycle one, I think the route value will be changed from bicycle to mtb. I
suggest using add instead of set on the relation statement for mountain bike
routes:
type=route & route=mtb
{
apply
{add route='${route}'; set
route_mtb_name='$(route_mtb_name),${name}'|'${name}'; set
route_mtb_ref='$(route_mtb_ref),${ref}'|'${ref}';}
}
Regards,
Mike
From: Bernard Mai
Sent: 26 January 2024 10:50
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: [mkgmap-dev] Ranking of relations
Dear all,
I want to generate an overlay map to be used as additional layer on a Garmin
watch. This
