[HOT] landuse=residential and routing problems

[Pierre Béland]

I did not say to create "virtual roads" but to interpret the imagery in a specific context, here rural area in a semi-artic region with no road infrastructures like paved roads or gravel roads going to the small villages.  We have to interpret the traces on the sand. At the rainy season, cattle, people walking and cars leave traces in all directions.
It is yes difficult to interpret in such areas and this is a challenge to provide significant infos about the road network. 

We often see that  too many highway=unclassified are traced in parallel going from village A to village B.

Your answer is too short saying do not connect A and B.

In the case of this specific village, Mulla, which ways would you keep as highway=unclassified?If you keep one from the north, one from the south, would you say that this is impossible that a car goes through the village to move from the north way to the south way ? 

What is virtual, what is the reality in such a context?  :-)  
Pierre 


      De : john whelan <jwhelan0112 at gmail.com>
 À : Vao Matua <vaomatua at gmail.com> 
Cc : hot at openstreetmap.org
 Envoyé le : lundi 31 juillet 2017 16h07
 Objet : Re: [HOT] landuse=residential and routing problems
   
Echoing Pierre's comments should we come up with better instructions?  I think the requirements for the NGOs are where do people live and how do we get there?
Which suggests we want the settlements and a highway to reach them.
This is probably different to normal OSM which sometimes seems to be map everything in sight.
Personally I think there are two styles of mapping a settlement.  One tightly maps round the buildings the other is looser in nature and maps groups of buildings more loosely.  Both have advantages.  Tight mapping means you can get a rough approximation of population without mapping every building.
Mapping fewer highways would let us cover a larger area for the same amount of effort but how to describe the optimum mix is difficult.
Cheerio John
On 31 Jul 2017 3:40 pm, "Vao Matua" <vaomatua at gmail.com> wrote:

Interesting situation Marco, one I've often seen in Ethiopia.I would suggest that creating "virtual" roads is not a good idea.
The purpose of routing software is to help someone navigate the real world. If someone were to try to drive an imaginary route it would cause problems. Additionally I find it hard to imagine a scenario where someone would use a routing app to go 100 meters through a village.
The paths you have mapped are fine, but the key thing is to map the route to the next village or highway=unclassified+.
Emmor
On Mon, Jul 31, 2017 at 10:22 AM, mbranco2 <mbranco2 at gmail.com> wrote:

Thank you all for your answers, and for your hints not to map too much detailed.
For my question, the key seems to be: "roads must share a node to let the routing software calculate...".
A lot of times I find situations like this one [1]: there are no roads connecting the highway from NW and the highway from SE, but I think routing sw must know the two highways are connectable...
So, I'm undestanding that sometimes it could be necessary to draw "virtual" roads around or inside a village, to connect between them several external roads (of course, if it seems appropriate, looking at the aerial images).If so, maybe it could be suitable to put a note (if not a specific tag), indicating that segment as "virtual"?
Thank you again,Marco
[1] http://www.openstreetmap.org/# map=16/12.0527/14.4386


______________________________ _________________
HOT mailing list
HOT at openstreetmap.org
https://lists.openstreetmap.or g/listinfo/hot




______________________________ _________________
HOT mailing list
HOT at openstreetmap.org
https://lists.openstreetmap. org/listinfo/hot


_______________________________________________
HOT mailing list
HOT at openstreetmap.org
https://lists.openstreetmap.org/listinfo/hot


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/hot/attachments/20170731/859db2e6/attachment.html>