Hi,
I tried the rule
natural=beach | natural=sand [0x53 resolution 20]
without any typ file and I think the result looks worse compared to a map without those polygons,
at least in Basecamp and Mapsource.
I assume you tested with a typ file?
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen@hotmail.com>
Gesendet: Donnerstag, 27. September 2018 18:22
An: osm@pinns; Development list for mkgmap
Betreff: Re: [mkgmap-dev] Beaches as a polygon
Hi all,
thanks for the input. I'll try this change tomorrow and if I find no problems I'll commit it.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von osm@pinns <osm@pinns.co.uk>
Gesendet: Donnerstag, 27. September 2018 11:23
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Beaches as a polygon
Sorry , had the wrong style ; yes 53 does show up
On 27/09/2018 10:14, osm@pinns wrote:
Just noticed that both Basecamp and Mapsource don't seem to show 0x53 :(
On 27/09/2018 09:48, osm@pinns wrote:
Hi Minko
Yes, 0x53 sounds good ; I have 53 down as 'flat , mud "
r
Nick
On 27/09/2018 09:05, lig fietser wrote:
Hi Nick,
Remarkable that this have not been noticed already!
I would suggest polygon type 0x53, typ viewer shows this as is the non NT version of 0x10C06 (if that matters). And please add natural=sand.
Suggestion:
natural=beach | natural=sand [0x53 resolution 20]
________________________________
Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk> namens nwillink <osm@pinns.co.uk><mailto:osm@pinns.co.uk>
Verzonden: woensdag 26 september 2018 23:04
Aan: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
Onderwerp: [mkgmap-dev] Beaches as a polygon
Hi
I noticed that the default style only renders Beaches as a point not a
polygon.
Beaches as a polygon may be unimportant to many but I feel that without
them maps are very misleading and incomplete -
see picture
http://files.mkgmap.org.uk/download/437/beach.jpg
(left default style , right with beach)
Garmin deems them important as they are included as an option in their kmtf
files for their City Navigator maps and nuvis etc.
Given the fact that only a very limited number of polygons are used in a
kmtf file, the beach inclusion seems quite significant.
They use 0x10C06 in City Navigator.
Just a suggestion
r.
Nick
--
Sent from:
http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev