Getting OSMF vector tiles working in JOSM

Has anyone managed to get the OSMF hosted Shortbread Vector tiles working in JOSM?

I’m currently trying to create a layer that will just show the currently mapped buildings for ease of comparison with a second layer that shows postcodes in the UK. As the vector.openstreetmap.org tiles are the most up to date I would like to use those.

After failing to load a style json directly from osm.org using Maputnik I was able to use a copy of a style I already had locally as a starting point and strip out everything I didn’t want. However while I’m able to get the resulting file to load tiles in JOSM[1] I realised that the style was referencing Versatiles.org rather than OpenStreetMap.org. If I swap the tile URLs out JOSM spends a minute or two with a :hourglass_done: and then is only successful loading one of several tiles that should be in view.

Is there any solution to this? (Other than using a different source.)

If that is resolvable then the second issue I have is styling. While the style looks fine[2] on Maputnik in JOSM everything all data seem to have be rendered in the same style rather than just the layer that should be shown (it’s also using a lot of CPU). From what I’ve read that JOSM’s styling ability is limited for MVT layers but I’m not away of anything detailing what those limitations are. Is there a page anywhere that describes that MVT features does and does not support?


  1. With completely broken styling, see below ↩︎

  2. for what it is, it isn’t meant to be pretty ↩︎

1 Like

Hi. I am having the same problem: any style rule added applies to all layers not just the layer the style guide specified. I opened a ticket yesterday:

Small changes in JOSM could make community tile layers that aid mapping more easy to set up (vector tiles are much easier to set up than raster tiles for basic things like postcode polygons). I suspect that we are however from being able to do a full map style in JOSM. In fact I’m not sure it is wise loading “default” OSM vector tiles into JOSM as it struggles with large volumes of vector data.

1 Like

I was hoping that anything was was on a layer that was deliberately left undefined would be quietly dropped and not result in a lot of lag, but that seems not to be the case.

Ah yes, dropping that data would help keep lags to a minimum. Perhaps worth opening a JOSM ticket specifically for this.