Site structure for tiles.openstreetmap.us

[quincylvania]

Per conversation with @jake-low, it makes sense for the OSM US Tileservice to include all the components someone would need to display a web map. I'm thinking the site structure of tiles.openstreetmap.us could look something like this:

Permalink	Content
/	Homepage with overview of the tileservice, quick start info, and site directory
/tiles/	List of available tilesets
/vector/{tileset}.json	TileJSON files describing each vector tileset
/vector/{tileset}/{z}/{x}/{y}.mvt	Individual vector tiles
/raster/{tileset}.json	TileJSON files describing each raster tileset
/raster/{tileset}/{z}/{x}/{y}.jpg	Individual raster tiles
/styles/	List of available map stylesheets
/styles/{stylesheet}.json	Individual MapLibre stylesheet JSON files
/fonts/	List of available fontstacks ("glyphs" in a stylesheet)
/fonts/{fontstack}/{range}.pbf	PBF font files suitable for use in stylesheets
/sprites/	List of available spritesheets
/sprites/{spritesheet}.png /sprites/{spritesheet}.json	Spritesheet assets

[ZeLonewolf]

I'm curious about including sprites in the tile server since that's usually a style asset?

[quincylvania]

@ZeLonewolf So the idea is for everything on the tileserver to be compatible with each other and also be modular. The sprites will still be developed in tandem with first party styles, but I think it's helpful to keep them generic. Third party style developers will have instant access to high quality map icons hosted for free. MapLibre supports multiple spritesheets in a single style, so developers can mix OSM US sprites with their own. Spritesheets are usually just a few KB, so it's okay if people are loading a few extra icons they don't reference.