Oh, I just noticed that the legend pops up as a dialog at the very start, my bad!

I think years of training of clicking through cookie banners, “subscribe our newsletter” and “login with Google” dialogs finally paid off that I don’t even perceive startup dialogs anymore 😆

Saw this through weeklyOSM. It looks really good and really useful! I also thought about including a similar thing in StreetComplete, in the overlays, but didn’t find a good solution for the use case that ideally one wants to see color-coded both the age and what it is currently tagged with (to find mistakes in the first place). In the end, I filed this idea in #4735 with the prevailing idea to just have slider setting that allows coloring as red if the information is older than X.

Maybe the code could be generalized so that one could easily do the same for other properties?

I don’t know if it is, but the color palette also looks like it would be (red-green) color blind-proof. Regarding the color palette, I am missing a legend that is telling me which color signifies what.

Red is probably “it’s missing”. Did you take into account that oftentimes when source:maxspeed (or any of its siblings like maxspeed:type) is specified, often maxspeed is deliberately missing because it is an implicit speed limit (without signs)? If you don’t know it yet, you could also check out my talk Inferring Default Speed Limits from the State of the Map 2022. There’s also maxspeed:forward, backward etc., but that tag is kind of rare.

Also, what if maxspeed was tagged 10 years ago and the tag never changed, but check_date:maxspeed (or any of its sibling tags that are synonymous) specifies a newer date? Do you take this into account? It isn’t used a whole lot yet, but IMO it would be a good idea to use it more.

Sorry about that spam from the account sc_googleplay. It looks like a tester from Google Play used that account to explore what else he could do in the StreetComplete login screen apart from the OAuth login in the app. As a precaution, I changed the users’ password anyway. (Google Play requires that a test account is provided for them for apps that do not have 100% of the content available when not logged in, so they have to have a real OSM account.)

( https://github.com/streetcomplete/StreetComplete/commit/f6f358d7bf7b55f8163c97392c7cb7445ae7cc96 )

Now, StreetComplete users will get up to date suggestions in the atm operator, clothes container operator and charging station operator quests again :-)

Cool, thank you! For my use case, I don’t necessarily need the centroid, I could also just take the first point of a linestring etc.

By the way, is it a bug that if I export this query https://qlever.cs.uni-freiburg.de/osm-planet/bEcHTr to CSV, I get this:

name,type,geometry
Paris Gare du Nord,https://www.openstreetmap.org/node,POINT(2.3549733 48.8804003)

while if I export it to TSV, I get this:

?name	?type	?geometry
"Paris Gare du Nord"	<https://www.openstreetmap.org/node>	"POINT(2.3549733 48.8804003)"^^<http://www.opengis.net/ont/geosparql#wktLiteral>

(Note the different format of the header and also the “^^http://www.opengis.net/ont/geosparql#wktLiteral” at the end)