piebro/osm-data huggingface dataset:
SK53 (2022-01-30 10:24:45+00:00): You tagged this https://www.openstreetmap.org/node/8946964369 as having output of 3KW which given size of the panel looks rather low (I'd have expected 6-7 kW). Was this based on other knowledge, or is the 3kW an assumption?
DaveArq (2022-01-31 08:22:32+00:00): Hi, this is checked with the owner
SK53 (2022-01-31 10:37:44+00:00): Interesting. For reference, this (https://www.openstreetmap.org/node/6368780677) panel's output is available on the web https://shkspr.mobi/blog/2014/12/a-year-of-solar-panels-open-data/ and has 12 vs 22 panels.

Unfortunately Terence Eden moved 2 years ago & I dont know his new address so cant correlate number of panels, output & an OSM element :-).

Jerry
Patchanka (2021-07-24 18:44:46+00:00): oups, description entière : suppression des name qui ne sont pas des vrais noms sur les containers de recyclage du SITCOM - Côte sud des Landes, discuté avec @Vinber-Pro et @David Pédehourcq ayant réalisé l'import initial
ottwiz (2021-07-31 14:11:02+00:00): The telephone number is always in the following form (ITU form):  +1 304 xxx xxxx

Just as a tip. https://wiki.openstreetmap.org/wiki/Key:phone
ottwiz (2021-07-31 14:12:25+00:00): Also, you don't need to write 25 to multiple buildings, it's enough to put it on the main building. Because this is redundancy what you did, but hey, feel free to ask any questions! :) I'm happy to answer them
vulasala (2021-07-26 03:09:37+00:00): Hi Kri_ttt,
Trust your are doing well. I have modified the classification of way 967065423 from unclassified to service as there is a classification gap.
Thanks.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/108542949
evod (2022-05-15 12:14:34+00:00): kommt da wirklich noch eine abfahrt? die baustelle ist schon fertig soweit ich das vor ort sehe.
emergency99 (2022-05-15 20:58:05+00:00): Wenn nun keine weitere Bauaktivität ist, dann stufen wir es halt wieder auf proposed runter. Sah damals so aus als würden sie es bauen.
letihu (2021-10-18 18:58:32+00:00): Warum wird bei den Gräben nicht einfach die Breite eingetragen?
https://www.openstreetmap.org/way/967067512/history
Die Datenbank wird nicht besser durch solche Stellen wie diese.
https://www.openstreetmap.org/way/304584702/history
Die Wasserfläche ist neben dem Graben und über die Straße gemappt.
letihu (2021-10-18 19:11:03+00:00): Hier
https://www.openstreetmap.org/node/8947032354/history
sieht dass auch ganz schlimm aus :-(
VictorIE (2023-04-23 15:05:24+00:00): Hi,

Is access=no correct? https://www.openstreetmap.org/way/510292007
b-unicycling (2023-04-24 10:12:35+00:00): it's not, well spotted
BCNorwich (2021-07-27 07:06:05+00:00): Hi, Your changes included deleting parts of several areas resulting in many instances of self-intersection. I've reverted all the ones that I can see, thus reinstating the original outlines.

I see you completely deleted 14 other ways. I now wonder if these have also disrupted original areas. Could you please have a look at your deletions to see if amendments are needed?

Regards Bernard.
StephaneP (2021-07-26 09:52:13+00:00): Bonjour Trepliev,
Dans ce changeset, tu avais ajouté le tag "forêt" sur une zone bien plus grande que ce que je pense que tu voulais faire : https://www.openstreetmap.org/relation/10838148

Je viens de corriger.

Bonne journée !
Stf
Trepliev (2021-07-26 11:13:52+00:00): Merci, c'était une fausse manip !
Je ferai plus attention la prochaine fois.
Bonne journée,
StephaneP (2021-07-26 12:12:40+00:00): Pas de problème, et au fait : Bienvenue parmi les contributeurs !
Lee Carré (2021-07-27 12:12:55+00:00): I very much doubt that you crossed half of Europe within 30 minutes. This isn't your only changeset like this, either.

StreetComplete is for on-the-ground surveying; actually being there and seeing for yourself (hence source=survey, and the warning dialogue SC gives when your detected location isn't near the element you're changing).

If you're making changes from memory, then use a different editor and set the value for the source tag to be something like “local knowledge”.
Blauwdruk (2021-07-31 16:20:55+00:00): Thanks Lee for your comment.
Because the 'Gooikensdam' change was at where I work too, I was sure to be able to solve the things I did. Other questions I left.
But to not interfere the way StreetComplete works I will from now on only answer the questions from place where I am. 

Best wishes!
Lee Carré (2021-09-19 17:28:20+00:00): Apologies, I've only just noticed your reply.

Thankyou for your response. That sounds sensible.

Though, just as an FYI, I read, recently, in one of SC's issues on GitHub, that there's concern over SC being used for non-surveying changes, and an idea was suggested to set survey=local knowledge when the user isn't actually on-site. Though, I dunno if this is actually being implemented in more recent versions (than the one you used).

So, it might become a non-problem in future. For now, though, SC should be used only for survey work, like you said. 🙂

In order to keep your changeset areas small, it'd be better to upload your workplace changes (quest answers) separately from those at home. This will result in separate changesets, which should be localised, rather than spanning a wide area.

In SC either connect to the office 802.11 (‘Wi-Fi’) for it to auto-upload, else tap the upload widget on the main (quest-map) UI to trigger a manual upload. Then changes at home will be separate.

Your mode of usage seems to be that auto-upload is set to perma-on. This works differently. Instead of closing the changeset(s) (SC uses one per quest-type, per batch of answers) immediately after uploading changes, it keeps the changeset(s) (one per quest-type) open. By default, OSM allows them to remain open for 2 hours since the last uploaded change.

So, either change SC's upload mode, or wait until the existing changesets have all auto-closed before uploading answers to quests in a different region.

Though, this behaviour inspires me to open an issue for SC so that it avoids country-spanning changesets. That it, it closes the existing set if the new change is more than N km away from the last.

However, this relates back to SC being intended for surveying, and making assumptions to that effect. It would ordinarily be unlikely that someone would cross such a great distance in the 2 hour window of the same changeset remaining open.

But, edge cares exist. Especially if SC is going to allow non-survey changes at some point in future.
Lee Carré (2021-09-19 17:34:21+00:00): Having briefly checked your recent changesets, whatever configuration / usage changes you've made have had the desired effect; very small changeset areas.

Excellent 🙂👍. Continue, good sir.

Thankyou for your contributions. (And for reducing the noise (of irrelevant changesets) in my local list.)
t_ja (2021-07-26 17:35:56+00:00): Podla komentara usudzujem, ze tie drevene hranoly v podlahe sa asi nemenili od roku 2013, kedy som tam bol naposledy a uz vtedy som rozmyslal, ci to vobec zakreslovat. Ak si dobre pamatam, bola tam vtedy cedula "vstup na vlastne riziko", ale prejst sa to dalo (s trochou odvahy).

Fotecka aktualneho stavu by nebola? Zavesil by som ju do galerie na freemap.sk.
tanonin (2021-07-30 18:18:51+00:00): Tu t'est chauffé 👍
user_1566574 (2021-07-30 18:29:16+00:00): Cherches pas la bagarre ou j'ajoute tous les lampadaires côté Saint-Point-Lac

(Merci ! 😂🤜🤛 Il est gentillet celui-ci comparé à d'autres changesets)
tanonin (2021-07-30 20:07:19+00:00): J'ai fait du mieux que je peux uniquement sur chaon pour le moment
Je peut te filer des images mais c'est clairement pas moi qui vais ajouter les bouts de bois verticaux 😂
Au fait tu n'aurais pas touché une zone de construction vue du Lac, Chaon?
user_1566574 (2021-07-30 20:15:44+00:00): Oula non mais pas de soucis ! Si on devait commencer à se tirer dans les pattes car on a pas fait telle ou telle zone, tu serais le premier à m'incendier...

Rah, tu sais pas ce que tu perds hein. Ça rend vachement bien sur http://osmstreetlight.bplaced.net/ 🤭

Celle-ci ? https://www.openstreetmap.org/way/961669152
Pas depuis que tu y a touché non. J'en ai créé d'autres, mais c'est tout.
E de Wit (2021-07-25 11:17:56+00:00): Hi pe1aqp,

Review requested, so here goes:
The bird hide isn't a building, only a wall with horizontal slits in it. (based on recent oblique imegary)
Redundant tags, no need to define 0% incline.
highways shouldn't stick to the surrounding landuses.

I've added a couple of extra things, like a bridge, a wicket_gate, some fences and put the misaligned leisure=bird_hide in the right place.

Changeset:
https://www.openstreetmap.org/changeset/108560701

-E de Wit
pe1aqp (2021-07-25 14:04:06+00:00): Thanks for your corrections and additions.  I wasn't sure about the "building" classification, it does have a cellar.
E de Wit (2021-07-25 20:38:53+00:00): I noticed the 'cellar' door (south-east), it has water running towards the door.
Perhaps a resevoir of some kind?
pe1aqp (2021-07-25 21:05:29+00:00): It is a bat-cellar, similar to: https://www.vleermuizenindepolder.nl/vleermuiskelders.html
maro21 (2021-07-25 19:32:18+00:00): Czy kasy na dworcu nie są już dostosowane dla niepełnosprawnych? Coś się zmieniło?
eggie (2025-06-20 06:20:09+00:00): Dag phypere.. bicycle=use_sidepath ligt hier overal onterecht. Het zijn Niet verplichte fietspaden. NL:G13
MVG
eggie
eggie (2025-06-20 06:43:24+00:00): Ik heb use_sidepath verwijderd. Het routeert weer.
MVG
eggie
user_2066394 (2021-07-24 22:45:30+00:00): https://www.openstreetmap.org/way/29053418
Hier hat es was verzogen.
martinst (2021-07-28 09:34:43+00:00): Hallo Norbert,
Du hast die Tags "highway" und "tracktype" bei diesen Objekten hinzugefügt:
https://www.openstreetmap.org/way/692055810
https://www.openstreetmap.org/way/762920786
Diese Eintragung macht bei Gebäuden und Bächen keinen Sinn und ist falsch. 
Bei Unklarheiten bitte im OSM-Wiki nachsehen, dort ist dokumentiert welche Tags wo verwendet werden sollen.
Könntest Du bitte diese (und evtl. weitere derartige) Eintragungen von dir rückgängig machen?
Gruß Martin
osm915 (2021-07-30 19:36:04+00:00): Hallo Norbert
mir ist auch gerade aufgefallen, dass es mit diesem Changeset wahrscheinlich ein copy und paste Problem gab.
Die keys highway=track und tracktype=grade3 wurden bei den verschiedensten "way-Typen" ergänzt.
Neben den bereits genannten Bächen und Gebäuden betrifft es beispielsweise auch
landuse residential: https://osm.org/way/37000278
highway residential: https://osm.org/way/24560130
railway rail: https://osm.org/way/37001981

Mit https://overpass-api.de/achavi/?changeset=108547349 kannst du dir einen Überblick verschaffen.
Kannst du das bald korrigieren oder soll ich mich darum kümmern?
Freundliche Grüße!
osm915 (2021-08-12 13:32:23+00:00): Hallo Norbert
danke, dass du ein paar Objekte korrigiert hast.
Ich habe ich mich vorgestern noch um weitere gekümmert, die ich ohne aktuelle Vorort-Kontrolle korrigieren konnte:
highway: https://osm.org/changeset/109486350
landuse: https://osm.org/changeset/109486430
building: https://osm.org/changeset/109486504
railway: https://osm.org/changeset/109486457
und noch ein paar Kleinigkeiten (CS#109486599 und 109486725).

highways die bereits vor der (track+tracktype) "Anpassung" als path oder track getaggt waren habe ich nicht korrigiert. Das müsste sich ggf. mal jemand vor Ort ansehen.
Freundliche Grüße!
CRCulver (2021-12-17 09:04:15+00:00): You added tags relating to Dečani Monastery to the way representing the main church within the monastery. These should go on the monastery way which is traced around the entire complex.
Arlo James Barnes (2021-07-24 21:54:29+00:00): Oh no, munged the name of the hotel when merging duplicate area and point...will fix later if someone else doesn't first, have to run right now though.
Mateusz Konieczny (2024-03-16 06:54:50+00:00): Hello! https://www.openstreetmap.org/way/759933624/history has construction = construction that was added in this edit (if I checked things correctly)
What construction=construction means? What you wanted to express by using this tag?
wielandb (2021-07-24 22:06:42+00:00): Nur der Vollständigkeit halber: Source ist arial imagery, nicht survey. Hab mich dank der Macht der Gewohnheit verklickt. :(
impiaaa (2021-07-25 06:05:04+00:00): This changeset reuses nodes from the surrounding road to create a building. Please do not reuse objects for unrelated features.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/108547997
SomeoneElse (2021-07-25 12:36:29+00:00): Hello,
Yes, it will cause confusion when people look at https://www.openstreetmap.org/node/105038338/history and find that that had TIGER import tags on it (because it was part of a road)  but it is now part of a building.
Why are you re-using nodes like this?
Best Regards,
Andy
sander79 (2021-07-26 08:24:37+00:00): de waarde van opening_hours is niet geldig. (zie wiki). Maak er anders een aparte note van
syntex (2021-07-26 16:02:03+00:00): Ale rysuj przynajmniej na podstawie warstwy EGIB. Takie kształty są kiepskie : /
Martin Constantino–Bodin (2021-07-25 16:34:57+00:00): Bonjour ☺
Il y a des changements en Normandie en plus de la Corse dans ce groupe de modifications : https://www.openstreetmap.org/way/209731051 Il s’agit peut-être d’une erreur : pouvez-vous vérifier que c’est bon ? Merci d’avance ! ☺
Laurent CHOISIE (2021-07-25 22:45:24+00:00): Bonsoir, non pas de souci. C’est « normal ». Effectivement, d’habitude je fais des petits changeset pour éviter ce genre de choses. Mais j’ai bien dessiné en Corse (des chemins agricoles principalement) et rectifier qques routes (d’accès principalement) en Normandie. Merci par avance de valider ces modifications ! Cordialement
Martin Constantino–Bodin (2021-07-26 10:12:37+00:00): Super ! Merci et bonne journée ☺
ottwiz (2021-07-31 13:29:18+00:00): Hey! it's so cool to see more WV mappers on OSM. You see that the entire Ohio County is in need of fixing stuff. If you got any questions, feel free to comment below this, or send me a message by clicking on my name, and "Send message"

But also we got a discord community: https://discord.gg/openstreetmap

And an OSM US slack community where I set up the #local-west-virginia channel: https://slack.openstreetmap.us/, although I'm from Hungary but i have some internet friends from WV.
HubMiner (2021-11-25 01:45:41+00:00): https://www.openstreetmap.org/way/174246375/history

Hi, what is the definition of "school hours"?
Strubbl (2021-07-25 08:55:59+00:00): Hi meggs2000, wo kann man das B1-1_5-79-UELA_181025.pdf einsehen? Hast du einen Link für mich?
meggs2000 (2021-07-25 20:38:57+00:00): Hi, hier sind die gesamten Unterlagen für den Planungsabschnitt 79 zu finden
https://www.muenchen.de/rathaus/Stadtverwaltung/baureferat/planfeststellungsverfahren/u5_pa-77.html
Strubbl (2021-07-25 20:45:51+00:00): Vielen lieben Dank
tekim (2021-07-25 03:44:51+00:00): Pretty arrogant for you to post yet another changeset with a huge geographic extent after you have been informed via changeset comments on one of your other changesets that this is not appropriate.  Also, this appears to be a mechanical edit, which is also not appropriate.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/108548780
Friendly_Ghost (2021-07-25 08:33:55+00:00): Hello Tekim, 

No one seems to have a problem with the contents of my changesets so far, only with the method, which I think is ridiculous because it's one of the few ways to get this kind of thing done. 

I wouldn't call it a mechanical edit, because I reviewed all of the tag combinations before I changed them to avoid losing any information.

If you have suggestions to update deprecated and misspelled tags, I'm all ears. 

Best regards

Casper
MxxCon (2021-07-25 17:18:42+00:00): Just because people don't comment on your changesets doesn't mean they completely approve of you making giant multi-continent bounding boxes. I too would appreciate if you limited your edits to smaller geographic regions so that each changeset could be evaluated to make sure there are no problems. Now reviewing almost 3200 changes in one commit is unreasonable.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/108548780
Friendly_Ghost (2021-07-25 17:49:03+00:00): Then how would you prefer to review my 3200 changes: in 10, 100 or 1000 changesets? How many people would bother to review 1,000 very similar tiny changesets?

There is no sweet spot that will please everyone. There are just a whole lot of outdated and erroneous tags. I just fixed a lot of them to make OSM data more consistent and understandable for data users and analysts.
MxxCon (2021-07-25 17:57:03+00:00): By state or last by general geographic regions. Best case I'd prefer it split up by major populated areas. Because your changeset is so huge, I can't even tell where most of your changes are...
And due to the nature of OSM, your bounding box also included a bunch of other countries which don't care seeing changes from USA.
Friendly_Ghost (2021-07-25 18:33:23+00:00): Nobody wants to do the same edit separately for each state, and even then people would complain about state-wide edits that are only a few hundred changes. Changes like this just need to be done. 

Of course I wouldn't create tiny edits across the globe in a single changeset, but this one is large enough to warrant the large bbox.
tekim (2021-07-25 18:43:48+00:00): > Then how would you prefer to review my 3200 changes    
If you don't have enough respect for our community to follow our norms and invest the time, effort, and skill (or recruit others with the necessary time and skill to help you) to do things inline with community expectations and rules, then I would prefer that you do not make this type of change at all.  The fact that there are a few "color" vs "colour" tags is not a life and death situation for OpenStreetMap, and data consumers can easily translate if it is important to them.

BTW, regardless of what you call it, this does fall under the Automated Edits Code of Conduct[0], which states the code covers the "use of find-and-replace functionality using a standard editor such as JOSM "


[0]https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct
Friendly_Ghost (2021-07-25 19:13:29+00:00): Who are you to dictate norms to anyone? OSM does not know the concept of authority. We collaborate. I fixed your tags, you're welcome. 

"data consumers can easily translate" - or we can just produce good data in the first place, which is what I'm doing. 

Of course a few "color" vs "colour" tags is not a life and death situation. Neither is the fact that I'm taking my time to fix them. I prioritise good data over my bbox size and I suggest that you do the same.
Friendly_Ghost (2021-07-25 19:21:43+00:00): Furthermore, you didn't answer my question: how would you prefer to review my 3,200 changes?
tekim (2021-07-25 19:30:11+00:00): I would prefer to just review those in my metro area or county.
Friendly_Ghost (2021-07-25 19:35:28+00:00): In that case you can easily use achavi (https://overpass-api.de/achavi/?changeset=108548780) to zoom in to your area and review each specific object separately. 

It's simply not feasible to split up thematic map changes per county, unless you know of a JOSM tool that can perform that kind of action.
snoozingnewt (2021-07-25 20:30:18+00:00): I don't think this argument matters at all. Does it actually harm the map? No. Does it inconvenience you in any way? Not with the right tools. Personally, I'm completely fine with these edits.

And by the way tekim, the wiki states 
"use of find-and-replace functionality using a standard editor such as JOSM or finding using services such as Overpass API and changing without reviewing cases individually". The edits seem to have all been reviewed already by Casper, so it shouldn't be a problem.
tekim (2021-07-25 20:39:32+00:00): If every data element (way, node, relation) was individually reviewed, then it is not a mechanical edit, but based on what Casper has said, that is not what happened here (for example, there was no mention of loading all elements about to be changed into something like the todo list and looking at each one individually).
Friendly_Ghost (2021-07-25 20:49:58+00:00): You mean you want me to look at all 3,2k buildings individually and replace the same tags over and over again? The ctrl+F tool was invented and implemented specifically for this kind of usage.
MxxCon (2021-07-25 21:06:51+00:00): >Does it actually harm the map? No.
@snoozingnewt, but the issue at hand. Do you know for sure that every single one of these 3200 changes is correct for the situation it's in? That's why people monitor the map to spot any potential issues, intentional or not. It's very difficult to review a single changeset with 3200 changes.

> Does it inconvenience you in any way? Not with the right tools.

It does if you try to ensure that edits that go into OSM are of high quality. As an example, that archavi link posted earlier errors out with "osmDiff:  runtime error: Query timed out in "query" at line 1 after 181 seconds."
Most tools are not designed to wrangle such huge changesets.
Friendly_Ghost (2021-07-25 21:20:42+00:00): > It's very difficult to review a single changeset with 3200 changes.

It's even more difficult to review 3,2k changesets with 1 change each. Choices have to be made and seeing that no one had taken up the job of updating these tags, I made this choice. There is no single solution that pleases everyone, but changes like this still need to be made. 

If you can find or make a tool that splits up changes by geographic area, I'll happily use it, and I think several other mappers would also be very happy with it. 

> that archavi link posted earlier errors out

That's a complaint to send to achavi rather than to me. Many changesets are larger than this one, imports for example.
snoozingnewt (2021-07-25 21:24:53+00:00): @MxxCon it would obviously time out with the entire changeset, but there's an option to make the bounding box smaller. If you're only reviewing one area, it shouldn't be a problem.
Ex: https://media.discordapp.net/attachments/802176475230371864/868966985076187196/unknown.png
Zaneo (2021-07-26 02:07:15+00:00): Specifically addressing this point:

>Just because people don't comment on your changesets doesn't mean they completely approve of you making giant multi-continent bounding boxes.

If people don't raise issues they have, then they can't be upset when those issues aren't considered.

About large bounding boxes. Taking the max and min lat/long of changes and drawing a box is not the greatest way to highlight area affected. Using a rotated rect could show very differently results for a long thin diagonal edit.

Or within the changeset box, highlighting some areas where change was actually affected.

My opinion about large bounding box issues is that they are a problem of the tools, not the act. Review tools that don't properly highlight the changes are causing mappers to get freaked out.
skquinn (2021-07-26 03:08:44+00:00): The standard in the US seems to be one changeset per state in most cases. In Texas I try to keep them smaller when feasible as Texas is huge.

I agree that the bounding box system isn't perfect but it's what we've got.
Zaneo (2021-07-26 03:35:10+00:00): Are there any reliable tools for determining which "state" a node belongs too? (On a global level).

Or is it something like:
Query all the administrative boundaries. Find out what level is state in each country. Find if the node is enclosed in the polygon of the administrative boundary?