piebro/osm-data huggingface dataset:
commented by Lostmonkey (2025-04-30 11:42:11+00:00): Personally I am not going to engange in a "mapping war" over this but just want to reiterate that this is (in my opinion) already covered by the private tag. That some map renderers perhaps dont make use of the available data to make the distinction between private and public parking clear is not an issue with OSM.
commented by Jones57 (2025-04-30 13:43:03+00:00): No intention of starting a "mapping war" here either 😄 Just to clarify where I'm coming from: the homeowners' association is dealing with an ongoing issue where residents are regularly finding their designated spots taken by non-residents. When confronted, these drivers often refer to their GPS saying it’s a public parking area.

So while I fully appreciate that the "private" tag is in place (and agree it's the correct way to do it in OSM), the challenge seems to be that some apps don’t interpret that data clearly — and the end result is confusion on the ground.

I realise that's not something OSM can directly fix, but just wanted to share the background, so you know it’s not about map politics — just about trying to make everyday life a bit easier for the folks living there.
commented by Lostmonkey (2025-04-30 13:49:53+00:00): Maybe try to wait a little longer to see if setting the private-tag makes a difference. It has been less than a week since I set it and apps and other maps often dont update their OSM-data that quickly. It can take several weeks or even months.
commented by Jones57 (2025-04-30 17:38:46+00:00): That’s a fair point – I’ll definitely give it some more time to see if the update makes a difference in practice.

That said, I still believe it might be better if the area isn’t marked as parking at all. Since the spaces are strictly reserved for residents, and not relevant for general public use, it seems more accurate (and perhaps less confusing) to leave it untagged as parking altogether.

But I appreciate the effort you’ve already put into tagging it correctly – and happy to go with what the wider community considers best practice
commented by Lostmonkey (2025-04-30 19:03:49+00:00): I can of course understand your argument and sympathize with the residents. And perhaps removing it entirely would help to keep some people from parking there. On the other hand I think you will find that most experienced OSM-mappers will tell you it's a very slippery slope if you start tagging objects differently in OSM than they are in reality (or delete them) just to compensate for shortcomings in other apps (or people ignoring the info in the data). Also, regarding the "wider community": According to the OSM-wiki about mapping private information, "Mapping private buildings, private roads (including driveways), and private parking is completely acceptable. Add access=private as appropriate to roads, parking lots, etc." ( https://wiki.openstreetmap.org/wiki/Mapping_private_information )
commented by Jones57 (2025-04-30 19:56:13+00:00): Thanks for the detailed response – and fair point regarding OSM’s approach to representing real-world features accurately. I’ve read the wiki on Mapping private information, and I fully understand that mapping private parking is acceptable and even encouraged when tagged correctly with access=private.

That said, the real issue we’re facing locally isn’t about tagging as such, but the practical consequence: these resident-only spots are showing up as general parking in various apps that don’t interpret the access restrictions. This leads to regular confusion and unwanted parking — and it’s becoming a real frustration for the people who actually live there.

From that perspective, I’m simply trying to find a pragmatic way to reduce the misuse. I do realise removing the parking tag may go against general OSM practice, but since the parking is not intended for general use anyway, I still believe that omitting it entirely might more accurately reflect its functional availability to the public.

I’m definitely open to alternative tagging suggestions that would achieve the same effect — keeping it invisible to most navigation apps while staying within OSM guidelines. Let me know if there’s a better route to that goal!
commented by Linus W Frische (2025-04-30 20:33:51+00:00): The thing is, that even if we remove it, nothing is stopping someone else from just readding it to the osm-database again in a year's time. 

You should contact the "various apps" and complain that they are showing private parking as publically accessable; urge them to parse the access key.
commented by Jones57 (2025-04-30 20:44:48+00:00): That’s a valid point — and I understand that there’s always a chance someone might re-add it later.

Still, I’d argue that we could just try removing the parking indication for now and see if that helps reduce the misuse. If it doesn’t stick long term, then at least we’ve tested it in practice rather than assuming in advance that it won’t last.

Of course, I agree that apps should interpret the access key properly, and I’ll look into contacting a few of them. But from a resident’s perspective, even a temporary improvement would be a step in the right direction.

Thanks again for the discussion — really appreciate the open exchang
commented by Lostmonkey (2025-04-30 21:10:18+00:00): From what I can see on streetview there is already a clear no entry sign (except for residents) for your street from the main road. In addition your street is also tagged 'private' in OSM. Perhaps blaming their map app is simply a bad excuse people come up with when confronted? In any case, I would still suggest giving it some time with the 'private' tag and then take it from there (complain to the app makers).
commented by Jones57 (2025-04-30 22:16:00+00:00): You’re absolutely right — there is a sign at the entrance stating no entry except for residents, and the street is correctly tagged as ‘private’ in OSM. But in practice, that sign isn’t always respected, especially since parking is in high demand due to the hospital across the road.

I agree that the GPS excuse might sometimes just be a convenient justification when people are confronted. Still, that’s exactly the kind of excuse I’d like to eliminate by ensuring the area doesn’t appear as publicly accessible parking in the first place.

In short, while the intention behind the current mapping might be good, the result is that it causes frustration for a number of residents — without adding real value to the broader public. That’s why I still believe it would be more appropriate to remove the parking indication entirely in this case.

Thanks again for the ongoing dialogue — it’s genuinely appreciated.
commented by cyclist789 (2025-05-11 11:37:44+00:00): https://www.openstreetmap.org/#map=19/55.737226/12.547547&layers=N
On osm.org itself, the 🅿️ for this parking lot is almost invisible, unlike those on the other side of Kildegårdsvej. (But maybe it was better to not display private areas *at all* on the main map.)

As I understand it, the policy of OSM is to tag things *as they are*, and leave to the app-designers the responsibility of how to *display* them.
But perhaps OSM should provide some best-practice guide for this (assuming that it doesn't already) to those that make the map apps and editor apps. I say the displaying of parking spaces should depend on both the *access*, *fee*, and *maxstay* tags. Maybe display "2:00h 🅿️💲" for 2-hour paid parking, and "🛍️🅿️" for customer parking, and hide any parking lots without recognized *access* tags.

I also feel like the access values should be far more visible on maps than e.g. the difference between an unpaved footpath and an asphalt motorhighway.

Do you happen to know which apps display parking lots poorly?

There is also a chance that the ones who steal your parking spaces never used a map at all, but saw the parking lot through their car windows and thought: "If I get caught, I'll just lie and say that my GPS told me to park here."

And besides, "my GPS told me" wouldn't hold in court. Tell the police to make them stop.
commented by Jones57 (2025-05-11 13:54:50+00:00): Thanks for the thoughtful input — I agree with much of what you’re saying, especially the idea that app developers should be encouraged to factor in access, fee, and maxstay more actively in their visual design. And yes, the current 🅿️ indication on osm.org is quite subtle — but unfortunately, that’s not the case across all platforms.

You’re absolutely right that “my GPS told me” wouldn’t hold in court — but the point is: why should that even be an excuse people can reach for, when we have the option of removing the cause of the confusion altogether?

I still firmly believe that if the parking area is not intended for public use — and, in fact, is privately owned and allocated to specific residents — then the community of owners should reasonably have a say in whether it appears as a public amenity on the map. If other residents in similar situations suddenly saw their private driveway marked as a parking lot, I imagine they’d be equally frustrated — especially in a high-pressure area where parking is already a serious problem due to the nearby hospital.

So while I appreciate the general OSM principle of mapping what exists physically, I think this is a clear example where displaying something brings more harm than benefit — and removing the parking tag would, in this case, reflect its actual availability better than its mere physical presence.

Thanks again for taking the time to engage — I really value the constructive tone in this discussion.
closed by Linus W Frische (2025-05-11 14:21:23+00:00): As has been stated multiple times now, it is on the app developers to represent data correctly. Now that the parking lot has been marked as private, there is nothing more that can/should be done in osm. The parking lot will not be deleted.

I highly doubt your problem is caused by osm in the first place. They passed a physical, visible sign. They are just coming up with excuses. We should not let these bad people force us to make our map worse.

I think you should call the police/other relevant authorities if people park illegally. If you are aware of an app that shows the parking as publically accessable, reach out to the app developers. I am going to close the note now.
opened by Antisthenes (2025-04-24 14:03:10+00:00): Spielplatz

via StreetComplete 60.3

Attached photo(s):
https://streetcomplete.app/p/273483.jpg
closed by ironspock (2025-06-02 16:18:35+00:00): war/ist bereits eingetragen (siehe https://www.openstreetmap.org/way/68742631/history)
opened by Dave7007 (2025-04-24 14:03:14+00:00): David gate

#OsmAnd
opened by Claudia sendas grischunas (2025-04-24 14:03:15+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
commented by habi (2025-04-25 10:01:10+00:00): Der Weg ist auf dem digitalen Geländemodell von swisstopo sehr gut sichtbar, und wird laut der Strava Heatmap auch häufig begangen und befahren.
In https://www.openstreetmap.org/changeset/165415451 etwas an diese beiden Quellen angepasst.
closed by habi (2025-04-25 10:01:10+00:00): https://www.openstreetmap.org/changeset/165415451
opened by Claudia sendas grischunas (2025-04-24 14:03:33+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
closed by habi (2025-04-25 10:01:10+00:00): Der Weg ist auf dem digitalen Geländemodell von swisstopo sehr gut sichtbar, und wird laut der Strava Heatmap auch häufig begangen und befahren.
In https://www.openstreetmap.org/changeset/165415451 etwas an diese beiden Quellen angepasst.
opened by Claudia sendas grischunas (2025-04-24 14:03:55+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
commented by habi (2025-04-25 08:03:17+00:00): Ciao Claudia
Auch wenn dies hier alles "keine offiziellen Wege sind", sind diese auf den swisstopo Orthofotos zu sehen.
Zusätzlich ist auf der Strava Heatmap [1] hier einiges an Aktivität zu sehen, die Wege werden also begangen.
Deshalb können (und sollen) die Wege auch in OpenStreetMap auftauchen.

Gruss aus Bern, 
habi

[1]: https://www.strava.com/maps/global-heatmap/segments?sport=Hike&style=dark&terrain=false&labels=true&poi=true&cPhotos=true&sType=all&sElevation=all&sSurface=0&sMin=0&gColor=hot&gOpacity=100#11.84/46.81634/10.21211
closed by habi (2025-04-25 08:03:18+00:00): Mit https://www.openstreetmap.org/changeset/165410557 etwas angepasst
opened by Claudia sendas grischunas (2025-04-24 14:04:18+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
commented by habi (2025-04-25 09:42:12+00:00): Der Weg ist auf dem digitalen Geländemodell von swisstopo sehr gut erkennbar: https://pasteimg.com/image/screenshot-from-2025-04-25-11-41-29.nbcjs
closed by habi (2025-04-25 09:52:53+00:00): Mit https://www.openstreetmap.org/changeset/165415135 erledigt
opened by Claudia sendas grischunas (2025-04-24 14:04:31+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
closed by habi (2025-04-25 09:16:39+00:00): Mit https://www.openstreetmap.org/changeset/165413607 gelöst.
Kommentar dazu wie für alle anderen Notizen in dieser Gegend: Der Weg ist auf den Orthofotos und in der Strava Heatmap sichtbar, also kann er auch in OpenStreetMap verbleiben.
opened by Claudia sendas grischunas (2025-04-24 14:04:36+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
closed by habi (2025-04-25 09:38:36+00:00): https://www.openstreetmap.org/changeset/165413373
opened by Claudia sendas grischunas (2025-04-24 14:04:49+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
commented by habi (2025-04-25 09:28:19+00:00): Der Weg ist auf dem digitalen Geländemodell von swisstopo sehr gut zu erkennen.
commented by habi (2025-04-25 09:28:19+00:00): Auf der Strava Heatmap sieht es aus, als wären hier schon viele Menschen durchgegangen.
closed by habi (2025-04-25 09:38:06+00:00): Mit https://www.openstreetmap.org/changeset/165413373 gelöst
opened by Claudia sendas grischunas (2025-04-24 14:04:55+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
closed by habi (2025-04-25 09:16:35+00:00): Mit https://www.openstreetmap.org/changeset/165413607 gelöst.
Kommentar dazu wie für alle anderen Notizen in dieser Gegend: Der Weg ist auf den Orthofotos und in der Strava Heatmap sichtbar, also kann er auch in OpenStreetMap verbleiben.
opened by Claudia sendas grischunas (2025-04-24 14:05:05+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
closed by habi (2025-04-25 09:16:31+00:00): Mit https://www.openstreetmap.org/changeset/165413607 gelöst.
Kommentar dazu wie für alle anderen Notizen in dieser Gegend: Der Weg ist auf den Orthofotos und in der Strava Heatmap sichtbar, also kann er auch in OpenStreetMap verbleiben.
opened by Claudia sendas grischunas (2025-04-24 14:05:42+00:00): PP ist weiter unten, bis hier ist ein Fahrverbot.
closed by habi (2025-04-25 09:28:15+00:00): Mit https://www.openstreetmap.org/changeset/165414076 erledigt
opened by  (2025-04-24 14:06:05+00:00): MANCANTE: COLONNA PARK HOTEL, PORTO CERVO, VIA DELLA MARINERIA
opened by Claudia sendas grischunas (2025-04-24 14:06:16+00:00): Hier ist ein PP, ab hier ist Fahrverbot auf der Via d'Alp Laret
commented by habi (2025-04-25 09:28:19+00:00): Ein Poller, der motorisierten Verkehr stoppt ist erst weiter oben erfasst: https://www.openstreetmap.org/node/11162704987
commented by habi (2025-04-25 09:28:20+00:00): Ich habe in https://www.openstreetmap.org/changeset/165414076 den sog. Access-Tag nach https://wiki.openstreetmap.org/wiki/Switzerland/Map_Features#Other_common_Signs mit 'motorisiertem Verkehr verboten' angepasst.
closed by habi (2025-04-25 09:28:26+00:00): Mit https://www.openstreetmap.org/changeset/165414076 erledigt
closed by Claudia sendas grischunas (2025-04-29 07:52:13+00:00): Danke ... der Poller ist nicht so entscheident wie das Verbotsschild, oder?
closed by habi (2025-04-30 07:10:03+00:00): Der Poller verhinderte schon vorher bei der https://wiki.openstreetmap.org/wiki/DE:Routenplanung, dass Autos dort durchgeleitet werden, jetzt hat https://www.openstreetmap.org/way/217531906 auch die Information, dass motorisierter Verkehr nicht erlaubt ist.
opened by Blauwdruk (2025-04-24 14:06:23+00:00): Unable to answer "Is this still here?" – Omega Pharma (Corporate Office) – https://osm.org/node/6504970145 via StreetComplete 60.3:

Dit is nu logistiek en facilitair platform Maria Middelares
closed by Thibault Rommel (2025-04-26 13:24:29+00:00): aangepast
opened by Alireza atash (2025-04-24 14:06:49+00:00): تعمیرگاه اسکانیا جهان
commented by Alireza atash (2025-04-24 14:07:12+00:00): تعمیرگاه اسکانیا جهان
opened by HJS_Holten (2025-04-24 14:07:13+00:00): Via dit punt Maarten van Rosssumpad
commented by Geim (2025-04-24 16:16:41+00:00): Wat bedoel je hier precies mee? Wat kan er aangepast worden op de kaart?
commented by HJS_Holten (2025-04-24 16:50:15+00:00): Gezien tijdens geochachen: Het Maarten van Rossumpad is in deze omgeving verlegd. O.a. loopt het pad nu via dit punt (deze zeer scherpe bocht).
commented by dvdhoven (2025-04-24 17:11:40+00:00): In wandelnet staat het MvR pad precies zo als in OSM.
Het kan zijn dat het inmiddels verlegd is, maar daar is digitaal nog geen bron voor te vinden
commented by HJS_Holten (2026-01-12 11:16:25+00:00): Net gemeld (12-1-2026) dat de wijziging in het veld nog steeds niet is doorgevoerd op diverse sites (wandelnetwek/PDOK viewer onder LAW)
bij wandelnetwerk
opened by Claudia sendas grischunas (2025-04-24 14:07:51+00:00): Hier sind diverse Wege einzeichnet die keine offiziellen Wege sind - bitte streichen (siehe SWISSTOPO)
closed by habi (2025-04-25 10:05:38+00:00): Resolved with changeset https://www.openstreetmap.org/changeset/61573840 by noteSolver_plugin/0.5.0
opened by  (2025-04-24 14:07:52+00:00): onosm.org submitted note from a business:
نام: عکاسی آریان
addr:housenumber=40
addr:street=نور
addr:place=نور
addr:city=Urmia
addr:postcode=5717833586
شماره تماس: 09388014151
وب‌سایت: https://musicsweb.ir/
ساعات کاری: شنبه - پنچ شنبه ساعت 8.30 تا 9 شبب
دسترسی با ویلچر: yes
دسته‌بندی: فروشگاه ها و خدمات عکاسی
توضیحات: عکاسی و فتوکپی - پرینت رنگی و سیاه سفید 
روش های پرداخت پذیرفته شده: نقد
takeaway=yes
takeaway:description=عکاسی در بیرون
closed by Mateusz Konieczny (2025-08-04 03:44:44+00:00): to person creating thousands upon thousands of this notes - have you considered actually editing OpenStreetMap? You cannot copy shops locations from Google Maps, but you can go on walk and add some of them. Or map remotely, there is Bing Streetside imagery in some places. Or map buildings remotely.

Creating note flood is simply not useful, or even harmful.

close not needed onosm note

Iran is simply flooded with them - with so many that people started closing notes in Iran solely for being old, and over 60 000 notes were closed in 2023. It is better to close just this not needed flood and notes with higher chance of being useful will remain.

Note that notes about missing shops are nearly useless - they do not speed up mapping, it is trivial to find missing shops nearly anywhere.

See https://resultmaps.neis-one.org/osm-notes-country?c=Iran&stats=full
opened by RedAuburn (2025-04-24 14:08:36+00:00): this cycleway section needs adding to relations
closed by RedAuburn (2025-04-24 22:48:20+00:00): looks like it's ok actually?
opened by AndreasUserfriendly (2025-04-24 14:11:43+00:00): Unable to answer "What’s the surface here?" – Foot Path – https://osm.org/way/34632164 via StreetComplete 60.3:

Verwildert

Attached photo(s):
https://streetcomplete.app/p/273484.jpg
closed by AlexSpritze (2026-01-13 07:45:23+00:00): https://www.openstreetmap.org/changeset/177166974
opened by davidoclubb (2025-04-24 14:13:00+00:00): Playground

via StreetComplete_ee 60.3

Attached photo(s):
https://streetcomplete.app/p/273485.jpg
closed by confusedbuffalo (2025-10-11 17:06:19+00:00): Already mapped, thanks
opened by 94621 (2025-04-24 14:13:06+00:00): Speed bump

via StreetComplete 60.3
closed by Carlos Martin Noriega (2025-06-25 06:01:59+00:00): added
opened by  (2025-04-24 14:13:09+00:00): Newly constructed apartment building opened here in 2025:

Riverwalk Heights
430 Main St, New York, NY 10044
closed by Hypsometric (2025-04-28 12:34:01+00:00): Added.
opened by 94621 (2025-04-24 14:14:32+00:00): Speed bump

via StreetComplete 60.3
closed by Carlos Martin Noriega (2025-06-25 06:01:19+00:00): added
opened by AndreasUserfriendly (2025-04-24 14:14:32+00:00): Ferienhaus ,signature lodge'

via StreetComplete 60.3

Attached photo(s):
https://streetcomplete.app/p/273486.jpg
closed by AlexSpritze (2025-07-22 08:35:33+00:00): https://www.openstreetmap.org/changeset/169280463
opened by 94621 (2025-04-24 14:14:48+00:00): Speed bump

via StreetComplete 60.3
closed by Carlos Martin Noriega (2025-06-25 06:00:04+00:00): added
opened by nuclearsnorkel91 (2025-04-24 14:15:13+00:00): In context of overlay "Addresses" – house number 1458: Building – https://osm.org/way/775238215 via StreetComplete 60.3:

Holding lot for Phase1 Recovery

Attached photo(s):
https://streetcomplete.app/p/273487.jpg
closed by MikeN (2025-04-24 14:45:30+00:00): Add driveway and gate
opened by AndreasUserfriendly (2025-04-24 14:16:23+00:00): Zwei Ferienhäuser im Bau

via StreetComplete 60.3

Attached photo(s):
https://streetcomplete.app/p/273488.jpg
closed by AlexSpritze (2025-07-22 08:34:02+00:00): Hinzugefügt: https://www.openstreetmap.org/changeset/169280402
opened by 94621 (2025-04-24 14:17:49+00:00): Speed bump

via StreetComplete 60.3
closed by Carlos Martin Noriega (2025-06-25 05:58:46+00:00): added
opened by ali1k88 (2025-04-24 14:18:38+00:00): Countrywide Group of Companies
opened by 94621 (2025-04-24 14:19:32+00:00): Speed bump

via StreetComplete 60.3
opened by ali1k88 (2025-04-24 14:19:53+00:00): Leamington Bandstand
opened by 94621 (2025-04-24 14:20:34+00:00): Speed bump

via StreetComplete 60.3
closed by Carlos Martin Noriega (2025-06-25 05:49:42+00:00): added
opened by Hannes Röst (2025-04-24 14:20:41+00:00): construction Apr 2025
closed by skfd (2025-05-13 14:09:44+00:00): added
opened by  (2025-04-24 14:20:43+00:00): onosm.org submitted note from a business:
نام: تعمیرگاه اسکانیا جهان
addr:street=بلوار کربلا جنب آرد سفید اراک
addr:city=Arak
شماره تماس: 09185270768 - 09182945839
ساعات کاری: همه روزه از ساعت 8:00 الی 00:00
دسترسی با ویلچر: yes
دسته‌بندی: تعمیر خودرو
توضیحات: تعمیرگاه اسکانیا جهان
روش های پرداخت پذیرفته شده: 
takeaway=no
opened by 94621 (2025-04-24 14:20:47+00:00): Speed bump

via StreetComplete 60.3
closed by Carlos Martin Noriega (2025-06-25 05:48:00+00:00): added
opened by 94621 (2025-04-24 14:21:11+00:00): Speed bump

via StreetComplete 60.3
closed by Carlos Martin Noriega (2025-06-22 17:17:03+00:00): added
opened by 94621 (2025-04-24 14:21:31+00:00): Speed bump

via StreetComplete 60.3
closed by Carlos Martin Noriega (2025-06-22 17:15:16+00:00): added
opened by esaulenka (2025-04-24 14:22:11+00:00): water 

#OsmAnd
closed by DrDimedrol (2025-08-02 11:24:08+00:00): on map
opened by  (2025-04-24 14:23:55+00:00): Ab sofort bis Ende Juni 2025: Vollsperrung B97 in Richtung Spremberg zw. Berliner Straße und B156: https://www.rbb24.de/panorama/beitrag/2025/04/sperrung-b97-spremberg-brandenburg.html
closed by Fabian1429 (2025-07-19 20:25:43+00:00): Sperrung von langer Dauer werden in OSM als Straße in Bau gekennzeichnet. Bei kürzeren Baumaßnahmen (wie in diesem Falle da Unterteilung in einzelne Abschnitte mit kürzerer Baudauer) ändert sich in der Darstellung bei OSM nichts.
opened by Αντρέ (2025-04-24 14:28:37+00:00): Ολύνθου 6

via StreetComplete 60.3
opened by Αντρέ (2025-04-24 14:28:37+00:00): Ολύνθου 8

via StreetComplete 60.3
opened by Αντρέ (2025-04-24 14:28:38+00:00): Ολύνθου 10

via StreetComplete 60.3
opened by Αντρέ (2025-04-24 14:28:38+00:00): Μακρυγιάννη 108

via StreetComplete 60.3
opened by Αντρέ (2025-04-24 14:28:38+00:00): Μακρυγιάννη 106

via StreetComplete 60.3
opened by Αντρέ (2025-04-24 14:28:39+00:00): Κοραή 12

via StreetComplete 60.3