piebro/osm-data huggingface dataset:
mgerken (2023-03-26 15:00:59+00:00): Hm, ja, da hast du Recht, dass das nicht so eindeutig ist, welche Schreibweise hier zu nehmen ist. Ich weiß auch nicht, was ich als Anwohner als Schreibweise bei meiner Adresse angeben würde, da es ja wahrscheinlich im Ausweis dann anders steht als auf dem Straßenschild. Wenn ich als Außenstehender eine Adresse bestimmen will bleibt mir ja nur das Schild, aus dem Standpunkt würde ich dann die Schreibweise auf dem Schild vorziehen.

Ich denke aber, ich werde da einmal vor Ort schauen was aktuell auf dem Schild steht und das dann der Stadt als Mängel melden. Mit viel Glück werden sie die Schilder dann tauschen. Bis zu einer Antwort der Stadt würde ich das so lassen wie es jetzt ist.

Das Routing-Problem wird sich aktuell wahrscheinlich noch nicht lösen, denn die Adressen auf den Häusern haben noch die alte Schreibweise. Das sollte auf jeden Fall konsistent sein. Der Parkplatz ist ja definitiv nicht so eingetragen wie er heißt und beschildert ist.
stefan_o (2023-03-26 15:10:22+00:00): Super, vielen Dank!
mgerken (2023-04-25 19:17:58+00:00): Die Stadt hat geantwortet: Die Straße heißt laut deren Unterlagen korrekt Anspacherstraße, wie es auch auf den Schildern steht. Ich habe es in https://www.openstreetmap.org/changeset/135357165 wieder zurückgeändert.

Ich denke, dass die abweichende Schreibweise im Wahlverzeichnis etc. komplett aus ALKIS übernommen wurde und dort falsch eingetragen wurde.
highflyer74 (2023-03-30 08:03:57+00:00): Vandalism reverted after community discussion.
highflyer74 (2023-03-30 07:59:10+00:00): Vandalism reverted after community discussion.
TrekClimbing (2023-03-25 22:34:40+00:00): also sourced from survey, LiDAR and StreetSide
Henry572 (2023-03-26 11:05:19+00:00): Hallo JanN-MR,
Willkommen bei OpenStreetMap!
Ich habe mir deine Änderung angeschaut und es sieht alles gut aus.
Gruß, Henry
Marek-M (2023-03-28 09:18:15+00:00): Hej, nazwy rodzajowej nie wpisujemy dla sklepów - np. tutaj: https://www.openstreetmap.org/node/10762205305 - wystarczy sam tag shop=alcohol a name='Sklep monopolowy' i jego angielska pisownia jest całkowicie zbędna.

Tutaj utworzyłeś tzw. atrakcję bez uszczegółowienia jej rodzaju: https://www.openstreetmap.org/node/10762205505 - domyślam się, że chodzi o tężnię solankową, która jest już na mapie. Zamiast tworzyć nic nie znaczący węzeł lepiej jest dodać dodatkowy tag do istniejącego obiektu: https://www.openstreetmap.org/node/9599876582 - dzięki temu wyszukujący atrakcji od razu mogą dowiedzieć się czego się spodziewać w tym miejscu. 

Poprawiłem te dwa miejsca: https://overpass-api.de/achavi/?changeset=134211142
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/134120641
user_5359 (2023-03-26 14:30:16+00:00): Hello! Please have a look on https://www.osm.org/way/1157289974 (one of sixteen objects). Is there any reason to use building=residences instead of building=residential?
NorthCrab_upload (2023-03-25 23:00:22+00:00): Zauważyłem, że Twoja zmiana zawiera adresy wymagające dodatkowej uwagi. Przygotowałem listę obiektów oraz dodatkowe informacje:

Nazwa ulicy nie istnieje w okolicy. Jeśli adres ma nazwę ulicy, upewnij się, że jest ona poprawna. Jeśli nie, usuń addr:street, a nazwę miejscowości przekaż w addr:place.
https://www.openstreetmap.org/node/10762196290

