
WanMil wrote
I want to make a small statistic why restriction relations become invalid. Maybe the problem is so seldom that it's not worthy...
I have made a short stat with the high-prec branch: There are around 850 relations that are valid (RestrictionRelation.isValid() == true) after loading but that are not valid when the StyledConverter calls RestrictionRelations.convertRelation(MapCollector ...). So it seems to me as if the problem is greater than expected.
Yes, sounds too much. The only good case that I can think of is that the relation is saved by splitter because one of the related ways has at least one point within the boundary, but another part of the relation is outside of the boundary. If the via node is within the tile boundary we should be able to create the restriction. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Problem-with-turn-restriction-tp5795049p57951... Sent from the Mkgmap Development mailing list archive at Nabble.com.