Jeżeli tag ma mieć więcej niż jedną wartość, to rozdzielamy ją średnikiem bez spacji, czyli zamiast:
`network=PKP Intercity, Polregio` powinno być:
`network=PKP Intercity;Polregio`

Już poprawiłem jakby co :)

Cześć, taka droga, którą dodałeś w OSM określamy drogą dojazdową i nie powinna mieć nazwy. Dodatkowo ograniczenie prędkości raczej na takiej drodze nie jest ustalone.

Poprawiłem tagowanie na poniższe:
```
highway=service
service=driveway
```

Wycofuję edycję jako błędną. W edycji dodano dodatkowe linie highway mimo braku podziału fizycznego jezdni.

changeset/159431359

Cześć, w jakim celu tworzysz nieistniejące podziały dróg? Brak podziału fizycznego jezdni, to powinna być jedna linia z dodatkowymi tagami lanes/turn:lanes - wymalowany azyl na jezdni nie jest fizycznym podziałem drogi. Twoja edycja jest błędna.

Wycofanie edycji, w której DDPiR bez rozdziału fizycznego został naniesiony jako dwie linie. Zepsute zostały też relacje bus.

changeset/159354397

Cześć, dlaczego rozdzielasz DDPiR na dwie linie, gdy nie ma rozdziału fizycznego pomiędzy częścią dla pieszych i rowerów?

Tak, wiem o tym ale z jednostką ładniej mi ten parametr wygląda :⁠-⁠)

I don't know how OSM will develop in connection with AI, but for now I'm struggling with it normally - manually.

I'm not encouraging or convincing you to use other tools than you need now, but you have to understand that mobile applications usually have fewer capabilities than tools available for PCs. Regardless of these limitations, the rules in OSM are the same for all editors.

I've corrected the charging stations to which you added descriptive names. If you included any data about the station in the name, I tried to enter it into OSM according to the rules written in WIKI. I moved the remaining data to the `description` tag or removed it if it seemed insignificant.

I've supplemented the station from this edition with data available on the Lidl Polska website.

node/12330757701

It is not said that no charging station can have a name. Maybe some new company will start naming their chargers, nameplates will appear, then such chargers in OSM will have names. Names in OSM can appear when it is verifiable in the field or when someone local considers that a given name is commonly used in the local community.

As long as there are no such chargers with names, the names in OSM will be deleted or moved to other tags - e.g. `description`. These are the rules here. If other applications have their own data, they can use it in their own invented way and the OSM community has no influence on this.

As you have probably read on amenity=charging_station, various tags are set in OSM to more precisely describe the capabilities of individual chargers. The fact that the charger is located on the premises of, for example, Lidl may describe an additional tag `operator=Lidl`

Unfortunately, there is no way around the fact that the rules for mapping in OSM are complicated, especially for beginner editors. OSM maps are like any new program that you have to learn to use. Not everyone is immediately fluent in Word or Excel, but with practice you gain some skill.

I hope you will not be discouraged from adding new data to the OSM map. It is not really difficult and these few simple rules will certainly be at your fingertips after a few edits.

Your information added to the map is available almost immediately, only 'OrganicMaps' updates the map data probably only once a month.

Chargers don't have a name and that's just the way it is. They are not restaurants, so the comparison is not correct.

I still don't understand what you want to achieve by adding a fictitious name with an address for chargers. This is not allowed in OSM and you can't change this standard. This is not my requirement, but the requirement of the entire community, which is set on the OSM WIKI.

Have you tried searching for charging stations in 'OrganicMaps' displaying all of them on the map? Instead of an address, which you don't have to know, it is easier to find an interesting place directly on the map.

https://i.imgur.com/ZD8WGuf.jpeg
https://i.imgur.com/F0hSlH4.jpeg

Thanks for the large amount of information in your answer.

If I understood you correctly, the 'OrganicMaps' application requires you to provide a name for the charging station you are adding. I have just added `charging_station` in this application for testing and the name was not required, I could add a point without any additional data. If it works differently for you, maybe you should update 'OrganicMaps'.

Additional data in the form of an incorrect name will not make it easier to find objects on OSM maps. OSM has fixed tag values ​​for this purpose, so that each application from each country can search for e.g. chargers, because it is enough to search for `amenity=charging_station`.

I recommend adding additional data related to the charging station in another application or directly through the osm.org website in accordance with the arrangements on the website: amenity=charging_station

You can also describe the charger data in 'OrganicMaps' in the notes (the field is available at the end of the form for adding an object in 'OrganicMaps') but there is no guarantee that someone will enter this data into OSM in accordance with the OSM WIKI.

Hello,
On OSM maps, it is enough to add a node marked as `amenity=charging_station` and this is enough information for applications to search for such a station. I do not know your application searching for charging stations, but such data from OSM can be easily obtained by generating a simple query to the database - e.g. this one: https://overpass-turbo.eu/s/1Ujw

Additionally marking the node with a name is allowed when such an object has its own name. The name of the charging station is definitely not its address. Here is information on how to use the `name` tag: osm.wiki/Names#Name_is_the_name_only

The address of the charging station can be determined using the geographic coordinates of this node.

I hope I managed to explain how to map charging stations in OSM.

Cześć, obiekt `amenity=parking_space` powinien być zawarty wewnątrz większego obszaru `amenity=parking` jako element tego parkingu. Poprawiłem ten parking w tej edycji: https://overpass-api.de/achavi/?changeset=159213768

Spoczko, z Relatify fajnie się je edytuje :)

Poprawiłem miasteczko akademickie

changeset/159108576

Takie parkingi przy drodze np. way/1333504271 warto oznaczać dodatkowym tagiem `parking=street_side`

Znaków typu `stop`, `give_way` itp nie powinno się wstawiać na skrzyżowaniach, tak jak tutaj node/12337321133 , bo nawigacje nie będą potrafiły określić kierunku którego taki znak dotyczy.

Cześć,
Nie wiem skąd masz źródło nazwy tego przystanku ale jeżeli posiada on dwie nazwy (pewnie każdy operator używa innej nazwy), to w `name` zostaw taką jaka widnieje na przystanku a drugą nazwę przerzuć do np. tagu `alt_name`. Wiem, że nie będzie się wtedy wyświetlała ale tak będzie bardziej poprawnie. Podwójny `ref` albo rozdziel średnikiem zgodnie z zasadami OSM albo drugi ref wrzuć np. do `ref:PKS` lub coś w tym stylu.
Pozdrawiam!

Please, don't add names with POI address.

Cześć, punkty adresowe, w szczególności te będące w obrysie budynku nie mogą mieć dodanego tagu `building=yes` - taką edycję zrobiłeś m.in. dla tego punktu: node/8395466750 - dasz radę poprawić wszystkie takie swoje edycje, bo podobną edycję zrobiłeś też przy tworzeniu np. tego węzła node/12331265263