search

mapbox / tilejson-spec

JSON format for describing map tilesets.
255 stars 52 forks source link

data #43

Closed mapsam closed 6 years ago

mapsam commented 6 years ago

Adds the data section to 3.0

cc @GretaCB

mapsam commented 6 years ago

@GretaCB do you think it'd be worth adding a bit of extra context to this section? It's a bit unclear what data is used for, so some examples might be helpful.

GretaCB commented 6 years ago

@mapsam Definitely agree examples are needed. I'm unsure of current usecases of this field, due to improvements in tiling over the years. Curious if anyone else has thoughts on how this field is currently being used so that we can add some relevant examples.

cc @kkaefer @yhahn @stevage

yhahn commented 6 years ago

This used to be used for client-side overlays (displaying pins on a map after it's been loaded).

There are very few implementations AFAIK that support this, nor is the expected behavior around this key well defined. I'd be in favor of removing this property in a new version of the spec.

stevage commented 6 years ago

Huh. What's the relationship between this prop and https://github.com/mapbox/utfgrid-spec which does something pretty similar?

stevage commented 6 years ago

Oh now I remember. the "grids" property is for UTFgrid, which is sort of a rasterisation of the data for client-side interaction, "data" is a vector representation of all the data.

I don't think I have ever used it. It seems really marginal compared to these more likely requirements:

The "data" property as it stands is extremely limited: it has to be GeoJSON and it has to be tiled.

I'd recommend against including it.

mapsam commented 6 years ago

Thanks @stevage & @yhahn for the info! We'll add some clarifying notes to the 3.0 release, and plan on removing/deprecating in 4.0.