You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our map capabilities endpoint does not return a value for the "fields" key for vector_layers. At the time of writing this, the values to be included in the vectory_layers array is still being debated for the TileJSON spec. It also appears that the discussion is not aligning with Mapbox's current implementation. An example of Mapbox's implementation can be seen on issue #83.
Tegola currently supports "fields" (or as they're called in MVT, "tags") to be fetched from data providers as well as set default tags per layer. With the way Tegola is currently designed data providers would need a way to be queried for the supported "fields" by layer. This result set would then need to be combined with the default tags. The mvt.Provider interface might need to be expanded, or the LayerNames() method be replaced with Layers() and return more information about the layer (i.e. Name and Tags).
Another thing to consider is that Mapbox's current implementation of "fields" consists of key:value pairs, where the key is the name of the "field" and the value is a description. If we want to support the description we would need to figure out how to best implement this (in the config?).
The text was updated successfully, but these errors were encountered:
Currently our map capabilities endpoint does not return a value for the "fields" key for
vector_layers
. At the time of writing this, the values to be included in thevectory_layers
array is still being debated for the TileJSON spec. It also appears that the discussion is not aligning with Mapbox's current implementation. An example of Mapbox's implementation can be seen on issue #83.Tegola currently supports "fields" (or as they're called in MVT, "tags") to be fetched from data providers as well as set default tags per layer. With the way Tegola is currently designed data providers would need a way to be queried for the supported "fields" by layer. This result set would then need to be combined with the default tags. The
mvt.Provider
interface might need to be expanded, or theLayerNames()
method be replaced withLayers()
and return more information about the layer (i.e. Name and Tags).Another thing to consider is that Mapbox's current implementation of "fields" consists of key:value pairs, where the
key
is the name of the "field" and thevalue
is a description. If we want to support the description we would need to figure out how to best implement this (in the config?).The text was updated successfully, but these errors were encountered: