[talk-ph] Luzon Coastline

[Jim Morgan]

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: jim at datalude.com
   Philippines: +63 2 403 1311 / mob: +63 920 912 5830
   Hong Kong: +852 9100 7586
   w: http://www.datalude.com/