Skip to content

Conversation

m-mohr
Copy link
Contributor

@m-mohr m-mohr commented Oct 3, 2023

@m-mohr m-mohr force-pushed the pmtiles-vector-property-schemas branch 3 times, most recently from 236d684 to 6d384b3 Compare October 3, 2023 00:52
@m-mohr m-mohr force-pushed the pmtiles-vector-property-schemas branch from 6d384b3 to b16e103 Compare October 3, 2023 00:53
@m-mohr m-mohr mentioned this pull request Oct 3, 2023
| href | string | **REQUIRED**. Link to a PMTiles file (usually ends with `.pmtiles`). |
| type | string | Recommended to be set to `application/vnd.pmtiles`. |
| pmtiles:layers | \[string] | For vector tiles, the layers to show on the map by default. If not provided, it's up to the discretion of the implementation to choose a layer from the `vector_layers` in the PMTiles metadata. |
| pmtiles:layer_properties | Map\<string, Map\<string, JSON Schema Object>> | For vector tiles, the properties/fields available for each layer and their corresponding [JSON Schema](#json-schema-object) as an object. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this meant to be exhaustive of all layer properties existing in the tileset (like in TileJSON), or only the properties/fields we want to visualize (like in the pmtiles:layers)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. I guess the second...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, that seems much more feasible than the former, though TileJSON vector_layers does not provide information about the possible enum values etc so the JSON Schema objects need to be constructed with outside knowledge.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, indeed. If we would have enough information in vector_layers, we would not need this construct at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants