It's all looking fine at the moment... http://osm.newportcoastsoftware.com/?zoom=11&lat=14.80342&lon=120.25358&layers=0BTFFFFFF http://osm.newportcoastsoftware.com/?zoom=8&lat=14.80342&lon=120.25358&layers=0BTFFFFFF
This view should be the coastline of the Philippines as produced by the coastline checking tools, plus captions of points (which is additional local layer) up to zoom 12... The coastline is showing as all white, which shows it's thought to be complete... there were 9 errors that showed up in the processing, but, I've not worked out how to make them display on the render yet... I did however find one on the main coastcheck at, which could be a 9 node way I guess... http://tile.openstreetmap.nl/coastlines.html?zoom=14&lat=12.8092&lon=123.26351&layers=B00T The output from the script was as follows if anyone is interested... osm2coast SVN version 0.12-20090223 $Rev: 4895 $ Reading in file: philippines.osm.bz2 Processing: Node(204k) Way(1k) Relation(0k) Reading in file: philippines.osm.bz2 Processing: Node(204k) Way(1k) Relation(0k) Node stats: total(204783), max(349935162) Way stats: total(1642), max(31405371) Relation stats: total(0), max(0) Pass 1: Collecting ways 887 collected, 755 closed, 0 zero-length Pass 2: Starting with 887 ways (epsilon=0.001) Pass 2a: Adding to R-Tree Pass 2b: Joining ways Remain: 3 / 887 (complete 41) Pass 2c: Consolidate remaining Consolidated: 3 Pass 3: Starting with 3 ways (epsilon=0.01) Pass 3a: Adding to R-Tree Pass 3b: Joining ways Remain: 3 / 887 (complete 41) Pass 3c: Consolidate remaining Consolidated: 3 Pass 4: Starting with 3 ways (epsilon=0.1) Pass 4a: Adding to R-Tree Pass 4b: Joining ways Remain: 2 / 887 (complete 41) Pass 4c: Consolidate remaining Consolidated: 2 Dumping remaining Total ways output: 887 ERROR: ld.so: object '/root/libtcmalloc.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object '/root/libtcmalloc.so' from LD_PRELOAD cannot be preloaded: ignored. coast2shp SVN version 0.12-20090223 $Rev: 4895 $ Reading in file: data/coastline.osm.gz Processing: Node(204k) Way(1k) Relation(0k) Reading in file: data/coast-merged.txt Max vertex count: 40137 Polygons: 796, Arcs: 2 Node stats: total(204783), max(349935162) Way stats: total(1642), max(31405371) Relation stats: total(0), max(0) Resizing subarea array to 1024 Arc: Found 1 large objects out of 2, removed 0+0 nodes, approx memory 0.0MB Polygon: Found 16 large objects out of 796, removed 0+0 nodes, approx memory 0.0MB Processing (399,399) (19937170.09,19937170.09)-(20037508.00,20037657.62) max tree depth:8 split ratio:0.55 processing data/coastline_c 9994 length=1615026 version=1000 type=5 extent:Envelope(13246555.08273602,511168.6087117034,14093233.21979928,2222622.647261268) number shapes=796 number nodes=755 processing data/coastline_i 9994 length=51586 version=1000 type=3 extent:Envelope(13149609.56089878,536857.1137060019,13326797.60526562,1280527.678805463) number shapes=2 number nodes=1 *processing data/coastline_p* 9994 length=176 version=1000 type=1 extent:Envelope(13155077.63132714,536857.1137060019,13244607.33367305,1158474.414221474) * number shapes=9 number nodes=9* *processing data/processed_p* 9994 length=1665602 version=1000 type=5 extent:Envelope(13224604.96875,511168.6087117034,14093233.21979928,2222622.647261268) * number shapes=980 number nodes=827* *processing data/processed_i* 9994 length=51586 version=1000 type=3 extent:Envelope(13149609.56089878,536857.1137060019,13326797.60526562,1280527.678805463) * number shapes=2 number nodes=1* done! Bold are the key bits, coastline_p contains errors, processed_p contrains the main coast polygons and processed_i contains the incomplete coastline, which, for this is where the bounding box of the data extract cut of some coast... I hope this helps, d 2009/2/23 Jim Morgan <j...@datalude.com> > D, > > Excellent. Someone who clearly knows what they're talking about. > > I'm extremely happy to hand this one off to you - you might have guessed I > was stabbing in the dark there, but it seemed like too big an issue to leave > alone. I'll keep my meddling browser out of there from now on ... > > I wasn't sure of the significance of the layer=-1 either, but as it was > already there I left it in. Feel free to change this if it doesn't look > right to you. > > Thanks for the tip about keeping coastlines down to ~ 250 node sections. > Didn't see any mention of this in the literature, so its worth publicising > this ... > > Jim > > D Tucny wrote, On Monday, February 23, 2009 02:51 PM: > > That section of coastline is now 2193 nodes, this will be too big for > > the 0.6 version of the API, coastline imported by the coastline import > > tool would typically make ways of up to 250 nodes if I recall correctly, > > over 2000 nodes will be a definite problem... It's an odd bit of > > coastline tagging though, layer=-1 stands out as the strangest bit... > > > > Along that section of coastline there are some odd bits that could > > potentially confuse rendering, such as water areas that overlap, but > > don't join, the coastline... But, this shouldn't confuse the coastline > > checker... > > > > I've split the coastline and fixed up some of these waterway/water area > > coastline joins, I'll look to get a copy of the coastline checker > > running here to see if I can see what it's problem is with this > section... > > > > d > > > -- > datalude: information security > e: j...@datalude.com > Philippines: +63 2 403 1311 / mob: +63 920 912 5830 > Hong Kong: +852 9100 7586 > w: http://www.datalude.com/ > > _______________________________________________ > talk-ph mailing list > talk-ph@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-ph >
_______________________________________________ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph