Richard Fairhurst

The intention is that, if you use the latest code with the default OMT-compatible profile/config, it will generate the planet correctly. If you find significant departures from this then please...

Could you confirm whether this happens with the default OMT-compatible schema?

tl;dr - the default profile is optimised to minimise coastline issues. Please use the [same config](https://github.com/systemed/tilemaker/blob/master/resources/config-openmaptiles.json#L20) for the ocean layer and report if you still have significant issues. --- Applying...

I'm not suggesting anything other than > If there is a bug in the default config/profile then please do report it here I'm afraid I'm finding this issue very hard...

Please supply more details: - what OS version - Apple Silicon or Intel - what libraries you've installed, what versions, and how you installed them

Yes, would be good to get this finally sorted out - .mvt is in real danger of turning into the new Markdown (everyone uses it, no two clients parse/write it...

> Maybe you could open an issue on https://github.com/systemed/potlatch3 and discuss adding an "Access-Control-Allow-Origin" header somewhere around here: https://github.com/systemed/potlatch3/blob/master/com/airhttp/ActionController.as#L149-L174 Yes, I think that'd work. I'll probably do a new release...

Could you paste the line you've added to your config JSON to include this file?

(deleted my previous erroneous comment) If I create a tileset of New Jersey with the New Brunswick station geojson, and with the above line added, I can run vt2geojson successfully...

No problem at all. vt2geojson is a huge help for debugging, particularly if you use it in conjunction with `tilemaker-server` which is pretty barebones and should guarantee there's no caching...