von Gerd
Petermann
Gesendet: Donnerstag, 28. Februar 2019 08:27
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] default style improvements
Hi Michael,
if I got you right you think the patches should be applied without any
changes?
Gerd
--
Sent from: http://gis.19327.n8.nabble.com
Hi Michael,
if I got you right you think the patches should be applied without any
changes?
Gerd
--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
regards, Michael
-Ursprüngliche Nachricht-
Von: mkgmap-dev Im Auftrag von Ticker
Berkin
Gesendet: Dienstag, 19. Februar 2019 11:57
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hello Michael
Thank you for your work checking all of this and your
11:01
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] default style improvements
Hello Ticker
I had a look into the 3 mails/proposals of yours.
Point and Lines are in a way easy. More interesting is the look into the
polygons.
To get the map impression I implemented the changes to polygons,
Hello Michael
Thank you for your work checking all of this and your feedback.
See embedded for my comments.
Kind regards
Ticker
On Sun, 2019-02-17 at 11:01 +0100, Michael Poesdorf wrote:
> Hello Ticker
>
> I had a look into the 3 mails/proposals of yours.
> Point and Lines are in a way easy.
: [mkgmap-dev] default style improvements
Hi Michael
The changes to the default style haven't been applied and released yet.
There were in 3 posts on 21-Jan around 06:30.
Regards
Ticker
On Sat, 2019-02-09 at 07:49 +0100, Michael Poesdorf wrote:
> Hi Ticker,
>
> I'm not sure if I've see
5. Februar 2019 09:26
> An: Ticker Berkin ; Development list for
> mkgmap
>
> Betreff: Re: [mkgmap-dev] default style improvements
>
> Hi Ticker,
>
> I'd prefer to get some positive feedback. I did not even try to
> understand
> the reasons for all these changes because
: Dienstag, 5. Februar 2019 09:26
An: Ticker Berkin ; Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi Ticker,
I'd prefer to get some positive feedback. I did not even try to understand
the reasons for all these changes because I hoped for some feedback from
: Dienstag, 5. Februar 2019 09:12
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi Gerd
Given the lack of comments and objections, can you apply my 3 patches
to default style points/lines/polygons from 21-Jan
Thanks
Ticker
Hi Gerd
Given the lack of comments and objections, can you apply my 3 patches
to default style points/lines/polygons from 21-Jan
Thanks
Ticker
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi
Some comments on "Some changes to be considered?"
On Sun, 2019-01-13 at 11:11 +, Joris Bo wrote:
> Hello,
...
> Some changes to be considered?
> ===
> Different kinds of public transport are mapped to the same symbol.
> For now I choose
Date: Mon, 21 Jan 2019 07:09:30 +
From: Ticker Berkin
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] default style improvements
Hi
Here is a patch to change some TYPE element numbers in
default/polygons:
Changes are:
0x17, which shows as "Park" in green, is curr
Grazie mille, Lorenzo
Van: mkgmap-dev Namens Lorenzo
Mastrogiacomi
Verzonden: maandag 21 januari 2019 00:19
Aan: mkgmap-dev@lists.mkgmap.org.uk
Onderwerp: Re: [mkgmap-dev] default style improvements / updated typ-file
Attached my italian translation too.
Lorenzo
Il giorno dom, 20/01/2019
Hi
Here is a patch to change some TYPE element numbers in
default/polygons:
Changes are:
0x17, which shows as "Park" in green, is currently used for these OSM
objects:
park, playground, common, garden, greenfield, meadow, grass,
village_green, square/plaza
Keep this mapping for leisure=park,
Hi
Here is a patch to change some TYPE element numbers in default/lines:
Changes are:
Use 0x30 for leisure=track instead of treating it like a footpath.
0x30 was introduced in the last set of changes as the code for various
sports tracks (gallop, raceway)
Use 0x0b (Road) instead of 0x06 as the
Hi
Here is a patch to change some TYPE element numbers in default/points:
Changes are:
Always use 0x2f0c instead of 0x4e00 for amenity=toilet.
0x4e00 isn't findable. 0x2f0c is "Other:Rest Area/Tourist Info".
add:
tourism=resort [0x2b04 resolution 24]
This is searchable under the "Lodgings" >
Hi
Sorry about the delay in replying.
I couldn't decide on a good colour for Historic either, and, at the
moment, I use the same colour for Building, Historic and Amenity.
I think the default style should output them as polygons not POI. A typ
-file can consider not rendering these polygons.
>
> > Van: mkgmap-dev Namens
> > Ralf Kleineisel
> >
> > Verzonden: zaterdag 19 januari 2019 11:57
> >
> > Aan: Development list for mkgmap
> >
> > Onderwerp: Re: [mkgmap-dev] default style improvements / updated
> > typ-file
> >
>
jk bericht-
> Van: mkgmap-dev Namens Ralf
> Kleineisel
> Verzonden: zaterdag 19 januari 2019 11:57
> Aan: Development list for mkgmap
> Onderwerp: Re: [mkgmap-dev] default style improvements / updated typ-file
>
> Hi,
>
> On 1/19/19 11:38 AM, Joris Bo wrote:
>
> &g
Super Ralf, Danke!
Habe es schon verarbeitet
Gr Joris
-Oorspronkelijk bericht-
Van: mkgmap-dev Namens Ralf Kleineisel
Verzonden: zaterdag 19 januari 2019 11:57
Aan: Development list for mkgmap
Onderwerp: Re: [mkgmap-dev] default style improvements / updated typ-file
Hi,
On 1/19/19
Hi,
On 1/19/19 11:38 AM, Joris Bo wrote:
> That’s very kind, thank you.
>
> Attached an excel with the exported translations up to r4262
>
> Just add a column for any new language
I just corrected a few issues in the german column.
20190119b Translations r4262.xlsx
Description: MS-Excel
Wesley Martins
Verzonden: zaterdag 19 januari 2019 11:18
Aan: Development list for mkgmap
Onderwerp: Re: [mkgmap-dev] default style improvements / updated typ-file
Hello Joris,
I have interest in help with portuguese (0x10) translate.
How can I help?
Regards,
Wesley
On Sat, Jan 19, 2019 at 7:04
t; Thx, I’ll have a look
>
>
>
>
>
> *Van:* mkgmap-dev *Namens *
> osm@pinns
> *Verzonden:* vrijdag 18 januari 2019 12:44
> *Aan:* mkgmap-dev@lists.mkgmap.org.uk
> *Onderwerp:* Re: [mkgmap-dev] default style improvements / updated
> typ-file
>
>
>
> Hi
, but you just find out that this
is not bullet proof
Thx, I’ll have a look
Van: mkgmap-dev Namens osm@pinns
Verzonden: vrijdag 18 januari 2019 12:44
Aan: mkgmap-dev@lists.mkgmap.org.uk
Onderwerp: Re: [mkgmap-dev] default style improvements / updated typ-file
Hi Jorus
Great job!
Just
Joris Bo
> Gesendet: Sonntag, 13. Januar 2019 12:11
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] default style improvements / upated typ
> -file
>
> Hello,
>
> I modified the type-file up to Ticker's changes in build r4262.
> Latest changes can also be fo
for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements / upated typ-file
Hello,
I modified the type-file up to Ticker's changes in build r4262.
Latest changes can also be found on
https://github.com/Jorisbo/Mkgmap-Mapnik-Style-Garmin
It already reflects some new mapnik colors which
Hi Gerd
Here is summary of the changes:
A few minor layout tidy-ups
Add GBR section to inc/access_country
Do aeroway=runway/taxiway/taxilane as lines unless marked as area=yes
and show these lines even when also a highway
Ignore more highways when abandoned/disused/demolished
Ignore more
: Re: [mkgmap-dev] default style improvements
Hi Gerd
I had indented to do the highway_ramp change but the edit got into my
pending list rather than the current change - sorry
shop resolution remaining at value in old version - fine
Areas of highway=service/residential/living_street explicitly
ons discussed before. For me this version
> would be OK.
>
> Gerd
>
>
>
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Donnerstag, 10. Januar 2019 10:37
> An: Development list for mkgmap
> Betreff: Re
rsion
> would be OK.
>
> Gerd
>
>
>
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Donnerstag, 10. Januar 2019 10:37
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] default style impr
] default style improvements
Hi Gerd
Here a new version of the patch with this wording.
Ticker
On Wed, 2019-01-09 at 15:15 +, Gerd Petermann wrote:
> # squares and plazas
> place=square [0x17 resolution 22]
> highway=pedestrian & (area=yes | mkgmap:mp_created=true) [0x17
&g
Hi Gerd
Here a new version of the patch with this wording.
Ticker
On Wed, 2019-01-09 at 15:15 +, Gerd Petermann wrote:
> # squares and plazas
> place=square [0x17 resolution 22]
> highway=pedestrian & (area=yes | mkgmap:mp_created=true) [0x17
> resolution 22]
> # following rule also renders
ent list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi
I propose this in 'lines':
# squares and plazas
place=square [0x17 resolution 22]
# squares/plazas are also mapped as highway=pedestrian areas.
# The tag area=yes forces the polygon element to be considered
.org.uk
> > > im Auftrag von Ticker Berkin <
> > rwb-mkg...@jagit.co.uk
> > >
> > Gesendet: Montag, 7. Januar 2019 10:55
> > An:
> > mkgmap-dev@lists.mkgmap.org.uk
> >
> > Betreff: Re: [mkgmap-dev] default style improvements
> >
> &
missing
>
> Gerd
>
>
> Von: mkgmap-dev <
> mkgmap-dev-boun...@lists.mkgmap.org.uk
> > im Auftrag von Ticker Berkin <
> rwb-mkg...@jagit.co.uk
> >
> Gesendet: Montag, 7. Januar 2019 10:55
> An:
> mkgmap-dev@lists.mkgmap.org.uk
>
> Betreff
Hi
On Sun, 2019-01-06 at 08:50 -0500, Greg Troxel wrote:
> Bernhard Hiller writes:
>
> > I often travel on bike in "nowhere land", where hotels and
> > restaurants
> > are rare. So I think it is good to show both PoIs if a hotel
> > contains
> > a restaurant. Of course, it would be more
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] default style improvements
Hi
Reading some of the relevant wiki pages, I am finding the wording
ambiguous.
https://wiki.openstreetmap.org/wiki/Key:area
https://wiki.openstreetmap.org/wiki/Tag:highway%3Dpedestrian
https://wiki.openstreetmap.org
Hi
Reading some of the relevant wiki pages, I am finding the wording
ambiguous.
https://wiki.openstreetmap.org/wiki/Key:area
https://wiki.openstreetmap.org/wiki/Tag:highway%3Dpedestrian
https://wiki.openstreetmap.org/wiki/Area
It seems wrong that the handling of the area= tag is not consistent
It's not what I meant.
The example you provided is a multipolygon relation and multipolygons
are always areas regardless if area=yes is set or not.
So this is not a valid example, actually I can not find one really
evident of missing area=yes on pedestrian areas.
Lorenzo
Il giorno dom,
Betreff: Re: [mkgmap-dev] default style improvements
Hi Gerd
Not sure what you mean here. Only complete polygons, either from closed
ways or generated by multipolygon get to be interpreted by 'polygons'
style processing.
Ticker
On Sun, 2019-01-06 at 16:58 +, Gerd Petermann wrote:
> Hi
Hi
I don't see anything in the OSM definition of a square that requires it
to come from a multipolygon relation
https://wiki.openstreetmap.org/wiki/Tag:highway%3Dpedestrian
Ticker
On Sun, 2019-01-06 at 17:46 +0100, Lorenzo Mastrogiacomi wrote:
> Il giorno dom, 06/01/2019 alle 12.45 +,
> Von: mkgmap-dev im Auftrag
> von Lorenzo Mastrogiacomi
> Gesendet: Sonntag, 6. Januar 2019 17:46
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] default style improvements
>
> Il giorno dom, 06/01/2019 alle 12.45 +, Ticker Berkin ha s
Von: mkgmap-dev im Auftrag von Lorenzo
Mastrogiacomi
Gesendet: Sonntag, 6. Januar 2019 17:46
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Il giorno dom, 06/01/2019 alle 12.45 +, Ticker Berkin ha scritto:
> Hi Lorenzo
&g
Il giorno dom, 06/01/2019 alle 12.45 +, Ticker Berkin ha scritto:
> Hi Lorenzo
>
> I know that the OSM definition says square should have area=yes, but
> I
> find a vast number where there is no area tag and they seem to be
> square/piazza, eg
>
>
Hi Gerd
see embedded answers
Regards
Ticker
On Sun, 2019-01-06 at 09:11 +, Gerd Petermann wrote:
> Hi Ticker,
>
> I think I understand the changes in the points file and in
> inc/accesss_country and they look okay to me. I agree that it is
> better to have the hotel POI
> for those cases
Bernhard Hiller writes:
> I often travel on bike in "nowhere land", where hotels and restaurants
> are rare. So I think it is good to show both PoIs if a hotel contains
> a restaurant. Of course, it would be more relevant to know how other
> users of OSM Garmin maps think about this topic (I use
Ticker Berkin writes:
> I know that the OSM definition says square should have area=yes, but I
> find a vast number where there is no area tag and they seem to be
> square/piazza, eg
>
> https://www.openstreetmap.org/relation/5174171
>
> With Italy data from July 2018, I get about 5000
Hi Lorenzo
I know that the OSM definition says square should have area=yes, but I
find a vast number where there is no area tag and they seem to be
square/piazza, eg
https://www.openstreetmap.org/relation/5174171
With Italy data from July 2018, I get about 5000 highway=pedestrian
polygons
cker
Berkin
Gesendet: Samstag, 5. Januar 2019 18:18
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi Gerd
I'd tried to get all the optical changes out of the way in the first 2
patches, but I missed a few and it seemed easier to fix them as I
spotted them.
This
both. Probably a case for continue ?
Gerd
Von: mkgmap-dev im Auftrag
von Ticker Berkin
Gesendet: Donnerstag, 3. Januar 2019 17:52
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi Gerd
Here is another patch. I've m
Il giorno sab, 05/01/2019 alle 17.18 +, Ticker Berkin ha scritto:
>
>
> highway=pedestrian always generates a line and, unless area=no, a
> polygon. This is the OSM representation of a square/plaza, and, in many
> cases, needs the routing given by the edge. The area tag is often
> missing,
> von Ticker Berkin
> Gesendet: Donnerstag, 3. Januar 2019 17:52
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] default style improvements
>
> Hi Gerd
>
> Here is another patch. I've made the changes as you suggested and the
> following changes:
>
>
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Donnerstag, 3. Januar 2019 17:52
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi Gerd
Here is another patch. I've made the changes as you suggested and the
following
: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Donnerstag, 3. Januar 2019 11:59
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] default style improvements
>
> Hi Gerd
>
> Do you want me to do another version of this patch before you commit
> it?
&
Hi Ticker,
yes please, my understanding was that the patch was not accepted.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Donnerstag, 3. Januar 2019 11:59
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style
Hi Gerd
Do you want me to do another version of this patch before you commit
it?
I'd like to get on with the next set of changes; minor things like
removing horse= can be done with these.
Regards
Ticker
On Thu, 2018-12-13 at 10:54 +, Ticker Berkin wrote:
> Hi Gerd
>
> My rationale was
_
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Samstag, 8. Dezember 2018 18:19
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] default style improvements
>
> Hi Gerd
>
> Here is revision to defaultStyleTidy3.patch. The changes are:
remove the mop up rule instead of adding a lot of "try to guess
better" rules.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Samstag, 8. Dezember 2018 18:19
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] def
Hi Gerd
Here is revision to defaultStyleTidy3.patch. The changes are:
1/ change highway=trail to highway=path; add bicycle=no instead of
track
2/ don't generate routable line for highway=rest_area
Regards
Ticker
Index: resources/styles/default/inc/access_country
I see there is no distinction between a pedestrian highway and a footway/path
yet.
On the generic new map I use 0x11 for pedestrian highways and 0x10 for
cycleways, but you can do the opposite.
Both are routable lines and visible on most (?) devices. Also for steps I use
another routable line
Yes - I saw the nodes marked "part of way ..." and just presumed they
were the road; sorry for wasting your time.
Ticker
On Wed, 2018-12-05 at 17:06 +, Gerd Petermann wrote:
> Hi Ticker,
>
> the first example shows why it is not a good idea to make it
> routable. It is not connected to the
von Ticker
Berkin
Gesendet: Mittwoch, 5. Dezember 2018 16:17
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi Gerd
Here are some polygons with area=yes:
https://www.openstreetmap.org/way/515054518 this needs to be routable
otherwise the navigation
d
> >
> > ________________
> > Von: mkgmap-dev im Auftrag
> > von Ticker Berkin
> > Gesendet: Dienstag, 4. Dezember 2018 17:50
> > An: Development list for mkgmap
> > Betreff: Re: [mkgmap-dev] default style improvements
>
for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi Gerd
Yes, I think trail > path, maybe with {add bicycle=no} would be better.
The services/rest_area question is slightly different from this topic.
I've not made a line element for any highway=services, but, having had
a trawl thro
th and other typos during the
> last weeks.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Dienstag, 4. Dezember 2018 17:50
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] default sty
Hi
In the latest release default style, all highway=* except pedestrian
that have area=yes or come from multi-polygon relations have id 0x05
(Parking lot)
In my latest batch of changes the polygon rule is:
(highway=services | highway=rest_area) & area!=no [0x05 resolution 22]
but, I agree, it
Hi
Once my current batch of changes is out of the way the next one will be
to change some if the element ids, mostly as per posting 13-Nov-18
17:25 UTC
I still think these typ files should go into trunk now and the default
-typ branch is abandoned
I don't like the name 'mkgmap.txt', not sure
Hi
I agree that bad tagging should be fixed in OSM but:
1/ some of the tags you mention here are acceptable
2/ it is a continuous job as some common mis-uses just get repeated
3/ its time-consuming
4/ it may be difficult for a non-local person to know exactly what the
highway really is
5/ my
On the forum someone asked if highway=services could be added to the polygons
style.
https://forum.openstreetmap.org/viewtopic.php?pid=728618#p728618
For example like in the generic new maps:
landuse=retail | highway=services [0x08 resolution 22-20]
If added, prevent that it also will be mopped
t; im Auftrag von Ticker Berkin
> Gesendet: Dienstag, 4. Dezember 2018 17:50An:
> Development list for mkgmapBetreff: Re: [mkgmap-dev] default style
> improvements
> Hi Gerd
> I had various OSM maps for Great Britain, Spain, Italy, Belgium
> andMorocco of different ages and when
fixed lots of highway=footpath and other typos during the last weeks.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Dienstag, 4. Dezember 2018 17:50
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi Gerd
ed path.
> 2) rest_area is converted to a routable way?
>
> Gerd
>
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Montag, 3. Dezember 2018 16:04
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev]
. Dezember 2018 16:04
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements
Hi
Here is the third batch of default style changes. Changes are:
Add GBR section to inc/access_country and tidy up the layout
LINES
A few minor layout tidy-ups
Do aeroway=runway/taxiway
Hi
Here is the third batch of default style changes. Changes are:
Add GBR section to inc/access_country and tidy up the layout
LINES
A few minor layout tidy-ups
Do aeroway=runway/taxiway/taxilane as lines unless marked as area=yes
and show these lines even when also a highway
Ignore more
-dev] default style improvements
Hi Gerd
Given lack of objections to any of this, could defaultStyleTidy2.patch
be applied to trunk.
Thanks
Ticker
On Fri, 2018-11-16 at 16:56 +, Ticker Berkin wrote:
> Hi
>
> This is the next batch of default style changes.
>
> I don't thin
Hi Gerd
Given lack of objections to any of this, could defaultStyleTidy2.patch
be applied to trunk.
Thanks
Ticker
On Fri, 2018-11-16 at 16:56 +, Ticker Berkin wrote:
> Hi
>
> This is the next batch of default style changes.
>
> I don't think anything here is contention. The changes are:
>
Hi Ticker,
> Is this logic general enough to move into the default style?
This is a solution for my maps and I have tried to make it universal.
There could be other propositions, for example some people could prefer
name of the road over ref number or include name into shield (but it
doesn't
Hi Andrzej
Is this logic general enough to move into the default style?
I assume it replaces:
# Display highway shield for mayor roads if they have a ref and make
them searchable by their name
(highway=motorway | highway=trunk) & ref=* {name '${ref|highway
-symbol:hbox}'; addlabel '${name}'}
Hi Ticker,
I guess variables like mkgmap:us_interstate come from my style. I use
them for shields with road reference numbers. There are dedicated
shields for US maps and standard shields for other countries. These
variables allows to create single style for both cases.
This is an example
Hi Gerd, Andrzej & maybe others
I'm trying to understand a couple of bits of logic in the default
style:
'relation' sets mkgmap:us_interstate, mkgmap:us_usroute and
mkgmap:us_state but I can't find any use of these tags. It looks like
these were introduced in revision 3979, 5-Aug-2017 following
Hi
This is the next batch of default style changes.
I don't think anything here is contention. The changes are:
A few minor white-space changes that I missed in the previous batch.
Remove unnecessary () in conditions
Add tmp: prefix to tags that are just used by the style logic, so it is
d I'll reflect these changes
against the TYP-file proposal.
Kind regards,
Joris
-Oorspronkelijk bericht-
Van: mkgmap-dev Namens Ticker Berkin
Verzonden: dinsdag 13 november 2018 18:26
Aan: Development list for mkgmap
Onderwerp: Re: [mkgmap-dev] default style improvements
All
I'd li
All
I'd like any thoughts on changing and introducing new element TYPE
numbers for various OSM objects. I propose:
POINTS:
Use 0x2f0c instead of 0x4e00 for amenity=toilet always.
0x4e00 isn't findable. 0x2f0c is "Other:Rest Area/Tourist Info".
Use 0x3200 instead of 0x660f for barrier=bollard
Hi Ticker,
OK, got your point. If no one complains I'll commit that patch on thursday.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Montag, 12. November 2018 16:19
An: mkgmap development
Betreff: Re: [mkgmap-dev] default style
Hi Gerd
I thought of doing it as you suggest but then it's wrong when there
is a [type ...] part, which I also want indented, ie
some condition {
action1;
action2;
...
} [0x01 resolution 20]
not that I can find any examples. And I feel that its clearer that all
parts of a
no;
set mkgmap:road-speed=1;
}
Besides that the changes are OK for me.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Montag, 12. November 2018 13:03
An: mkgmap development
Betreff: [mkgmap-dev] default style improvements
Hi
I'd like to make
Hi
I'd like to make quite a few changes and improvements to the default
style.
Some of these should be non-contentious:
The first change I propose is to make the layout consistent and clearer
and I've attached a patch to do this for the points/lines/polygons
files. The only change here is
87 matches
Mail list logo
