Dermot McNally schreef:
With the merge back into trunk, should I expect that the support there is identical to that on the multipolygon branch? [...] but if I process it using trunk code I get a mostly flooded map.
Anybody else seeing such differences?
Actually, I don't use the --sea-... option anymore, as there are a couple of tiles in the Netherlands flooded. This could the result of splitting (but I'm not entirely sure). It is *not* the geofabric cutout that is at fault, as one of these flooded tiles is in the centre of my.map >(but borders with http://osm.org/go/0E6W1PA_- so could still be a cutoff problem.
I wrote about this before (17-09-09 12:12).
I did not test the multipoligon branch - but I'm willing to do that; is there a rough outline of how to use svn branches here? (I'm perfectly able to compile and patch, I just never used svn branches before).
So basically, for trunk, I leave the sea-polygon thing out, I'd rather not swim to Utrecht ;)
V.
I brought the discusion on sea polygons back not because I'm that concerned with the sea. It's a nice to have. When I build South Africa in one tile it works very good. I build SA in one tile anyway for better routing. What is intersting is that when I build the exact same area in 4 tiles i.s.o. one, some tiles reverses the land & sea. I don't think there are broken coastlines in the original OSM data, because the sea polys are correct when using one tile. I am wondering if this might be a clue to other inter-tile problems? BTW I can not route across tile borders any more. Is any one else experiencing this, or am I blundering somewhere. I use --ignore-osm-bounds, (but I have always) would it have an effect? BennieD The opinions contained in this message are those of the sender only and do not reflect those of Sappi Limited or any of its subsidiary or associated companies. "This message, including any attachment(s), may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient of this message, please notify the sender thereof and destroy/delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies, jointly referred to as 'Sappi') shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Any opinions, statements, conclusions and other information contained in this message and/or its attachment(s) that do not relate or refer to the official business of Sappi Limited or any of its subsidiary or associated companies shall be regarded as neither provided nor approved by any Sappi company. Views expressed in this message or its attachment(s) may not necessarily be those of Sappi and Sappi cannot be held liable for any direct or indirect loss or injury resulting from the contents of a message and/or its attachments." Directors names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/SappiWeb/Investor+info/Corporate+governance/Board+resum... ##################################################################################### Scanned by MailMarshal - Marshal's comprehensive email content security solution. Download a free evaluation of MailMarshal at www.marshal.com #####################################################################################