Tilemaker does not support maritime boundaries about tilemaker HOT 2 OPEN

Should be simple enough to implement, so I'll take a look this evening. The other maritime features already present in the OMT schema (See here) mentioned above would be fixed by adding boundary=protected_area and boundary=nature_reserve to

	if     boundary=="national_park" then Layer("park",true); Attribute("class",boundary); SetNameAttributes()

There's definitely room for the OMT schema for much more maritime information, I think - from my own research it seems like progress in porting OpenSeaMap data died in the cradle with the move from MapBox to OpenMapTiles. I've been considering writing something like a process-maritime.lua script that would handle seamark information present in the osm.pbf file, but it would also involve sorting the stylesheets - not a trivial endeavour. Possibly a conversation for a different repo though!

from tilemaker.

I'll be completely honest and say the particular reason is that I think they look terrible! osm-carto, and styles influenced by it, are the only mainstream maps to show all maritime boundaries. Other webmaps and standard print cartography don't.

That said, if they're in the standard OMT schema, I wouldn't be opposed to a PR to include them in the vector tiles as long as it included a corresponding change to the default stylesheet to not show them.

from tilemaker.