Hello, it seems that, using the OSM maps, speedlimits are shown only for the 'maxspeed' tag. The tags 'maxspeed:forward' and 'maxspeed:backward' are not used. This means that for areas with different speedlimits in the different directions the speedlimit will not be shown on mapfactor. One Example is 'line: 206068976' I'm using Navigator 12.3.0 on windows mobile. best regards Werner
Hello mdx, hope you've had a nice, relaxing vacation time. Maybe you can check this situation. Here the link https://www.openstreetmap.org/way/243274570 Best regards Werner
... I am very slowly reading old posts, sorry ... the current MCA format supports only one speed limit and I can confirm that at the moment tags 'maxspeed:forward' and 'maxspeed:backward' are ignored. Martin
Oh, that's really bad ... and I was so convinced that the app already is dealing with the :forward/backward :-( I understand that this would be a major change regarding your data ... however, can you tell something about the current plans and time frames to implement this?
@razor974 - I would update what I wrote in mail ... in reality we process RO:urban, RO:rural, RO:trunk, RO:motorway, RU:urban, RU:rural ... probably a long time ago. Could there be problem 'RO:urban' vs. 'ro:urban'?
Hi folks - are you planning to implement the maxspeed:forward/backward tag in the near future, or is it off the table for now? Quite a few roads have been tagged with this, especially before/after the crossing/intersection.