26 Aug
2009
26 Aug
'09
4:14 p.m.
Chris Miller schrieb:
CG> - I have noticed problems due to partly missing shoreline segments CG> for CG> example at the Elbe. This, however, seems to be a problem in the CG> splitting of the data.
Assuming you're talking about the splitter... is this because the nodes that make up the shoreline are quite far apart where they cross a tile boundary? If so then it's possible the node outside the tile isn't getting included in the 'overlap'. Try specifying a larger --overlap value for the splitter and see if that helps (the default is 2000).
Would it be to complicated for the splitter to add a coastline-node exactly on the cutting boundary? (If this helps the seapoly- algorithm to work). What unit is the "2000" ? Chris