Email or username:

Password:

Forgot your password?
SomeoneElse

I suspect I wasn't the only person a bit disappointed with the "OpenStreetMap's New Vector Tiles" discussion at news.ycombinator.com/item?id=4 earlier today. Using the data in the Shortbread-schema tiles as a way of looking at OSM data is like not going to a concert but reading about it the next day. You'll get some of the information, but will miss most of it.

Perhaps some examples will help...

11 comments
SomeoneElse

map.atownsend.org.uk/vector/in
Here's a pub which serves food and real ale, has a stone floor so you don't have to take your boots off, and is accessible by wheelchair. The bus stop outside has both a pole and a real-time display.

SomeoneElse

map.atownsend.org.uk/vector/in
Here's a milestone by the side of the Leeds and Liverpool canal. You can see the cycle route that is there too. However, zoom in a bit ...

SomeoneElse

map.atownsend.org.uk/vector/in
and you can see the directions on it.
This is all just using regular #OpenStreetMap data (so I guess it fits today's #30DayMapChallenge2024 ).

SomeoneElse

The schema used to extract the information is at github.com/SomeoneElseOSM/Some . The map style is github.com/SomeoneElseOSM/Some .
Documentation for both is ... as yet somewhat incomplete, but hopefully there's enough information there to show that doing this sort of thing really isn't that complicated.

SomeoneElse

It can be frustrating to see maps made with OSM data (by big companies that I won't link to here) that omit basic information - like hiking and cycling maps that don't say where you are and are not allowed to walk or cycle.
I suspect that the market for maps that show which pubs that have stone floors is a bit niche (i.e. me), but things like "can I get a wheelchair in" and "which hiking route goes through here" really aren't.

Ilya Zverev

@SomeoneElse I both agree and not agree. These new vector tiles are great for promoting Maplibre GL: before one had to set up their own vector tiles, or pay some company. And most uses of OSM are for the background layer, roads and buildings, which the new tiles provide.

But. The ShortBread schema, being created by german Geofabrik, has so many issues stemming from its origins. The first being labels — only in German and English, come on. It's the biggest problem with the new VT.

Ilya Zverev

@SomeoneElse

So I hoped to maybe use the official tiles for Every Door in the future, but it's clear I won't. Needs customization, target audience for the schema is unclear. German customers?

I hoped that people might make new exciting maps with the new VT, but the schema is the most limiting of all the options, so they won't. Matt's world map is much better at this:

watmildon.github.io/TIGERMap/W

And VT are definitely not for casual browsing, like Carto. There is nothing interesting there.

@SomeoneElse

So I hoped to maybe use the official tiles for Every Door in the future, but it's clear I won't. Needs customization, target audience for the schema is unclear. German customers?

I hoped that people might make new exciting maps with the new VT, but the schema is the most limiting of all the options, so they won't. Matt's world map is much better at this:

Simon Poole

@zverik @SomeoneElse name_en and name_de are essentially for compatibility with the openmaptiles schema. I don't think anybody plans on limiting things to that.

The question is likely more is the route OMT took to allow any name:xx in the tiles the best approach or wouldn't it make sense to have language(-groups?) specific tiles that contain the label layers.

Ilya Zverev

@simon @SomeoneElse yeah I don't think the language issue won't be resolved. But it is an indicator of the general narrowness of the schema.

I assume, MapTiler schema was born out of the Mapbox one, so there has been a lot of work poured into it. I wonder why not use it for a start, given it's the most popular on the market.

Simon Poole

@zverik @SomeoneElse IP/licensing reasons (that isn't really a secret).

SomeoneElse

@zverik @simon There are other ways of getting the right languages available in the right place without putting "all name:xx tags" on every object. For raster maps (of a small area with 4 languages) I do language processing up-front; some sort of "global region" processing might work on a worldwide scale. There are also wikidata-based options for translations and genuine exonyms.
In my case, the main reason I went with my own schema is that it did what I wanted and others did not.

Go Up