I noticed all the roundabouts are now turned into oneways. Is this a change that is hardcoded recently in mkgmap? How to get rid of this, because there are bike path roundabouts which are twoway-bikelanes.
On Fri, Apr 22, 2011 at 01:32:11PM +0200, Minko wrote:
I noticed all the roundabouts are now turned into oneways. Is this a change that is hardcoded recently in mkgmap?
I believe that this has been the case for some two years or longer.
How to get rid of this, because there are bike path roundabouts which are twoway-bikelanes.
I found two references to junction=roundabout in the source code: src/uk/me/parabola/mkgmap/reader/osm/HighwayHooks.java src/uk/me/parabola/mkgmap/osmstyle/StyledConverter.java In HighwayHooks, you might want to remove this code: // if the way is a roundabout but isn't already // flagged as "oneway", flag it here if ("roundabout".equals(way.getTag("junction"))) { if (way.getTag("oneway") == null) { way.addTag("oneway", "yes"); } Another method would be to add oneway=no to the junction=roundabout ways. Best regards, Marko
Thanks Marko, I didn't notice it until now ;-) I cannot {add oneway=no} with the style file rules because all roundabouts are hardcoded set to oneway=yes. So this means if someone didnt tag a roundabout with a tag oneway=* there will be allways oneway=yes and I cannot see if this yes is hardcoded or not. Or can I use something like junction=roundabout & mkgmap:oneway=yes {set oneway=no} ?? Is it not better to add this rule to the default style file instead of hard coding it?
On 04/23/2011 10:12 AM, Minko wrote:
I cannot {add oneway=no} with the style file rules because all roundabouts are hardcoded set to oneway=yes. So this means if someone didnt tag a roundabout with a tag oneway=* there will be allways oneway=yes and I cannot see if this yes is hardcoded or not. Or can I use something like junction=roundabout& mkgmap:oneway=yes {set oneway=no} ??
Is it not better to add this rule to the default style file instead of hard coding it?
Junction=roundabout implies oneway=yes. I think the best solution is to add oneway=no tag to the mapping data if it is missing. -- harri
Hi Minko Might it be an fault in OSM-data? In Germany junction=roundabout imply oneway=yes. I don't know exactly how this is handled in other countries, but I won't be surprised, if this is globally implied. So if there is an roundabout, which isn't an oneway, you should add an oneway=no. Henning
Op 23-04-11 10:42, Henning Scholland schreef:
Hi Minko Might it be an fault in OSM-data? In Germany junction=roundabout imply oneway=yes. I don't know exactly how this is handled in other countries, but I won't be surprised, if this is globally implied. So if there is an roundabout, which isn't an oneway, you should add an oneway=no.
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev I might add that I suspect Ligfietser (=recumbent cyclist) is talking about cycleway roundabouts (or cycleways that circle a roundabout). Many of these (at least in the Netherlands) allow cyclists to take the roundabout in both directions.
So, yes, for cars roundabouts will be oneways mostly everywhere, but not necessarily for cyclists or pedestrians. I also note that the wiki tagging page suggests that oneway=yes is implied, so it follows that every non-oneway roundabout should be tagged oneway=no?
I agree, it should be done in the first place on osm. I've started to map the bike path roundabouts which allow twoway cycle traffic with oneway=no ;-)
I can't quite work out why we would consider a circular bit of road a roundabout if it isn't one way. The whole point of a roundabout is that you yield to traffic on the roundabout and go around in only one direction. What is special about the conventions of such a circular cycle traffic circle that would make us consider it a roundabout? Dermot -- -------------------------------------- Igaühel on siin oma laul ja ma oma ei leiagi üles
a) because it is part of that roundabout. See http://maps.google.nl/maps?f=q&source=s_q&hl=nl&geocode=&q=vathorst&aq=&sll=... Even the streetname here is officially called rotonde #1 (rotonde=roundabout) b) you have to yield to the cycle traffic on the roundabout c) If you work with the merkaartor editor its very convenient to draw roundabout circles ;-)
On 23 April 2011 16:41, Minko <ligfietser@online.nl> wrote:
a) because it is part of that roundabout. See
Yes, I see now, that alone makes it all make sense. And it also means that the oneway=no suggestions of others won't work either. The best I can come up with is to have separate ways for the cycle path part, either not tagged as roundabout at all or tagged oneway=no. I'd consider it very unwise to have roundabouts default to 2-way for cyclists. The ones around here do enough mad stuff without having them come the wrong way around a roundabout too... Dermot -- -------------------------------------- Igaühel on siin oma laul ja ma oma ei leiagi üles
This is a roundabout for cars and a cycle path in circular shape around it. I would just not tag the cycle way with roundabout and map what is on the ground. Don't tag for Merkaator … On 23 Apr 2011, at 8:41 , Minko wrote:
a) because it is part of that roundabout. See http://maps.google.nl/maps?f=q&source=s_q&hl=nl&geocode=&q=vathorst&aq=&sll=... Even the streetname here is officially called rotonde #1 (rotonde=roundabout) b) you have to yield to the cycle traffic on the roundabout c) If you work with the merkaartor editor its very convenient to draw roundabout circles ;-) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (7)
-
Apollinaris Schoell -
Dermot McNally -
harri -
Henning Scholland -
Lambertus -
Marko Mäkelä -
Minko