[REPEAT] Boundaries layer features tagged maritime_boundary = 1 in error

[nvkelso]

The fix we landed in #1482 in v1.5 somehow didn't make it into the build?

[zerebubuth]

Hmmm.... That's really annoying. How many times have we "fixed" this now?

I tried to reproduce this locally and with the latest (internal v1.6c) build, and wasn't able to find the maritime_boundary property on the USA-CA border around zooms 7-10. Although there's so many name properties it's possible I missed it.

Could you let me know exactly which URL is being used to load those tiles, from the Chrome/Firefox inspector network tab ideally, please? Privately, if this is an internal build.

[nvkelso]

The Tag Explorer uses the public Nextzen build based on v1.5 schema:

https://tangrams.github.io/explorer/#9.0/48.6320/-123.0359/kind/country

Eg it's loading tiles like:

• https://tile.nextzen.org/tilezen/vector/v1/512/all/8/40/87.mvt

[nvkelso]

This looks fine in dev. Fingers crossed it looks good on staging as well.

[nvkelso]

Looks good in staging, closing :)

[nvkelso]

This happened again in dev, reopening into v1.7 milestone.