Actually, not that bad! :-) Cosmic has a certain ring to it.

The tendency of OSM developers to use OSM in the names of their app is strong I guess.

The internal/developer name for Vespucci is osmeditor4android. And the initial name for StreetComplete was osmagent (like, you are an agent that collects data for OSM).

So what was the intial name(s) for Go Map!! ?

Based on the links posted by Supaplex030, work has started in StreetComplete to implement a UI for recording the smoothness information. Feel free to contribute. We are still looking for clear and representative pictures for different smoothness levels of asphalt surfaces, of sett surfaces, of paving stones surfaces and more, see

https://github.com/streetcomplete/StreetComplete/pull/3257

I come to a different conclusion. The increased activity coincides with certain releases of SC that made mapping either more engaging or more efficient. See this chart:

Well I’d say most of the funding should also go to the one that maintains and extends it afterwards (and that won’t be me, it’s too much for one person).

As written in that ticket, it would take very roughly half a year for two people to port the app to iOS.

Some statistics here: https://github.com/streetcomplete/StreetComplete/discussions/2671

Difficult to look at that isolated. A lot of other things changed in the last year which pushed efficiency and user count of the app.

User count roughly doubled in the last year, while the number of contributions roughly quadrupled.

(That was meant to be a list: 1. Funding, 2. maintainer, apparently kramdown doesn’t work)

See https://github.com/streetcomplete/StreetComplete/issues/1892

Basically, it is possible but is a very large untertaking. What is missing is * Funding * Someone willing to maintain/extend the port afterwards

Cool, very interesting analysis!

Yeah, OpenStreetMap is very much more carried by few users (“power mappers”) with a lot of contributions than many users with each only a few contributions. This fact is not so obvious when looking at the map per se, because most of what can be seen on the map itself is traced from home, i.e. it doesn’t matter where exactly the user resides but it becomes obvious when looking at where edits are made that require the user to be on-site.

StreetComplete set out to lower the barrier for initial contribution in order to unskew that statistic a bit, but of course, there is only so much impact one app can have.

People who get the app for example but are not registered on OSM yet, for example, need to overcome the hurdle to register an account at OSM first before they can really contribute. The registration is unnecessarily tedious, especially on mobile, so a lot of users jump off before even making their first uploaded edit.

International roughness index (IRI)

Ich bin durch Zufall noch einmal auf dieses Thema gestoßen. IRI ist ein internationaler Standard für Messung der Straßen-Unebenheit.

Gemessen wird er offenbar vor allem mit speziell ausgestatteten Autos bei denen Sensoren an der Hinterradachse befestigt sind. Allerdings wird im Wikipedia-Artikel auch erwähnt, dass man grundsätzlich auch andere Methoden verwenden kann, z.B. Messen der Erschütterung (genannt RTRRMS - Response-Type Road Roughness Measuring Systems), also letztlich deine Methode.

Diese müssten dann natürlich entsprechend kalibriert werden, damit sie möglichst die gleichen Werte ausgeben wie ein entsprechend ausgestattetes Auto. Mindestens dazu notwendig wäre, an IRI-Daten zu kommen wo man selbst quasi mit deiner App und eigenem Fahrrad hinkommt um es abzugleichen. Aber wenn man diese Daten hätte, könnte man (z.B. in der Wiki, oder auf GitHub) ein entsprechendes Verzeichnis von Kalibrationen erstellen. Wenn man diese Kalibration dann jeweils anwendet, könnte man erreichen, mehr oder weniger genau, dass deine App ICI-Daten ausspuckt. Das wäre doch ziemlich krass oder?

Hier noch ein Artikel generell zu Methoden die Oberflächenunebenheit zu messen: https://pavementinteractive.org/reference-desk/pavement-management/pavement-evaluation/roughness/

I love how the tool takes into account area:highway. So this makes this officially the first renderer that heeds this tag!

What would be a realistic scenarios for a “takeover”, what would it consist of?

Is it possible to change the license to something like “Yeah no, contributors do not retain their copyright, copyright goes to OSMF and actually, we are changing our license to XYZ, nyah nyah!”?

Oh, when looking at the graph, I thought that the blue line was fitted so DE would be the reference point (=neither over nor underrepresented).

Anyway, thanks for the analysis!

Sehr schön, weitermachen ;-)

sheesh, the list formatting doesn’t really work, does it? :-/

How does the app decide what is left and what is right? From current view direction (compass)? If yes, this means that the map also rotates with the compass? This might turn out to be a bit jittery.

I have a few suggestions on the interface: * When pressing < or >, does the keypad come up on fullscreen immediately? If yes, I’d suggest to have only a minimal interface with +/- buttons first (it looks like this is the case in your first screenshot) * If the +/- are to increase/decrease the housenumber that is currently being added: the +/- could show in place of the < and > buttons because those should have no function while in the process of adding a new housenumber

On the name: * Address Pad * IpswichPad * Left And Right * 3LR (look left, look right) * LRPad * Address Mapper * or if KeyPad Mapper is not taken anymore…

This diary entry has been mentioned in the weeklyOSM 547. I for one did not know about the extrude tool, thanks for that!

A few notes: - addr:street can also be set with StreetComplete. Though of course, if you are certain which street a building belongs to, it is definitely more efficient with JOSM - There is an idea to add an even more efficient way to contribute/check housenumbers with StreetComplete: https://github.com/streetcomplete/StreetComplete/issues/2461 , a mockup

Hey arnalielsewhere, I’ve read your article a couple of days ago and came across this discussion on hackernews just now which you and anyone else interested in pedestrian routing might find interesting: Show HN: Find the safest well lit walking route between two locations.

Of course, OpenStreetMap is mentioned quite a bit in that discussion cause it is natural to try to source this information (whether a path is safe or not) at least partly from open data. What I find most interesting in this ongoing discussion is that many other factors that may effect pedestrian safety are mentioned that could be taken into account, some of which may be candidates to be tagged in OpenStreetMap.

This thing went totally past me, I just skimmed through it now because it was mentioned on weeklyOSM. As an outsider who didn’t take part in any discussion concerning this, I’d just like to say that I am glad that Heather Leson is not in a position of power at the OSMF any more.

I don’t trust people in positions of power who talk about power all the time and pull off these kind of power-plays.

Whenever I read something on OSM Weekly about what Heather Leson has written in the past few years, and I read up about it, I came away with the impression that this is pure politics, (ironically) quite hateful and made to damage the OSMF and OSM community in general. And to what end. And the latest example would be this “open letter”. Any normal person would have just called out that crude comparison in that emotional post of yours as a reply to that post, like Rory did, or contacted the list’s moderators about it. Instead, manufacture a public scandal in order to cancel an (apparent) adversary? Wow.