Dokumentacja adresów (po polsku):
https://wiki.openstreetmap.org/wiki/Pl:Key:addr:*

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
NorthCrab_upload (2023-03-25 23:00:21+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Adres jest niekompletny, brakuje informacji o nazwie ulicy.
https://www.openstreetmap.org/way/1157290501

Pozdrawiam! 🦀
NorthCrab_upload (2023-03-25 23:10:21+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Duplikat adresu w okolicy. Adres można oznaczyć na dwa sposoby: na obszarze (dokładniejsze) albo na punkcie. Aktualizując adres, należy się upewnić, czy w okolicy nie pozostały żadne duplikaty.
https://www.openstreetmap.org/node/10762193815
https://www.openstreetmap.org/way/1157291117

Dokumentacja adresów (po polsku):
https://wiki.openstreetmap.org/wiki/Pl:Key:addr:*

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
felipeeugenio (2023-03-26 23:05:19+00:00): Estimado, por favor ingresar al chat de la comunidad. Sus ediciones contravienen los acuerdos de la comunidad. Está borrado cosas que otros han hecho sin ninguna consulta, por favor ingresar para poder conversar. No proseguir con los cambios de clasificaciones ni borrados de caminos existentes. saludos
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/134120898
AndersAndersson (2023-03-25 23:32:59+00:00): Hej!
Vi ändrade visst på samma skogspolygon samtidigt.
Jag är klar, men du får gärna se över Lillsjön bredvid denna länkade sjö när du är klar så att den får rätt roll i den stora skogspolygonen.
https://www.openstreetmap.org/relation/7307207
johantiden (2023-03-26 14:05:10+00:00): Hej! Bra att du håller koll!

Jag märkte att mitt program fick "konflikt" i datat och tyckte set såg bra ut. Jag tycker det ser bra ut nu också!

Det är svårt med de här enormt stora skogspolygonerna, de har en tendens att gå sönder eftersom man inte kan överblicka hela lätt. Jag försöker dela upp dem så det blir mindre problem framöver

Jag kommer nog fortsätt med just https://www.openstreetmap.org/relation/7307206#map=12/60.9802/16.1087 ett tag till då det också finns en massa detaljwr i som saknas.
AndersAndersson (2023-03-26 14:22:52+00:00): Jag vaknade tidigt och fixade det som felade i morse. Så nu är den ok igen.
MxxCon (2023-03-29 19:46:05+00:00): Hello.
Does this sculpture have a name or some other information that can be added here?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/134121199
mikeocool (2023-03-29 20:22:47+00:00): As far as I can tell it does not, short kinda making something up like "82 Degraw Street Sculpture Garden". It's discussed here: https://www.brooklynpaper.com/columbia-street-waterfront-district-artwork/

It is very much visible from the street, though the actual grounds are not open to the public, so not sure if that warrants being mapped or not.
MxxCon (2023-03-29 20:39:42+00:00): Ah, so it's not a single statue but a whole area. It could be mapped as an art gallery instead.
mikeocool (2023-03-29 22:00:44+00:00): Good call -- updated.
adrianojbr (2023-04-11 01:14:09+00:00): Olá, raldite!

Muito boas suas contribuições. Se quiser complementá-las, há uma padronização que foi aprovada para o mapeamento de escolas no Brasil: https://wiki.openstreetmap.org/wiki/Pt:Tag:amenity%3Dschool#Mapeamento_brasileiro.

Abraço!
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/134121317
user_5359 (2023-03-26 16:11:16+00:00): Hello! Please notice the language is a postfix (note:de instead de:note). However, the type of a tree is described with the key genus. So it is better to use genus:de=Birch if you cannot think of the technical term genus=Betula.
redd (2023-04-01 12:20:13+00:00): thanks for fixing it! 

I will try to remember it!
user_5359 (2023-03-26 05:55:24+00:00): Welcome to OSM! Please write a meaningful comment what you have changed
Diacritic (2023-03-26 00:53:56+00:00): Hello,

The previous tagging appears to be correct. The electorate of Kew is a political boundary.

https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dpolitical

Dian
Marek-M (2023-03-28 09:10:44+00:00): Hej, czy w tym pubie można kupować alkohol tak jak w sklepie monopolowym, czy jest to tyko pub?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/134121794
Marek-M (2023-03-28 09:08:09+00:00): Cześć, chyba nie chodziło tu o sklep z oponami tylko o kompresor na stacji paliw. Zamiast shop=tyres powinien być tag amenity=compressed_air i raczej nie ma on nazwy. Nie wiem czy OrganicMaps ma na coś takiego szablon i stąd pewnie jest problem :). Poprawiłem to miejsce ale jeśli jestem w błędzie, to daj znać.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/134121845
scintlark (2023-03-26 19:33:23+00:00): Great work on adding buildings in Scotland, thank you! :)
whammo (2023-03-28 01:32:45+00:00): Hey Joseph, I'm confused why/how this stretch of Columbia Pike has reappeared (I removed it in changeset 133972535, maybe there was an edit conflict given how closely in time we edited). There is no trace of it on the ground currently, and when it's eventually rebuilt from scratch in the coming years, my understanding is it will head straight to the underpass of VA 27, rather than this junction with South Joyce. See https://highways.dot.gov/sites/fhwa.dot.gov/files/AD.JPG
Joseph R P (2023-03-28 02:41:51+00:00): That would be a mistake on my part. I've now roughly updated everything based on the future plans and what I could make out of the Maxar Imagery (with some of the ROW for the future road alignments visible).
MxxCon (2023-03-29 19:48:51+00:00): Hello.
Please group your edits into smaller geographic regions. There's no reason for the same changeset to contain edits from Wales and Tennessee.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/134121975
CapG57 (2023-03-29 21:07:35+00:00): Apologies. The Tennesse edit was a mistake.
Godonhorry (2023-03-26 06:04:43+00:00): turn left - keep to the left-hand lane. follow the road ahead - keep to the left-hand or middle lane. turn right - move to the right-hand lane in good time.
https://linensrange.co.uk/
Godonhorry (2023-03-26 06:04:53+00:00): turn left - keep to the left-hand lane. follow the road ahead - keep to the left-hand or middle lane. turn right - move to the right-hand lane in good time.
https://linensrange.co.uk/
wehoye (2024-01-23 19:02:06+00:00): The corrected road priorities aim to enhance traffic flow and safety, emphasizing efficient routes for smoother commuting. The implementation of these changes aligns with the vision to optimize transportation networks. For further details on the updated road plan, you can visit https://oldrollapk.com/.
yayore_lisa (2025-03-25 16:43:40+00:00): Highway classification categorizes roads based on their function, capacity, and accessibility, such as expressways, arterials, collectors, and local roads. It helps in planning, designing, and managing transportation networks efficiently. For a detailed explanation, visit https://wordslibrary.com/.
yayore_lisa (2025-03-25 16:44:55+00:00): Highway classification is the process of categorizing roads based on their function, capacity, and importance in the transportation network. It includes categories like expressways, arterial roads, collector roads, and local roads. Proper classification helps in planning, maintenance, and traffic management. For more details, visit https://stylish-name.in/.
yayore_lisa (2025-03-25 16:46:06+00:00): Highway classification is the process of categorizing roads based on their function, capacity, and design standards. It includes categories like expressways, arterial roads, collector roads, and local streets. Proper classification helps in planning and managing transportation systems efficiently. For more details, visit https://consultasaldomovilnet.com/.
alinarizwan (2025-04-22 12:24:35+00:00): Thanks for sharing this. It's good to see the road priorities being corrected properly
nimrakhan (2025-04-24 16:17:23+00:00): Thanks for sharing the updated road priorities. This will definitely help in better planning and navigation. Appreciate the effort
Zarqum (2025-04-25 13:01:01+00:00): Glad to hear the updates are helpful! Better planning makes a big difference—appreciate you taking the time to acknowledge it.
alinarizwan (2025-04-29 12:13:48+00:00): Thank you for bringing up the issue of road priorities. It's important to have clear guidelines for safety and efficiency. If there are any specific suggestions or areas you'd like help with, feel free to share, and I'd be happy to discuss them further
kajas28 (2025-05-15 12:23:16+00:00): A **changeset** is a collection of modifications made to a database or codebase, typically in version control systems. It helps track updates, rollbacks, or improvements over time. For example, a changeset can reflect updates in a university's fee details, like those seen at [UOS Fee Structure](https://feestructure.com.pk/uos-fee-structure/) for accurate financial planning.
nosagi (2025-07-10 05:25:00+00:00): Corrected road priorities refer to adjustments made in traffic flow rules, road signs, or infrastructure to improve safety, reduce congestion, or reflect new development patterns. For example, a previously minor road may be given priority if traffic patterns change due to urban growth. To understand and download related presentations or traffic management plans, you can visit https://slidessharedownloader.com/ — a helpful tool for downloading SlideShare presentations for offline reference.
nosagi (2025-07-10 05:28:25+00:00): Corrected road priorities are essential for ensuring smoother traffic flow, reducing accidents, and improving road safety. When road priorities are clearly marked and followed, it minimizes confusion among drivers and enhances overall transportation efficiency. For instance, just like how updates fix bugs in popular games such as Nulls Brawl, which you can download from https://indirapk.tr/nulls-brawl-apk-indir/, corrected road priorities act as an essential upgrade for real-world traffic systems—making navigation more predictable and reliable for everyone.
eggie (2023-04-04 08:48:22+00:00): Dag C Batenburg.. foot=no heb ik hier verwijderd.
MVG
eggie
JJIglesias (2023-03-26 15:57:25+00:00): Excelente adicion Gerhard, ojala tuvieramos lo mismo para cada Departamento. Siempre Tarija haciendo diferencias positivas.
Gracias y Feliz Mapeo
JJ
JJIglesias (2023-03-26 16:11:12+00:00): Solo un detalle, cuando pones smoothness=bad seria bueno q revisaras este Wiki al respecto:
https://wiki.openstreetmap.org/wiki/Key:smoothness
Saludos
athlus (2023-03-27 04:19:53+00:00): Solo aumente Ref sin leer lo demás. Tendré más cuidado la próxima.
JJIglesias (2023-03-27 08:26:38+00:00): Gracias
Spaghetti Monster🍝 (2023-03-29 10:27:46+00:00): Please don't delete valid features. https://wiki.openstreetmap.org/wiki/Keep_the_history
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/134123632
Lokai (2023-03-26 09:45:11+00:00): Hallo,

