You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Route Details list is supposed to display the names of all roads along the route.
For example,
Turn left and go Hosur Road
Turn right and go MG Road
Keep left and go NH44
In this list, if the road has no name, OsmAnd omits the name. This is OK.
But OsmAnd also omits the name of the road if we turn into it via an exit link!
Since the link does not have a name, OsmAnd thinks that the subsequent road also has no name.
Usually we encounter such links when we join primary roads, which are supposed to take us hundreds of kilometers, and yet the details list fails to mention that road by name!
In this example, I have kept the distance short (3.2 km) so that I can show it in the screenshot. But this road is several km long, and I could have selected a distant point on it as destination. Anyhow, the point is, OsmAnd fails to name this road in the Details list.
(the starting point is at latlong 12.858806,77.65943)
The same thing happens when we encounter complex flyovers with different links joining different roads. Here are two examples from a single flyover (located @ latlong: 12.92066,77.66529):
[BUG#1]
This is an easily resolvable bug: Whenever there is a link, look for the name of the road after it.
Further, sometimes a mapper may have used a link to represent a median break between two halves of a major road. In that case we will have the same road name before and after the link. In such cases, it should be treated as a U turn. [BUG#2]
(In the last example, these are indeed U-turn links, which are routed under the flyover. Since the flyover passes between the two halves of a road, the mapper would think of this as a link, rather than a simple median break. But nonetheless, it is effectively a median-break, and a U-turn.)
The text was updated successfully, but these errors were encountered:
raindropsfromsky
changed the title
The Route Details list cannot show the name of road if starting wioth a link.
The Route Details list cannot show the name of road if it starts with a link.
Feb 25, 2019
BTW these links are distinctly U-shaped, and yet OsmAnd treats them like a "Slight right" or "right".
That is because it only looks for the first segment in the polyline.
In case of links, it should look for the entire shape, and then describe it. [BUG#3]
I am not sure how this label ("Observed") is treated.
From the past cases, it looks like an issue that may not be really there.
(Almost like saying "well, noted. Let's see...")
If so, IMHO this issue should be taken up, because-
(a) It is not so trivial.
(b) the root cause is identified (no investigation needed).
(c) IMHO it is easy to correct this (a low-hanging fruit).
The Route Details list is supposed to display the names of all roads along the route.
For example,
Turn left and go Hosur Road
Turn right and go MG Road
Keep left and go NH44
In this list, if the road has no name, OsmAnd omits the name. This is OK.
But OsmAnd also omits the name of the road if we turn into it via an exit link!
Since the link does not have a name, OsmAnd thinks that the subsequent road also has no name.
Usually we encounter such links when we join primary roads, which are supposed to take us hundreds of kilometers, and yet the details list fails to mention that road by name!
In this example, I have kept the distance short (3.2 km) so that I can show it in the screenshot. But this road is several km long, and I could have selected a distant point on it as destination. Anyhow, the point is, OsmAnd fails to name this road in the Details list.
(the starting point is at latlong 12.858806,77.65943)
The same thing happens when we encounter complex flyovers with different links joining different roads. Here are two examples from a single flyover (located @ latlong: 12.92066,77.66529):
[BUG#1]
This is an easily resolvable bug: Whenever there is a link, look for the name of the road after it.
Further, sometimes a mapper may have used a link to represent a median break between two halves of a major road. In that case we will have the same road name before and after the link. In such cases, it should be treated as a U turn. [BUG#2]
(In the last example, these are indeed U-turn links, which are routed under the flyover. Since the flyover passes between the two halves of a road, the mapper would think of this as a link, rather than a simple median break. But nonetheless, it is effectively a median-break, and a U-turn.)
The text was updated successfully, but these errors were encountered: