Re: [mkgmap-dev] Pending changes
Regarding your extra comment on #3, would it be really the case for bridges? What about any connected highway=* + bridge=yes? No objection for new additional changes El 11/2/21 a las 15:57, Ticker Berkin escribió: Hi all I've re-made this set of changes, along with a few improvements that I've gathered over the last 6 months. Following list numbering is the same as original patch, but include some [extra] notes + new items at the end. Relevant threads: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031375.html http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031424.html 1/ Sometimes charges for using a pedestrian highway are expressed as a fee rather than a toll, so pick this up in mkgmap:toll. 2/ Show bridges using type 0x10107. With the mapnik addition, these look good for narrow highways, but might not show for wide representations like motorways. 3/ Where it is likely that bits of highway might not be connected to the road/path system, use mkgmap:set_unconnected_type and mkgmap:set_semi_connected_type to stop the NET/NOD rather than relying on NETnoNOD (now disabled) and --check-routing-island-len=+ve, which is being suspected of causing problems on some devices and BaseCamp. [extra] In all cases where unconnected/semi-connected changes are mentioned, this only applies to lines not derived from an original/OSM standard highway. 4/ Quote some filter subst strings that contain spaces - no actual effect but clearer and safer. 5/ Have line for leisure=track even if area. 6/ Change the type for tracks/raceways etc from 0x30, which doesn't show on BaseCamp or MapSource, to 0x2a. 7/ For piers, if 'unconnecting', use marine type 0x1040c (Obstruction: Pier or Jetty) instead of footway. 8/ Change type for the various barriers from 0x17, which doesn't show on BaseCamp to 0x2b, see: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q1/030348.html 9/ Consider natural=cliff a barrier. 10/ Add motorway[_link] roundabouts (yes, some do exist). 11/ Unquote some numbers - no actual effect. 12/ Tweak some road speeds. [extra] A few more tweaked. 13/ Use 0x09 (high-speed ramp) for road class 4 links 14/ Add footway around car parks if 'connecting'. [extra] This change is disabled. 15/ Disable coastline. For a long time the tag was suppressed by the Sea processing and it adds little to the map. 16/ Improve railway platform names and suppress footway if not 'connecting'. 17/ Show disused:railway in the same way as railway=disused. 18/ Have cable_car, gondola, funicular as routable, by default with a toll and pedestrian only. 19/ Show "Course of old Railway", unless a highway has taken over the way (for you Eric, but I like it as well). [extra] This change is disabled 20/ Speed up car ferries. 21/ A few other layout/space fixes. Additional changes: 22/ motorroad=yes just sets mkgmap:fast_road, which generally increases the speed/class of the highway and decreases the resolution 23/ natural=landslide like other barriers (eg cliff) 24/ Don't generate (routable) line for highway=unclassified & area=yes; there are many instances in OSM where this is used to draw a polygon around a complex junction. 25/ Change the bridleway from 0x07 (Alley) to 0x16 (Trail) 26/ For ferry/platform/aerialway, blank out address fields to prevent it getting into the Address index 27/ Add comment about colour pallet to mapnik.txt Patch attached Ticker On Tue, 2021-02-09 at 11:30 +0100, Carlos Dávila wrote: On [1] Ticker proposed a set of changes to default style lines file. There was a long discussion about point #14, which ended without a consensus. Other changes didn't get any objection, but they didn't get into trunk. I agree with numbers 1, 6, 8, 10, 15, 17, 18. Also with 7 and 16, but for unconnected ways only, see #3. 2: more codes could be added for wider highways and their corresponding entries in mapnik.txt 3: not sure about this one, specially about semi-connected ways, which I think should remain as routable (also applies for 7, 16). [1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031375.html ___ 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 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Pending changes
Hi Ticker, while you are at it: I see lots of rather confusing texts like "gate" or "lift_gate" popping up in the map on my Oregon. I think they might be useful for mappers but they are not very useful for the normal user. Maybe it is only on my device but I don't see any need for this. Gerd Von: mkgmap-dev im Auftrag von Ticker Berkin Gesendet: Donnerstag, 11. Februar 2021 15:57 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Pending changes Hi all I've re-made this set of changes, along with a few improvements that I've gathered over the last 6 months. Following list numbering is the same as original patch, but include some [extra] notes + new items at the end. Relevant threads: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031375.html http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031424.html 1/ Sometimes charges for using a pedestrian highway are expressed as a fee rather than a toll, so pick this up in mkgmap:toll. 2/ Show bridges using type 0x10107. With the mapnik addition, these look good for narrow highways, but might not show for wide representations like motorways. 3/ Where it is likely that bits of highway might not be connected to the road/path system, use mkgmap:set_unconnected_type and mkgmap:set_semi_connected_type to stop the NET/NOD rather than relying on NETnoNOD (now disabled) and --check-routing-island-len=+ve, which is being suspected of causing problems on some devices and BaseCamp. [extra] In all cases where unconnected/semi-connected changes are mentioned, this only applies to lines not derived from an original/OSM standard highway. 4/ Quote some filter subst strings that contain spaces - no actual effect but clearer and safer. 5/ Have line for leisure=track even if area. 6/ Change the type for tracks/raceways etc from 0x30, which doesn't show on BaseCamp or MapSource, to 0x2a. 7/ For piers, if 'unconnecting', use marine type 0x1040c (Obstruction: Pier or Jetty) instead of footway. 8/ Change type for the various barriers from 0x17, which doesn't show on BaseCamp to 0x2b, see: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q1/030348.html 9/ Consider natural=cliff a barrier. 10/ Add motorway[_link] roundabouts (yes, some do exist). 11/ Unquote some numbers - no actual effect. 12/ Tweak some road speeds. [extra] A few more tweaked. 13/ Use 0x09 (high-speed ramp) for road class 4 links 14/ Add footway around car parks if 'connecting'. [extra] This change is disabled. 15/ Disable coastline. For a long time the tag was suppressed by the Sea processing and it adds little to the map. 16/ Improve railway platform names and suppress footway if not 'connecting'. 17/ Show disused:railway in the same way as railway=disused. 18/ Have cable_car, gondola, funicular as routable, by default with a toll and pedestrian only. 19/ Show "Course of old Railway", unless a highway has taken over the way (for you Eric, but I like it as well). [extra] This change is disabled 20/ Speed up car ferries. 21/ A few other layout/space fixes. Additional changes: 22/ motorroad=yes just sets mkgmap:fast_road, which generally increases the speed/class of the highway and decreases the resolution 23/ natural=landslide like other barriers (eg cliff) 24/ Don't generate (routable) line for highway=unclassified & area=yes; there are many instances in OSM where this is used to draw a polygon around a complex junction. 25/ Change the bridleway from 0x07 (Alley) to 0x16 (Trail) 26/ For ferry/platform/aerialway, blank out address fields to prevent it getting into the Address index 27/ Add comment about colour pallet to mapnik.txt Patch attached Ticker On Tue, 2021-02-09 at 11:30 +0100, Carlos Dávila wrote: > On [1] Ticker proposed a set of changes to default style lines file. > There was a long discussion about point #14, which ended without a > consensus. Other changes didn't get any objection, but they didn't > get > into trunk. I agree with numbers 1, 6, 8, 10, 15, 17, 18. Also with 7 > and 16, but for unconnected ways only, see #3. > > 2: more codes could be added for wider highways and their > corresponding > entries in mapnik.txt > > 3: not sure about this one, specially about semi-connected ways, > which I > think should remain as routable (also applies for 7, 16). > > [1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031375.html > > ___ > 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
Re: [mkgmap-dev] Pending changes
Hi all
I've re-made this set of changes, along with a few improvements that
I've gathered over the last 6 months. Following list numbering is the
same as original patch, but include some [extra] notes + new items at
the end.
Relevant threads:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031375.html
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031424.html
1/ Sometimes charges for using a pedestrian highway are expressed as a
fee rather than a toll, so pick this up in mkgmap:toll.
2/ Show bridges using type 0x10107. With the mapnik addition, these
look good for narrow highways, but might not show for wide
representations like motorways.
3/ Where it is likely that bits of highway might not be connected to
the road/path system, use mkgmap:set_unconnected_type and
mkgmap:set_semi_connected_type to stop the NET/NOD rather than relying
on NETnoNOD (now disabled) and --check-routing-island-len=+ve, which is
being suspected of causing problems on some devices and BaseCamp.
[extra] In all cases where unconnected/semi-connected changes are
mentioned, this only applies to lines not derived from an original/OSM
standard highway.
4/ Quote some filter subst strings that contain spaces - no actual
effect but clearer and safer.
5/ Have line for leisure=track even if area.
6/ Change the type for tracks/raceways etc from 0x30, which doesn't
show on BaseCamp or MapSource, to 0x2a.
7/ For piers, if 'unconnecting', use marine type 0x1040c (Obstruction:
Pier or Jetty) instead of footway.
8/ Change type for the various barriers from 0x17, which doesn't show
on BaseCamp to 0x2b, see:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q1/030348.html
9/ Consider natural=cliff a barrier.
10/ Add motorway[_link] roundabouts (yes, some do exist).
11/ Unquote some numbers - no actual effect.
12/ Tweak some road speeds.
[extra] A few more tweaked.
13/ Use 0x09 (high-speed ramp) for road class 4 links
14/ Add footway around car parks if 'connecting'.
[extra] This change is disabled.
15/ Disable coastline. For a long time the tag was suppressed by the
Sea processing and it adds little to the map.
16/ Improve railway platform names and suppress footway if not
'connecting'.
17/ Show disused:railway in the same way as railway=disused.
18/ Have cable_car, gondola, funicular as routable, by default with a
toll and pedestrian only.
19/ Show "Course of old Railway", unless a highway has taken over the
way (for you Eric, but I like it as well).
[extra] This change is disabled
20/ Speed up car ferries.
21/ A few other layout/space fixes.
Additional changes:
22/ motorroad=yes just sets mkgmap:fast_road, which generally increases
the speed/class of the highway and decreases the resolution
23/ natural=landslide like other barriers (eg cliff)
24/ Don't generate (routable) line for highway=unclassified & area=yes;
there are many instances in OSM where this is used to draw a polygon
around a complex junction.
25/ Change the bridleway from 0x07 (Alley) to 0x16 (Trail)
26/ For ferry/platform/aerialway, blank out address fields to prevent
it getting into the Address index
27/ Add comment about colour pallet to mapnik.txt
Patch attached
Ticker
On Tue, 2021-02-09 at 11:30 +0100, Carlos Dávila wrote:
> On [1] Ticker proposed a set of changes to default style lines file.
> There was a long discussion about point #14, which ended without a
> consensus. Other changes didn't get any objection, but they didn't
> get
> into trunk. I agree with numbers 1, 6, 8, 10, 15, 17, 18. Also with 7
> and 16, but for unconnected ways only, see #3.
>
> 2: more codes could be added for wider highways and their
> corresponding
> entries in mapnik.txt
>
> 3: not sure about this one, specially about semi-connected ways,
> which I
> think should remain as routable (also applies for 7, 16).
>
> [1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2020q3/031375.html
>
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-devIndex: resources/styles/default/lines
===
--- resources/styles/default/lines (revision 4600)
+++ resources/styles/default/lines (working copy)
@@ -19,8 +19,8 @@
# Assign the street name for house number search
highway=* & name=* {set mkgmap:street='${name}'}
-# Mark highways with the toll flag
-highway=* & (toll=yes | toll=true) {set mkgmap:toll=yes}
+# Mark highways with the toll flag (fee is sometimes used on pedestrian type routes)
+highway=* & (toll=* | fee=*) {set mkgmap:toll='${toll}' | '${fee}'}
# Hide proposed ways
highway=proposed | highway=proposal | highway=planned | highway~'.*proposed.*' {delete highway; delete junction}
@@ -40,6 +40,14 @@
highway=piste | highway=ski {delete highway}
highway=no | highway=none {delete highway}
+# Show bridges. Often these also have unconnected highway=track/... If so, we would like to cau
Re: [mkgmap-dev] Multipolygon Role Understanding
Hi Jan, the multipolygon processing happens before POI are generated. With the original MP mkgmap creates a POI for the unnamed leisure of the MP and probably also one for the outer way which (at this time) only has one tag name="Naturfreibad Sankt Märgen". There is no rule for such an object in the points file and therefore no POI is generated. I also wondered how to detect this error. I expected that JOSM would complain but it only shows an info message. Will look at this later. No idea yet how to find those cases with overpass. You may search for a specific tag like the leisure=water_park but I see no easy way to find all MP where the MP repeats an important tag of one of the outer ways. Gerd Von: mkgmap-dev im Auftrag von jan meisters Gesendet: Donnerstag, 11. Februar 2021 00:15 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Multipolygon Role Understanding Hi Gerd, yes, that works for me as described. As I understand, due to consecutive processing: nameless leisure gone, next matched? Another work_around I found by just changing the outer role to an inner. Both indicates imho more likely a mistagging. I´d like to have an overpass query to find similar examples - if anyone has an idea: appreciated ;-) Jan > Am 10.02.2021 um 23:13 schrieb Gerd Petermann > : > > Hi all, > > sorry, the style file is OK. I just tried with the (locally) corrected MP > (removed the leisure tag) and with that the name "Naturfreibad Sankt Märgen" > is shown in the map. > I think the multipolygon code removes all tags from the outer way which also > appear in the MP. The remaining tags > name=Naturfreibad Sankt Märgen > opening_hours=Jun-Sep: Mo-Su 09:00-18:00 > wheelchair=limited > are ignored by the default style. > > The behaviour is intended, but in fact a bit confusing. > > Gerd > > > Von: mkgmap-dev im Auftrag von Gerd > Petermann > Gesendet: Mittwoch, 10. Februar 2021 23:03 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] Multipolygon Role Understanding > > Hi Jan, > > I think the multipolygon describes the landuse, the outer way describes the > leisure. It makes no sense to have both tags on the MP. > Reg. the missing "Naturfreibad Sankt Märgen": > The default style doesn't use the name of the leisure, neither for the > polygon nor for the POI. Not sure why. I would have expected that inc/name > does that. > > Gerd > > > Von: mkgmap-dev im Auftrag von jan > meisters > Gesendet: Mittwoch, 10. Februar 2021 21:11 > An: mkgmap-dev@lists.mkgmap.org.uk > Betreff: [mkgmap-dev] Multipolygon Role Understanding > > Hi all, > > with my limited multipolygon knowledge I stumbled on missing poi tags here: > https://www.openstreetmap.org/relation/4077717 > > The multipolygon is tagged more limited than the outer role. > mkgmap renders the mp-tags, but drops the more useful outer tags (name etc.). > This useful it´s rendered on openstreetmap, but I can´t get it with mkgmap. > Tried default style and others, even OsmAnd (in OffRoad.jar) - all fail. > > So I wonder how or at all I could style the desired display in mkgmap. > Of course the mp itself might be wrong - don`t know - but then I suspect a > lot of them ;-/ > > Jan > ___ > 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 > ___ > 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 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
