Hi Brett, I started to write a new program to split up [EMAIL PROTECTED] .osm files. Fortunately, I checked out Osmosis before I got too far. It does most of what I want.
The resource problem in [EMAIL PROTECTED] is being caused by the large size of the Z16 and Z17 svg files. What I want to try is to use Osmosis with the bounding box option to cut the .osm file into strips and then create smaller svg files. For Z >12, the SVG files are processed strip by strip anyway. This should (theoretically) completely solve the current problems with unrenderable tiles. The only problem I can forsee is with ways that will cross one of the stripes without having a node within the stripe. I checked the source and AFAICS, Osmosis only include ways that have a node within the bounding box. It looks to me like it would be a pretty simple to change to AreaFilter and BoundingBoxFilter also include ways that cross the bounding box. Perhaps this feature should be turned on with an additional parameter? Thoughts? Thanks, Brent. ____________________________________________________________ Brent Easton Analyst/Programmer University of Western Sydney Email: [EMAIL PROTECTED] _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
