Just for the record: https://github.com/simonpoole/pmtiles-reader and https://github.com/MarcusWolschon/osmeditor4android/pull/2391

PS: IMHO both google and MS building outlines should be considered off limits.

My post/toot on the fund raising drive got 2 retweets on TSNFKAT, but 981 (and increasing) boosts on Mastodon, even though I have roughly 30% more followers on TSNFKAT.

I can only comment on 2) and following.

Nobody had or has any problem with your question with respect to the usage of AWS.

However you can’t reasonably expect everybody to drop what they are doing to get you an immediate detailed answer, for, a in the larger scheme of things, small line item in the budget. Nor should you expect to find every detail documented in advance.

It was clearly pointed out to you that the person responsible on the technical side of things was on vacation and wouldn’t be available before today, but you didn’t pause your barrage of requests even just for two days.

Instead of blaming everybody else for your totally over the top reaction to the push back you deservedly received, maybe you should calm down and reflect a bit.

Ich finde in der PC-Version nicht die Möglichkeit,

In der PC-Version von was?

Naturally a 7 years old project will have lots of limitations compared with something recently created, that wasn’t the point.

See http://lists.openstreetmap.ch/archives/list/talk-ch@openstreetmap.ch/thread/UWA3J7GEVDO6WEX4XHL65AFXNP5MS5J2/

This isn’t really a new idea, we (HSR/SOSM) ran a Maproulette challenge generated from AI identified pedestrian crossings back in November of 2016.

@JJIglesias the retention rate has always been low to very low (with some small differences), and youthmappers are no different than other similar sources. The relevant number of concern (new mapper influx) isn’t affected by this in any case, any effect on “large mapper” growth will be longer term, if there is any at all.

I think you might have been overthinking the mobile editor aspect a bit. I can only speak for Vespucci, but the fast thing to do is to add address nodes where the door is on the building outline, the app will automatically add an entrance tag.

Typically given a half regular numbering scheme you will not have to type anything as the number will be predicted. If you need to fix up building outlines later on, having the entrance node already doesn’t really get in the way.

Das osm_ids Objekt ist optional, man kann aktuell aber keine solchen Todos ohne Objektbezug in Vespucci erstellen (normale Notes gehen natürlich auch), aber das Laden (und Abspeichern) geht.

Speichert man eine halb abgearbeitete Todoliste ab, dann sollten die abgearbeiteten Einträge “state”=”CLOSED” haben. Workflow: das Problem ist natürlich, dass es am besten wäre wenn man existierende OSM-Objekte referenziert, das geht im Augenblick nicht mit Features in GeoJSON (da es dort keine id geben muss die man als Referenz verwenden kann.

Muss ich mir mal überlegen ob man was in der Art unterstützen könnte.

Noch als Nachtrag das Dateiformat http://vespucci.io/tutorials/todos/

Zuerst einmal: http://vespucci.io/help/en/19.0.0%20Release%20notes/#support-for-external-measurement-apps

Zum Workflow: wenn ich richtig verstehe generierst du über mehrere Schritte hinweg modifizierte OSM Daten die du dann in Vespucci lädst und vor Ort anpasst. Das scheint mir etwas umständlich, ich hätte eher aus den Geoportal Daten Geojson generiert mit den gewünschten Attributen und die Geojson Schicht dann direkt in Vespucci gebraucht um entweder die Tags upzudaten, oder neue Objekte zu erstellen. Das braucht maximal 2-3 Klicks pro Objekt.

Alternativ oder zusätzlich, kannst du auch einfach eine Todo Liste erstellen, siehe http://vespucci.io/help/en/18.0.0%20Release%20notes/#improved-osmose-and-todo-support Das Format könnte vermutlich auch von deinem Skript erstellt werden, wenn du Interesse hast, bitte melden.

The long tail of values in essentially any “numeric” tag in OSM will contain malformed data that has to be dealt with. How exactly could range from trying to parse them to extract some useful information, to simply ignoring them. What you can’t do is simply assume they will contain well formatted numbers.

We had a discussion back in October in the Swiss community with respect to best practices of mapping individual chargers vs. the area of larger charging facilities. (and tagging the area). See http://lists.openstreetmap.ch/pipermail/talk-ch/2022-October/011686.html It would be nice if we could get general agreement on how to handle detailed vs. rough mapping without losing information.

Some of the issues you have seen in numeric values are “normal” and not specific to charging station tagging, any use will have to normalize these.

PS: I need to remember that we need a plug-in value for authentication, while this is only common right now for Teslas it is likely to become much more common.

Apologies, but from reading the post it isn’t clear if this is official product marketing, aka you announcing this as an Meta employee (or employee of an other related organisation), or something else. I believe a clarification would be in order.

@tg4567 and @jonsger this is already covered in the blog post.

@DeBigC sounds kind of normal and roughly in line with the influx of new mappers we see here osm.org/user/SimonPoole/diary/397810

One time editors have always been common as long as I’ve been involved in OSM and “larger mappers” that is contributors that have turned mapping in to their hobby are rare and I wouldn’t really expect that to change.

The dynamics are naturally going to be different in developing countries.

@pnorman thanks for the numbers, I think they at least indicate that there was something going on with the HOT numbers.

Naturally contributions tend to lag conversion/signup by a fair bit, but on the other hand if we assume that most HOT signups happen immediately at events at which the signups start mapping, those numbers would actually align with the periods we are looking at.

@stevea the point was not that residential areas can’t have names, the question was about using the brand of a development company to nmae them.

From a world wide point of view there may be legal issues.

Guess what mvexels audience here is.