When you know the details (it was like that 50 years ago)… when you don’t it is a large single undetermined area.
1 Like
Thanks - this is a great example.
It’d be interesting to see what it looked like with slightly different values for fill-color and fill-opacity here - maybe you could have a go?
Yes. That’s something that could be looked at.
Here bus stops are also disappearing because of:
- a name clash with the road name and other feature names (often quite long in this area)
- the size of the text used on other features (which as noted above is deliberately larger)
That’s a deliberate styling decision to avoid driveways etc. dominating the map.
This style is designed as a map, rather than a background upon which other data is displayed. One of the Versatiles styles (use the layer selector to see) would be better for that.
Specifically for airports:
- a way of representing areas of runways that isn’t widely used by mappers is in the schema.
- It is not in these vector tiles (see this issue)
As ever, the schema explains what should be available from what (vector) zoom level. Vector zoom levels are one less than raster zoom levels (which is what is shown on osm.org).
Edit: issue 30 created for the building colour.
Sorry, it wasn’t that clear. I was talking about the width key on those linear objects. But that seems to be not in either.
Another one…
I 90/I 94 label looks normal, but I 88/IL 110 get’s huge.
https://www.openstreetmap.org/#map=11/41.8552/-88.0808&layers=S
5 Likes
The trigger that causes it to go from “small” to “large” is “more than 5 digits”. Rebrand those interstates to motorways (M is much wider than I) and you’ll be fine 
I have no idea whether MapLibre supports “width in pixels of X in current font”. If it does and isn’t too computationally horrible, then that might work.
There is also a different (more serious) issue where the available shields I’ve created aren’t big enough for some of the sillier refs out there. There is an issue for that I think, with a bit more detail.
Great job - this is now my default style!
Is this an issue with the style, or something else? At first glance it looks like the boundary between different residential areas but when editing, it’s not that. Is it a join of some sort?
https://www.openstreetmap.org/#map=17/52.509176/-1.845049&layers=S
Not visible in any other layer.
Those lines look like vector tile boundaries to me. When polygons cross tile boundaries they get split up and depending how styling of a border is done these unintended lines can become visible. Here you can see that gray residential landuse polygons are affected, but yellow school polygons are not.
2 Likes
This is a bug: Check landuse buffers · Issue #85 · pnorman/spirit · GitHub
2 Likes
Follow-up on bus stops:
- zoom level 19, still nothing.
- zoom level 20, a few, here with the wrong icon (due to platform I guess).
Carto displays it IMHO better:
- at zoom level 16
- displays simplified icons
- at zoom level 19
- displays icons, labels only if there is enough room.
At first glance, the visual style looks great! Two small requests, if possible:
- Render
highway=trunkat the same zoom level ashighway=motorway: they are equally important, especially where “true” motorways do not exist (as is the case in some entire countries). The example of Belgium illustrates the main issue with not displaying them together: many isolated motorway fragments amidst empty areas. - Consider a font with proportions similar to Noto Sans SemiCondensed. I think this would allow for displaying more close labels without compromising legibility. The main benefit would be for long street names competing for display space.
This is so much better than the first version!
Another tweak: yellow color of tertiary roads is hard to distinguish from the surroundings, particularly the tan-colored farmland. It needs some orange hue, I’d say, to more closely match secondary roads:
View Larger Map
2 Likes
Few more suggestions:
Labels at the higher zoom levels are way too large. To me labels at z=13 seem pleasant, but they get larger and larger the more I zoom in. Especially street names are way too large (and therefore scarce) for me. Housenumbers on the other hand stay reasonably sized at any zoom they are displayed.
Same goes for icons like the already mentioned bus stops - too large and too late.
For my German taste road shields are way too prominent, they could be a lot smaller, e.g. with a thinner border and less padding. The mentioned long ref numbers are really a problem in DE because 5/6 character refs are rather common. On tertiary roads the change in size doesn’t happen and they are perfectly readable.
2 Likes
Especially, as like in France there’s a space between the “class of road” and the “number” 'suffix). Main roads have short refs, so minor ways are more prominent than major roads!
See zoom levels 13 and 14, worst IMHO 18.
BTW, on the second example 2 different sizes for L 545. As some L 545 are blurred, maybe a side effect.
Otherwise, the style is rather pleasant.
https://github.com/SomeoneElseOSM/SomeoneElse-vector-web-display/issues/20
Can you explain what you mean by the “wrong icon”? What icon would you like to see there, and how would it differ from the bus stop icon that is currently displayed? Here is a debug link to the area. The only data available to the map style is what you can see when you hover over a bus stop on that link.
Edit: Issue 20 is somewhat resolved, at least for bus stops; other examples of the same problem may need looking at on a case-by-case basis.
Can you explain what you mean by the “wrong icon”?
Sure: as for me, but it can be a cultural issue, the icon looks like a stop, waiting for a train, not a bus.
Maybe an icon like the one for the station close by, maybe with a vertical bar to represent a bus stop pole.
BTW the station icon/name are hidded (my guess) by the CCTVs on lower zoom level :-(.
As mentioned previously the choice of using a larger text size for road names etc. was a deliberate one. There is certainly some room for adjustment**, but I can’t read most of the text on OSM Carto on a phone screen without squinting, so I’m not planning to make it that small (the rest of the OSM UI is fine, by the way).
** the information board signs at https://www.openstreetmap.org/#map=18/48.385576/-4.483881&layers=S could definitely be smaller. The memorial there? Maybe.
Edit: https://github.com/SomeoneElseOSM/SomeoneElse-vector-web-display/issues/21
Edit 2: https://github.com/SomeoneElseOSM/SomeoneElse-vector-web-display/issues/21 (for road names) is now fixed. Please raise any other issues with labels as separate issues suggesting exactly what looks wrong now and how it should look. There are already a number of issues for shields.
Do you consider the label placement a bug? Not sure if you’d want me to log it.
Point and polygon features are labelled below their centre. Especially at lower zooms and for features like small countries, this produces confusing results:
Label for Czechia is over Austria, label for Austria is over Slovenia, Latvia is over Lithuania, Andorra is around Barcelona, Luxembourg is entirely over France, and Isle of Man is in the sea
Label for Helsinki is in the sea
I actually show them as soon as they’re available in the schema, so you’d need to suggest a change there for that.
I doubt that I’ll be doing that, but you could certainly have a go! This line in the style defines which fonts to use (that’s the default in my deployment; OSM’s is likely different). Recent MapLibre versions work with system fonts (that documentation is a bit cryptic; my recollection is that you can just miss the “glyphs” entry out and amend “text-font” and it’ll use system fonts).
1 Like
Please do log it. It may be that fixing it causes further problems, but it’s worth investigating. The offset you’re seeing is here - perhaps try without?
Edit: https://github.com/SomeoneElseOSM/SomeoneElse-vector-web-display/issues/24 , now resolved.
1 Like