I believe it's time to generate a new vector tiles source called nps-places-reference. We've discussed this category of data in the past – it's for basic features that shouldn't be editable by park staff. Boundaries fall under this category, but it still makes sense to keep those as their own separate source. The Reference tiles will be used to test custom hydrography, coast lines, perhaps even our own hillshaded terrain in the future (gasp!).
To begin, I'm proposing we add this to satisfy one simple need: a line geometry for the Continental Divide.
I'd suggest we structure the layers as follows...
nps-places-reference-v1
nps_ref_natural_line
unit_code
name
type
nps_ref_hydro_line
attributes tbd
nps_ref_hydro_poly
attributes tbd
more to be added over time...
@cwlawlis802: I'd like to touch base with you to flesh out what could be included now and in the future in this new source. @jimmyrocks : Once we get a handle on what we wanted, we can make a plan with you for where to keep the data and how to set up tile rendering.
I believe it's time to generate a new vector tiles source called
nps-places-reference. We've discussed this category of data in the past – it's for basic features that shouldn't be editable by park staff. Boundaries fall under this category, but it still makes sense to keep those as their own separate source. The Reference tiles will be used to test custom hydrography, coast lines, perhaps even our own hillshaded terrain in the future (gasp!).To begin, I'm proposing we add this to satisfy one simple need: a line geometry for the Continental Divide.
I'd suggest we structure the layers as follows...
nps-places-reference-v1nps_ref_natural_linenps_ref_hydro_linenps_ref_hydro_poly@cwlawlis802: I'd like to touch base with you to flesh out what could be included now and in the future in this new source. @jimmyrocks : Once we get a handle on what we wanted, we can make a plan with you for where to keep the data and how to set up tile rendering.