Hi Steve, I don't understand all of your comments, but I think that either I missunderstand the code in RoadDef or something is wrong. The comment in RoadDef says * A road definition. This ties together all segments of a single road * and provides street address information. but the current implementation works different. In StyledConverter, we create one MapRoad instance for each segment of an OSM way. MapRoad itself creates one instance of RoadDef for this single segment. The RoadDef class contains code to handle multiple segments at the same zoom level. So, if my assumption is right that the order of segments does matter, we should probably make sure that the entries in NET1 appear in the right order, or we should not create multiple RoadDef instances for a single OSM way. Gerd Steve Ratcliffe wrote
Hi Gerd,
I see files where every road has a different subdivision and line number, but that need not matter as long as everything matches up.
I have found a way in which a file compiled with transparent is definately broken though. I have a file where the all entries in NET 1 are exactly the same (apart from the subdiv/line numbers) - they have the same offsets in the file etc.
However NET 3, which is basically a list of pointers into NET 1, is not the same and there are entries that do not point to the beginning of a NET 1 entry.
It may not be the only problem, but I will see if I can find out why it happens tomorrow.
..Steve _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/PATCH-v1-highwayCount-tp5748554p5748864.html Sent from the Mkgmap Development mailing list archive at Nabble.com.