<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>7 cze 2022, 17:55 od a.kasparas@gmc.lt:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div><br></div><div><span></span><br></div><div><br></div><div>On Tue, 2022-06-07 at 15:58 +0200, Mateusz Konieczny via Talk-lt wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Second, every year some country roads are paved. This is done taking into account importance of the stretch of the road (plus, if it goes over some village). So, important stretches gets paved and upgraded in the OSM database. If more gaps are left, then
the whole road is less important in country's or wider context. So state of map reflects state on the ground. In our book this is how things should be.<br></div></blockquote><div dir="auto">Also when it results in a short strips of higway=tertiary upgraded to highway=secondary<br></div><div dir="auto">because section of say 30m or 100m or 300m was paved?<br></div></blockquote><div><br></div><div>If this reflects reality, I see no problem (with one exception).<br></div><div>In practice, shortest stretch will be as long as "habitable" part of village.<br></div><div>Exception being for the case when there is some paved part just before intersection. LT law says it does not change right of the way rules. So, if you see stretch of less than ~5 meters upgraded to secondary just before intersection, I will agree this
is mistake. I also will not have a good suggestion how this should be micromapped. <br></div><div>For the reference, part 3.14 of KET „<span style="color: rgb(42, 42, 42);">Šalutiniame kelyje prieš pat sankryžą esantis ruožas su kietąja ar biriąja danga nedaro jo lygiareikšmio su kertamuoju ar prisijungiančiuoju keliu.“</span><br></div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="auto">As far as I know, this is really unusual and goes against how highway=.../primary/secondary/<br></div><div dir="auto">teriary/... is in general mapped or should be mapped.<br></div></blockquote><div><br></div><div>How things are generally mapped and how they should be mapped are a little bit different things. Not tooooo long ago it was usual to drive horse carriage. Not any more. At least in our part of the world. Not too long ago one had to go to big guys if he
wanted a decent map. Not any more. At least in our part of the world.<br></div><div>When I see other people do things differently, I usually ask why they do it their way, what good they achieve in choosing their way, what problems they have and only then I ask have they considered the way I'm doing this thing. I often learn lots of interesting
things. Sometimes I learn that I always did something wrong.<br></div></blockquote><div dir="auto">Still, I think that redefining "this shows overall role/importance of road" to<br></div><div dir="auto">"secondary/tertiary is not for road importance it is for road quality and for<br></div><div dir="auto">marking is specific rule applying" is not helpful.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Third, there are different legal requirements while driving on paved roads and on unpaved roads -- 90 vs 70 km/h max speed, right of the way for driving on first vs second.<br></div></blockquote><div dir="auto">this, as far as I know, can be easily achieved by tagging and using surface=* tags<br></div><div dir="auto">(some places have different legal rules on lit/unlit single/double carriageways,<br></div><div dir="auto">inside/outside settled areas and so on and trying to fit it into highway=* classes is rarely<br></div><div dir="auto">the best idea)<br></div></blockquote><div><br></div><div>Yes, we know about surface, max_speed ant other tags. We encourage to use them. But their use is orthogonal to selection of highway= tag.<br></div></blockquote><div dir="auto">Except highway=tertiary/secondary in Lithuania where surface tagging hijacks also<br></div><div dir="auto"> highway=* classification.<br></div><div dir="auto"><br></div><div dir="auto">And some other places, for example Poland has in turn<br></div><div dir="auto">"residential unpaved road marked as highway=track" problem, but we are cleaning this up.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Forth, in all practical applications we could come up at the time of the decision we expected that one will work with set where all or none of secondary and tertiary will be included. So, we considered this to be safe.<br></div></blockquote><div dir="auto">sorry, I do not really understand this part.<br></div></blockquote><div><br></div><div>Ok, give me a second chance to explain.<br></div><div>Here, in LT mapping community, we often ask how the results of our mapping activity will be used. Mapping for the sake of mapping? Maybe important for someone, not very much for community. Sorry.<br></div><div>What was important for most -- make navigation practical. Car, bicycle, kayak. Done, AFAIK. At least first two.<br></div><div>Printed maps -- there are numerous posted in parks, used in leaflets, etc. Done.<br></div><div>Used as a background for maps on websites of all the kinds. Done.<br></div><div>Then some personal and not so personal experiments.<br></div><div><br></div><div>Take navigation. When you search a way from Lisbon to Vladivostok, you will not use roads marked as secondary or tertiary in LT. When you search for way between two PoIs in the same/neighboring districts in LT -- you'll consider both--secondary and tertiary--and
even unclassified.<br></div><div>Take printed maps. If you print whole Europe, you'll not show secondaries in LT, tertiaries too. When you print map of national park, you'll select both and even paths.<br></div><div><br></div><div>So, at the moment of writing these rules we sat down and tough about problems. We found none. At least unsolvable.<br></div><div><br></div><div>What we gained in choosing to distinguish paved roads and unpaved ones is they are clearly marked on the maps. When I select in the OsmAnd that I want to avoid unpaved road, it will look for surface tags and will do a good job. But, I value an option to
visually see how much "zebra" (of secondary and tertiary roads) is the alternative, which was avoided.<br></div><div><br></div><div>Yes, it's a sin of mapping for presentation. We knew this when we decided. We limited this sin just for this case. And we're not ready to live without it.<br></div><div><br></div><div>How this affects people outside LT? In our opinion, minimally. Secondary and tertiary are neighboring categories (we do not map paths as autostradas). Their limits are somehow overlapping in both OSM and legal use. People crossing LT fast have better alternatives
and should not use them. People crossing LT slowly or who need to reach some odd place... most likely survive our weird way of mapping country roads. So, is there a reason to force a change?<br></div></blockquote><div dir="auto">While for routing it is unlikely to matter, it is going to be irritating for example for<br></div><div dir="auto">people making maps intended to look well or showing road networks etc.<br></div><div dir="auto"><br></div><div dir="auto">But mostly for consistency - similarly deciding to ban use of highway=motorway and<br></div><div dir="auto">instead of mapping highway=trunk motorway=yes would not lead to some tragic <br></div><div dir="auto">effects but would be quite weird and overall unlikely to be a good idea.<br></div><div dir="auto"><br></div><div dir="auto">This kind of fragmentation is unavoidable in some ways, but ideally would be <br></div><div dir="auto">limited and not increased step by step and ending with ornate rules for<br></div><div dir="auto">each country which actively contradict wider standards.<br></div><div dir="auto">And not supported by local rules.<br></div><div dir="auto"><br></div><div dir="auto">In this case mismapping for renderer is also not some utterly 2000% <br></div><div dir="auto">wrong idea like <a href="https://wiki.openstreetmap.org/wiki/File:Ankara_3D.png">https://wiki.openstreetmap.org/wiki/File:Ankara_3D.png</a> [1]<br></div><div dir="auto">but ideally would not be done.<br></div><div dir="auto"><br></div><div dir="auto">At this point I probably communicated what was more-or-less useful.<br></div><div dir="auto"><br></div><div dir="auto">As I am unlikely to provide anything new and useful and I am not part of<br></div><div dir="auto">local community so I think that I should leave this discussion.<br></div><div dir="auto"><br></div><div dir="auto">Hopefully this feedback was at least sorf-of-useful.<br></div><div dir="auto"><br></div><div dir="auto">I would just propose considering unifying classification at least for extremely<br></div><div dir="auto">tiny sections (<100m?) where displaying something as paved is unlikely<br></div><div dir="auto">to matter much and such isolated highway=secondary is quite silly.<br></div> </body>
</html>