[mkgmap-dev] default style improvements

Tue Dec 4 17:01:16 GMT 2018

Hi Ticker,

I think highway=trail is often used in the USA.
When I stumbled over one it often looked like a highway=path + surface=ground.

With rest_area I see the same problem as with highway=services mentioned here:
https://forum.openstreetmap.org/viewtopic.php?pid=728618#p728618

And yes, I fixed lots of highway=footpath and other typos during the last weeks.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
Gesendet: Dienstag, 4. Dezember 2018 17:50
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvements

Hi Gerd

I had various OSM maps for Great Britain, Spain, Italy, Belgium and
Morocco of different ages and when I found a highway tag that wasn't
handled, looked at a few examples of the way/relation on OSM.

For trail, I don't think I found many examples and 'track' seemed a
reasonable option because, the example I looked at:

https://www.openstreetmap.org/way/445188184

joined to 2 other 'track's. 'path' is probably better but that there is
logic to convert 'path' to footway/cycleway/bridleway.

The rest_area example I looked at didn't have any other highway into
it, just a closed highway=rest_area with the beginning and end along
the main highway. It seemed best to make it routable so that navigation
turns into it correctly, rather than it saying a 90 degrees turn to the
center, after having gone past the entrance.

One of the maps I used was about 6 months old, and lots of the examples
of bad tagging I went looking for, I found you'd recently fixed in OSM.

Ticker

On Tue, 2018-12-04 at 15:27 +0000, Gerd Petermann wrote:
> Hi Ticker,
>
> I did not yet understand all changes. Can you explain why
> 1) highway=trail is translated to track? I would have used path.
> 2) rest_area is converted to a routable way?
>
> Gerd
>
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag
> von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
> Gesendet: Montag, 3. 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/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 highway tags that are not suitable for routing
>
> Convert
> highway=steps/corridor/stepping_stones/elevator/escalator/platform to
> footway / bicycle=no and remove later test for steps
>
> Convert highway=crossing/virtual to path
>
> Don't convert footway to cycleway, but more rules to convert path to
> footway/cycleway/bridleway
>
> Add footway around man_made=pier even if area=yes
>
> Fix common bad tagging for highway= and convert to the better values
>
> Put routable path around highway=pedestrian closed areas;
> squares/plazas often don't have other routing joining all entry/exit
> ways. Similarly for footway. Then continue to allow any polygon
> processing
>
> Handle some rarer highway types
>
> Show any other water lines
>
>
> POINTS
>
> Removed all the {set cityxx/tmp:city}, & cityxx/tmp:city!=yes,
> continue
> with_actions bits. This was put in as a safety measure when this
> block
> of rules was added, see
> http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2013q2/017943.html
> [mkgmap-dev] Adaptions in style (needed to make good use of) for
> overview2 branch
> From Felix Hartmann extremecarver at gmail.com on Tue May 7 18:44:46
> BST 2013
> and has never had any effect - there are no other tags on objects
> with
> place=city/town... that need to be rendered
>
> Group the rules amenity=restaurant/fast_food, cuisine= to clarify,
> simplify and show better how it relates Garmin "Food & Drink" search.
> The only overall effect of this is that
> amenity=fast_food,cuisine=pizza/grill moves to the "Fast Food"
> category. Add some a few more cuisines.
>
> For leisure=* where sport might be involved, show the sport if no
> name
> available. NB name will defaulted by the standard code in <finalize>
>
> Show canal/lock as 0x6505 (Water Features>Canal)
>
>
> POLYGONS
>
> Show aeroway=runway/taxiway/taxilane only if marked as area=yes
>
> Increase resolution that amenity=cafe/fast_food/restaurant, shop=*
> show
> at
>
> Show place=suburb
>
> Show highway=pedestrian as square/plaza unless explicit area=no, but,
> for highway=footway, only show if explicit area=yes
>
> Don't assume any other closed highway is parking area, just
> services/rest_area
>
> Show all historic=*
>
> Show drydock, canal & lock differently from standard natural=water,
> and
> use a different code for small lakes
>
> Show any other water area
>
> Show all man_made=* unless explicit area=no
>
> Regards
> Ticker
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev