glug was indeed originally written before data-driven styling was a thing, but it got expressions support in April 2022. So you would write that example as

icon_image match(mode,
   "bus", (case_when(station, "bus_station", "bus_stop")),
   "tram", "bus_stop",
   "subway", "subway",
   "train", "train",
   "airplane", "airplane",
   "airport", "airport",
   "" )

It’s pretty much word-for-word. The main differences are:

• glug doesn’t need “get”, you can just use a bareword
• case in MBGL is case_when in glug to avoid a Ruby keyword clash
• property names are hyphenated in MBGL, underscored in glug

If you want to copy and paste this into irb to try it out:

require 'glug'
puts Glug::Stylesheet.new {
  source :default, type: "vector", tiles: ["http://localhost:8080/{z}/{x}/{y}.pbf"], minzoom: 0, maxzoom: 14, default: true
  layer(:pois, zoom: 10..13) {
    icon_image match(mode,
      "bus", (case_when(station, "bus_station", "bus_stop")),
      "tram", "bus_stop",
      "subway", "subway",
      "train", "train",
      "airplane", "airplane",
      "airport", "airport",
      "" )
  }
}.to_json

and you’ll see that it compiles to exactly the JSON you’ve used above.

You would expect me to say this, but glug works well for me. Invisibly compiling “proper” expressions into the verbose M?GL JSON format is a massive timesaver.

There are things I would slightly rework in it (and might do if I have a moment) - the pre-processed cascading was intended for the days before data-driven styling and is probably less crucial now, so could perhaps be dropped. And there are a couple of minor infelicities that are implementation details in a Ruby DSL (precedence concerns mean that it’s best to surround everything with brackets; colours can’t be easily inferred within a data-driven query expression so need a .to_hex_color postfix). But generally I’m pretty happy with it.

This is only on the development server which doesn’t have any access to the main OSM database, including your user login. The real feature won’t require you to create a separate account.

I note that you and the table both sidestep the vexed issues of highway=track and highway=service ;)

Lots of administrations do release traffic data under an open licence - you’d be surprised!

But it’s something that we could and should survey for OSM. Broad-brush AADT equivalents (Average Annual Daily Traffic) are actually pretty easy to survey - the cut-off for safe cycling is often ~1000 cars per day, and you can extrapolate that pretty easily on many quiet roads.

only GraphHopper seems to be using the class:bicycle tag for it´s routing

That’s because it’s a terrible subjective tag and shouldn’t be used. Much better to tag objective speed limits and traffic levels.

Nice write-up!

One other significant milestone I’d mention is Kothic-JS, which I think was the first serious attempt to render OSM in-browser from Javascript as far back as 2011.

https://lists.openstreetmap.org/pipermail/mapcss/2011-June/000196.html

At the risk of stating the obvious, ArcGIS is developed by a company with a budget of $1.1bn, while the OpenStreetMap Foundation has a budget of about £27.50 and one full-time employee. I’d honestly suggest if you have a problem with ArcGIS, you ask the $1.1bn company.

I’m quite disappointed by your messages Richard and CactiStaccingCrane.

Many people, including me, have tried to explain to slice0 over a long time how his challenges could be resolved and how his particular mapping interests could be reconciled with the community. He has shown no interest in doing anything other than his own way, all the time. Attempts to engage have been met with walls of text and paranoid ramblings about the police.

At some point you stop being constructive and just throw your hands up in the air. You may of course have superhuman patience in which case I can only applaud you.

If you want to have the discussion on the community forum, maybe stop trolling the user diaries?

The problem with this is that “Whats on the Ground” literally has no authority

Think you might be in the wrong project.

Sheesh, learn how OSM works before mouthing off.

There are tags you can use for recording the official classification of a road. designation= is one of them. highway= is not.

The sheer effrontery of steamrollering in and changing an entire state’s highway tagging, because you somehow know better than every single mapper who has gone before in the 19 years of OSM, is really quite something.

That’s so good.

But no, I will not release my edits under a “Public Domain” license.

Tell me, what are these edits of which you speak?

Certainly lots of opportunities here. I’ve been intermittently working on an app (iPhone only so far) that has a couple of experimental features based on surveying and recording quality and overall impressions of rights of way. It’s in the App Store as Path Surveyor though given that your username ends in “_debian” I’m guessing you probably don’t have an iOS device ;). I’d like to do an Android version though that probably needs a bit more funding for development.

wandrer.earth is a really popular site for the whole “completist” idea though it’s more popular with cyclists than walkers, I think.

Wow, that’s horrible! (the billboards, not the tagging)

Similar issues with them in Manchester, UK: https://www.theguardian.com/uk-news/2022/jan/09/electronic-advertising-boards-manchester-energy-use-consumption

That sounds like an issue in the app, not an OSM data problem. If you write a routing app (like I have!) then you have to ‘look ahead’ for turns and announce them well in advance. If Organic Maps is not announcing them far enough in advance, that’s its problem, surely?

Thanks for your enthusiasm but please, please, please don’t start on something so complex as disputed country boundaries in your first week as an OSM mapper!

At this point there’s zero reason the style doesn’t render vector tiles except for pure complacency and laziness.

Awesome. Look forward to your patch @Adamant1 given that it’s so easy.