I don't think that Minkos style shows cycleways on the left/right side of a road - am I wrong? - Anyhow they would usually have a oneway tag already in OSM data. Also definitely no uphill/downhill arrows - which nearly never actually have a oneway tag (and only sometimes I add one during processing). The routing I don't want to stress right now - I still have to play a bit on that due to the rather recent Basecamp changes again... (as I usually want to have routing in both directions, but at different priority). I probably won't be able to get hard facts till monday with OSM links... (I cannot access my own SVN server - and mkgmap SVN is taking ages and often not responding either here). On 24.04.2014 23:35, Gerd Petermann wrote:
Hi Felix,
the problem with oneway=-1 should not appear often. If I got you right you say that there is another problem with roads that have a direction? Can you give an example ? Just the OSM id of a way that causes problems with your style. Maybe we find that Minkos style has the same problem, maybe we find that Minko found a better solution.
Gerd
Date: Thu, 24 Apr 2014 23:26:53 +0800 From: extremecarver@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] oneway reverse patch
On 24.04.2014 23:14, Minko wrote:
I dont have any difficulties with mkgmap showing arrows in the wrong direction, or routing going the wrong way. Well it didn't seem to work for me (at least using the patch with the most up to date mkgmap trunk version last Thursday) I do see that sometimes the bike lane is drawn on the wrong side of the road, but this is a Garmin bug. In Mapsource and Basecamp it is rendered on the correct side, but on the newer Garmins it is rendered on the opposite (wrong) side. On older units it is rendered ok. Garmin is aware of this issue but hasn't done anything for years. That's a bug - correct. But actually it's not sometimes, but all the time - I was first to report this over 3 years ago on the us garmin forum (mapsource 6.14) and actually one dev sometimes even promised to fix it but never got to do it. All asymetric lines are rendered the opposite side on Computer vs GPS unit (I think mapsource 6.13 is same side as GPS however). Garmin doesn't care as they never used asymetric lines (I was the first one to do so using transparency) - the only had asymetric lines in so far as older GPS units/mapsource 6.13 didn't render 2,4,6,8,... pixel lines actually in the middle (only 1,3,5 where actually centered) - and now that they started using asymetric lines - they don't have them dependent on direction...
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev