I've been thinking about map ids lately, and wondering if it's time to implement a more structured approach to naming our Mapbox map ids for Park Tiles. Now that PT3 is really out there, we need to be more disciplined about making careful, methodical updates by testing them first in a separate environment. This means doubling the number of map ids I'm juggling in PT3 from 12 to 24. Considering this, I believe that developing custom map ids with logical, descriptive names may help keep everything straight.
Here's what I'm thinking:
Live PT3 Map IDs:
nps.pt3-standard-base
nps.pt3-standard-middle
nps.pt3-standard-overlay
Development PT3 Map IDs:
nps.pt3-standard-base-dev
nps.pt3-standard-middle-dev
nps.pt3-standard-overlay-dev
I'm not quite ready to move on this because I want to think it through a little more before forcing another npmap.js release.
nateirwin
commented
8 years ago
I've been thinking about map ids lately, and wondering if it's time to implement a more structured approach to naming our Mapbox map ids for Park Tiles. Now that PT3 is really out there, we need to be more disciplined about making careful, methodical updates by testing them first in a separate environment. This means doubling the number of map ids I'm juggling in PT3 from 12 to 24. Considering this, I believe that developing custom map ids with logical, descriptive names may help keep everything straight.
Here's what I'm thinking:
Live PT3 Map IDs:
nps.pt3-standard-basenps.pt3-standard-middlenps.pt3-standard-overlayDevelopment PT3 Map IDs:
nps.pt3-standard-base-devnps.pt3-standard-middle-devnps.pt3-standard-overlay-devI'm not quite ready to move on this because I want to think it through a little more before forcing another npmap.js release.
@nateirwin, @jakecoolidge, @jimmyrocks, @cwlawlis802: Questions, comments, concerns?