beobachte mal die Relation

https://www.openstreetmap.org/relation/2307580

dort könnte ein Fehler vorliegen. Welcher CS dan nun war habe ich nicht überblickt.

Gruß

L.
Kovoschiz (2023-03-26 12:10:38+00:00): Thanks. There is another good question, as `addr:housenumber=` is the number used with street or village. It's unclear what blocks should use. I have used `ref=` and `addr:unit=` together for now. 
(According to some definition `addr:unit=` can be used when "inside divides into different units or staircases, where certain apartments/flats/offices can only be reached through a specific unit", so it seems more applicable to subbuildings found in modern apartment towers, ie Tower 1A and 1B inside the same Tower 1 physically. Consequently, it looks usable for houses, as different buildings in a compound can be called "units" overseas.  Shop "unit" in a building may be better off using `addr:door=`.)
Kovoschiz (2023-03-26 12:18:39+00:00): Some have also discussed whether `addr:building=` should be used. Perhaps it can be used in subbuildings ie `addr:building=1` + `addr:unit=1A` to show Tower 1A and 1B belongs to the same buildings. In this case, they are the same for one house, so not especially needed yet.
Another question is whether "Tower" or "House" should be included. For `ref=`, numbers are enough for blocks, and "Tower" is usually coded as "T1". But to generate an address with `addr:unit=`, it is unclear how it should be.
WC392309 (2023-03-27 01:57:37+00:00): yeah good idea. There should have been a collector road that connected
Joseph R P (2023-03-27 03:17:57+00:00): Sometimes tertiary roads can lead to dead-ends if they're lengthy and have something of significance along it or at its terminus, but usually, short dead-end roads like these are better as residential or minor roads.
user_5359 (2023-03-27 11:04:45+00:00): Hello! Please have a look on http://overpass-turbo.eu/s/1sXo. Did you mean old_ref instead of old_red?
Yitzchak M (2023-04-04 04:03:54+00:00): You recently changed the English name (name:en=) from "Ayalon Stream" to "Nahal Ayalon". As an American, I find this to be an incorrect translation. The Nahal Ayalon, in English, is the "Ayalon Stream". Please explain your justification is changing the name from correct to incorrect!
davidmguest (2023-04-04 06:48:38+00:00): As Hebrew words do not correspond exactly to English words, there can not be just one "correct" translation. This is especially true with proper names.
Therefore both "Nahal Ayalon" and "Ayalon Stream" are equally valid.
Whilst "Ayalon Stream" is the more user-friendly translation, "Nahal Ayalon" better reproduces the flavour of the original.
That is why I reverted name:en to its previous value of "Nahal Ayalon", and set "Ayalon Stream" as an alternative in tag name:en1.
Yitzchak M (2023-04-14 15:39:49+00:00): Hi. I have done some research, combing through various OSM forums and basically, it comes down to the issue of translate vs transliterate. And I discovered that your philosophy is very much in line with another philosophy that I have now come to subscribe to: Write it in a way that if a foreigner from that language would say the name as written in the foreign language, a local resident would understand the name and where was meant. Or as you put it: "better reproduces the flavour of the original". Thank you for your input and I can now say that I agree with your change. Lastly, should "Nahal" be spelled "nahal" as you did, or spelled like the Americans would spell it: "Nachal"?
Yitzchak M (2023-04-14 16:25:50+00:00): I just did some more research and discovered that "h" is more appropriate than "ch". So, you got it right! :-)
ovruni (2023-03-26 07:18:41+00:00): Hola, en este conjunto de cambios se ha eliminado un nodo de centro poblado, se ha modificado limite de relaciones donde se han retirado varios nodos del contorno, se han eliminado varios edificios, para crear otros con geometrías similares (algo sobre lo que ya le había escrito anteriormente), por lo que he revertido el conjunto de cambios.
Saludos
Henry572 (2023-03-26 10:45:13+00:00): Hallo Frau Rauscher,
Willkommen bei OpenStreetMap!
Ich habe mir deine Bearbeitung angeschaut, weil du das im Editor angeklickt hattest. Es sieht alles gut aus.
Gruß,
Henry
gscholz (2023-03-28 07:25:17+00:00): Hi Omar,
here are still overlapping ways:

