Hi Jon, Jon Burgess wrote: > This is how the data appeared when the existing polygons with holes were > run through the 0.4->0.5 conversion process. In 0.4 they consisted of a > single tagged way with disjoint segments. In the conversion, the > disjoint segments turned into multiple tagged ways and a relation was > created with them all as members. The conversion process was not > intelligent enough to assign them roles.
Does that create rendering errors? (E.g. holes not being rendered as holes?) Or are clients somehow figuring out that the holes are holes via a heuristic? Sorry to beat this to death here...it looks like clients have to handle a number of special cases for legacy data...I want to make sure I get them all so that my shapefile output isn't grossly different from what users see on the map. cheers bne -- Scenery Home Page: http://scenery.x-plane.com/ Scenery blog: http://xplanescenery.blogspot.com/ Plugin SDK: http://www.xsquawkbox.net/xpsdk/ X-Plane Wiki: http://wiki.x-plane.com/ Scenery mailing list: [email protected] Developer mailing list: [email protected] _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
