MapFactor Forum

mdx

You should see the simplest version mentioned sooner in all countries. Unfortunately recently I did not have time to continue on this task [current priority is release of "extended search", fix issues related to overflow of signed int for node id, ...]. I hope I will have better news for you "soon".
thanks for patience
Martin

jose1711

signed int? wasn't id always supposed to be unsigned? i am pretty sure a non-editor does not need id=-1 and the like.. just curious.

hurdygurdyman

As I've seen at German OSM-Forum http://forum.openstreetmap.org/viewtopic.php?pid=345339#p345339 according to a mailing-list lane-assist now should work.
I simulated the route shown on that picture http://up.picr.de/15083158ku.png and got the lane information but now simulating a rout in my home region http://www.openstreetmap.org/?lat=48.338706493377686&lon=7.828359603881836&zoom=15 , where several lane-informations are mapped, I couldn't get lane-assistance. My maps where updated some days ago.
Doesn't the Germany_south-map support the lane-assistance but Germany_west does?

mdx

Hi all,
I wanted to make another "micro-step" towards better OSM lanes integration and from various counts it looked like that tag="'destination:lanes" could be the next step. The first change was acceptance both of "turn:lanes:forward" and "turn:lanes" as on many motorways only the second is available (with combination of "destinations:lanes"). I experiment with germany_osm_north (Aug 2013, because it is waiting in a queue). You should see it on Early Map Access within an hour ...

Well ... it works more-or-less OK for example like:
http://www.openstreetmap.org/browse/way/4099428
although probably more useful would be to handle tag="motorway_junction" instead (on previous exit).

On the other hand it is giving non-sense lane indication and signs on:
http://www.openstreetmap.org/browse/way/206331862
destination:lanes = Hannover|Rotenburg/W;Bremen|Rotenburg/W;Bremen;Ehestorf
turn:lanes = left|through|through;right
Because left direction is connected with link against one-way, you will never see "Hannover" sign but instead "Rotenburg/W;Bremen". Wrong is probably also indication to the right, where you should see only "Ehestorf" and not all three cities "Rotenburg/W;Bremen;Ehestorf"??

I had a "small buffer overflow" for links like
http://www.openstreetmap.org/browse/way/201278920
but there is probably no simple way how to describe it and to list it N-times ...
Martin

imagic

Hi!

Thanks for the update.

Are you already considering the tag destination (without lanes) on the slip lanes? In most situations this (easier) tagging is sufficient and it is used much more often than destination:lanes, which - in my opinion - should only be used in complex situations.

Regarding the non-sense indication: you seem to imply that the tags relate to the end of the osm-way. This is not correct. In your example it is obvious, that the left direction can not be connected with the one-way link, therefore it must connect to the next osm-way in straight direction. You will not be able to create a lane assistance without building the connections between the lanes of separate osm-ways. For more complex situation I thought of introducing a relation (see [1]) to specify the lane connectivity. In this case such relation is not necessary as the correct connectivity could (and should) be estimated.

Please also have a look at [2]. Especially destination:ref is already in use.

br,
Martin

[1] http://wiki.openstreetmap.org/wiki/Proposed_features/lanes_General_Extension/ProposalPreVoting#Lane_connectivity
[2] http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details

mdx

Hi,
hurdygurdyman send me a link to discussion in German:
http://forum.openstreetmap.org/viewtopic.php?pid=364086#p364086
[It is bit hard for me to follow it in German]

The junction 206331862 as well as the one from German discussion
http://www.openstreetmap.org/#map=19/51.06144/13.69018
or directly
http://www.openstreetmap.org/browse/way/40550100
requires "micro-routing", find connected roads, ignore non-car roads, reject oneway in opposite direction. This could be done automatically with some defined search radius (max 100m?), but it is not that simple to do it during data/MCA processing. I would like to make this step forward, but there is not much time left to October processing.

Regarding tag destination - it is not integrated yet, but it is collected now, so I would like to add it soon.
thanks
Martin

rab

Hi,
I have an issue with turn and destination lanes to.
works:
https://www.openstreetmap.org/way/242088524
don´t work:
https://www.openstreetmap.org/way/151947003
would it be possible to handle "|none||through" the same way as "through|through|through"?
thanks

MapFactor Forum

Howdy, Stranger!

Categories

In this Discussion