https://tools.geofabrik.de/osmi/?view=routing&lon=-79.45179&lat=-7.35195&zoom=16&baselayer=Geofabrik%20Standard&overlays=duplicated_edges%2Cunconnected_open_ends_1

Guido
ovruni (2023-03-29 00:28:15+00:00): Hola, he retirando el segmento de vía superpuesto. Gracias por el aviso.
Saludos
eggie (2023-07-11 07:29:04+00:00): Dag outofoffice... Wanneer er een wandelroute loopt over een pad met access=no zal het niet meer routeren.
Hier loopt het Veluwe zwerfpad..   Hoe loopt die route dan nu?

MVG
eggie
eggie (2023-07-11 07:32:17+00:00): De wandelroute heb ik omgeleid..
Geef svp een seintje aan de wandelrouteexperts op het forum van osm als je routes afsluit.
MVG
eggie
josmougn (2023-05-21 10:43:40+00:00): bonjour, est-ce que les cyclistes et les piétons peuvent passer  sur le pont de Charaintru ?
bxl-forever (2023-03-26 16:59:26+00:00): Hello,

For your information, there are several types of paths in our database.

When we code it as "highway=footway" in the database, it means that only pedestrians are allowed here.  That automatically excludes cyclists, horse riders, buses, cars…

Thanks for surveying and checking that it is indeed not a place for cyclists.

