On 2011-10-10 19:33, Bartosz Fabianowski wrote:
Replying to myself, I think I see the problem now. You are specifying paths relative to the current working directory while mkgmap searches relative to its installation directory. Try specifying the coastline file and the boundary directors as absolute paths.
No - the problem was that I'd forgotten the '=' in the command-line syntax. Correct: --coastlinefile=coastlines_europe-111004.osm.pbf What I'd entered: --coastlinefile coastlines_europe-111004.osm.pbf It might be a worthwhile improvement for mkgmap to notice dud syntax like that and either accept the form without the '=' sign, or to put up an error message. As it is, it *seems* to realise that the coastline file is as I'd flagged it, but then reports that it can't read such a file. Confusing. Steve P.S: I can now confirm that Bartosz's fix (specifying a separate coastline file) appears to have completely fixed my flooding issues. Thank you Bartosz. Hopefully my experiences will help the coastline/flooding/tiles people get more of a grip on what's causing this problem. As I said last time, if anyone wants my files for investigations, I'll keep them for a while - just ask me and I'll send them.