But since the map was already correct, it is *not* useful to add a restriction for cyclists… because the map already knows it.  Adding explicit tags to duplicate standard values just confuses everyone.

Have a nice day.
daperson (2023-03-26 08:23:41+00:00): vale decir que alinee 2 campos de juegos que por alguna razon estaban desconectados.
skyper (2023-03-27 20:29:45+00:00): Siehe https://www.openstreetmap.org/changeset/133242861 und https://www.openstreetmap.org/changeset/134127486.
Mateusz Konieczny (2023-07-03 07:14:05+00:00): Why you removed language part of wikkipedia tag? Was it intentional?

(either way, I fixed this)
skyper (2023-03-27 20:31:41+00:00): Siehe https://www.openstreetmap.org/changeset/133242861 und https://www.openstreetmap.org/changeset/134127486.
Henry572 (2023-03-26 10:25:38+00:00): Hallo Prinz Eisenarsch,
Ich habe mir deine Änderungen angeschaut, weil du das im Editor angeklickt hattest. In diesem Änderungssatz hast du doch gar keine Geschwindigkeitsbegrenzung bearbeitet, sondern nur die Abbiegerichtungen, oder?
turn:lanes:forward=left|through|right macht aber bei nur 2 Spuren in dieser Richtung keinen Sinn. Wolltest du das right vielleicht für die andere Richtung ergänzen? Dann müsste es mit turn:lanes:backward=right eingetragen werden.
Gruß, Henry
Prinz Eisenarsch (2023-03-26 10:39:14+00:00): Vielen Dank für Deine Hilfe.
Bitte gib mir eine Info, wo ich "beide Richtungen" auswählen kann bzw. den Eintrag vornehmen muss. Danke Gruß Guido
Henry572 (2023-03-26 10:58:20+00:00): Hallo Guido,
Beide Richtungen wäre der Wert von maxspeed; maxspeed:forward und maxspeed:backward würden jeweils nur die entsprechende Fahrtrichtung relativ zur Richtung des Weges (im Editor durch kleine Pfeile/Dreiecke dargestellt) angeben.

Jetzt wo ich mir die Karte genauer anschaue, sehe ich aber erstmal ein anderes Problem. Du hattest in https://www.openstreetmap.org/changeset/133242861#map=16/48.0574/10.9075 eine weitere Straße https://www.openstreetmap.org/way/1150900417 angelegt, obwohl ja schon für beide Richtungen die Straße vorhanden war.
Als grundsätzliche Regel gilt, dass man solange nur einen Weg/Straße mappt, wie alle Fahrspuren nicht "baulich getrennt" sind. Bauliche Trennung lässt zwar einen Spielraum offen, ob die vorhandene Sperrfläche schon als Trennung gilt, aber die einzelnen Fahrspuren für eine Richtung sollten auf jeden Fall nicht separat gezeichnet werden. Ich würde vorschlagen, dass du in dem oben verlinkten Änderungssatz auf den Kommentar von skyper antwortest, der scheint sich in der Gegend besser auszukennen als ich. Ich kann nur das bearbeiten, was im Luftbild sichtbar ist.
Gruß, Henry
skyper (2023-03-27 20:27:55+00:00): Hi,
zunächst habe ich leider keine Vor-Ort-Kenntnisse, sonst hätte ich das in den CS-Quellenangaben vermerkt. Ich habe nur einen Mapbox-Edit verbessert, siehe https://openstreetmap.org/changeset/134017085. Die Ortskenntnisse hat höchstens Prinz Eisenarsch.

JOSMs Validator hat mich dabei auf Ungereimtheiten in Bezug auf `maxspeed` hingewiesen, woraufhin ich meinen Kommentar geschrieben habe (https://www.openstreetmap.org/changeset/133242861).

Leider ist es auch nach den letzten Änderungen noch falsch, da entweder `maxspeed=` oder eben `maxspeed:forward=` und `maxspeed:backward=` mit unterschiedlichen Werten verwendet werden sollte, siehe https://wiki.openstreetmap.org/wiki/DE:Key:maxspeed#Unterschiede_nach_Fahrtrichtung. Eine Kombination `maxspeed=` mit `maxspeed:forward=` bzw. `maxspeed:backward=` ist nicht eindeutig.

Zusätzlich wurde jetzt auch noch `turn:lanes:backward=` entfernt.
Bitte achtet auf den Verlauf (Historie) der Objekte und den Kommentar plus die Quellenangaben zu den entsprechenden Änderungen.
Wer räumt das jetzt auf? Ich kann höchstens beim Zurücksetzten helfen.

Viele Grüße,
skyper