Please stop making strange data duplications! -> Reverted

Thanks, it seems I overlooked some, probably because of the amount of the problems in this area.

I'm sorry for modifying it, I could not believe this as the location is within a town. I reverted my change and added the layer tag.

If you don't remember the other similar changes, this is no problem, the routing view of the OpenStreetMap inspector at https://tools.geofabrik.de/osmi/?view=routing&lon=2.71068&lat=48.72189&zoom=11&baselayer=Geofabrik%20Standard&overlays=unconnected_open_ends_1 detects these cases and I will inform you.
Thanks!

Great!

Can you also please check the other edits you did? Here is another example I detected: changeset/155613067

You created the new way way/1309110592 although there is already way way/242885938 there. Now they are parallel ways. It might be a bad implementation of the Go Map editor your are using. Please open the ways in a proper OSM editor like ID or JOSM and then you'll easily understand what I mean.

Hi sis651!

Please stop tagging highway=track with the name Tarla Yolu. I looked it up, it is the turkey name of track road and we don't use the name tag for classification

thanks

ratrun

Hi and welcome to OSM!

Could you please check you newly created oneway way way/1309110592 ? Please delete this way and apply the oneway tag to the respective segments of the previously already existing way way/242885938. Splitting this way before might required.

Thank you!

Hallo,

Sorry und danke fürs richtigstellen!

Sorry, but it seems you didn't understand my concerns: Just adding the tags is not enough, now you need to connect these ways to the existing ways. Otherwise the are not connected.

Hi,

this was not good idea as these ways are disconnected from the rest of the network. Please fix this, otherwise I'll need to revert.

thanks a lot for detecting this. I'm very sorry for creating this changeset with a way to big bounding box. It was an accident when I removed many way nodes in Africa, which were tagged with a surface tag. I forgot to click the search invert in JOSM when I searched for the nodes. I reverted the changes in Germany here: changeset/154743699

Hallo Hypoferalkus!

Der Knoten
node/12084023010#map=19/50.26241/9.18948 ist nicht verbunden mit dem Nachbarknoten node/12084023009. Auf Bing ist ein Hindernis dazwischen erkennbar, aber nicht gemapped. Kannst Du bitte entweder die beiden Knoten mergen oder mit noexit=yes versehen - je nachdem wie das vor Ort aussieht?

Danke
ratrun

Hi,

Can you please be more descriptive in your changeset comment? Where does your source come from? On the Bing areal image which you used as background this new ??? road is not visible. Additionally this road is not connected to the existing ways in that area. If this is a new road they please connect it correctly to the existing ways.

thanks

ratrun

It seems this user is a vandal. I asked the DWG for a complete revert of all changes made

Hi,
what is the purpose of way/377639961 This perfect circle highway residential is obviously wrong.

Hi,

please check node/741999000/history for road connectivity. It looks very unrealistic that it ends at this point with a noexit

thanks
ratrun

Hi,
I fixed a routing error by merging the separate unconnected end points of your new ferry line to node node/83560399#map=19/37.90583/20.70649 such that it got connected to the pier way/77669809#map=19/37.90522/20.70794. I cannot provide more details because user CharliePlett edited the ferry route again just a few minutes ago. As I don't know which way you meant by "the line" I cannot reproduce what your note that it does not show up. I can only say that I do see the ferry route in JOSM and also on lower zoom levels of the carto rendering.

Hi and welcome to OSM,

first, when you make changes please make sure to add a usefull changeset comment. "CDCDDDDD" is useless.

Second, please check your tagging: The tagging for way/1294896327 does not make any sense as "access=no" forbids any access. Additionally it looks as as if you should have tagged this way as highway=cycleway. Further more, name="CICLO VIA" is not correct, as this is not the name of this segment.

Additionally way/1294896326#map=16/-5.9527/-77.3014 is missing connectivity to the rest of the road network. When you addd new ways please check the connectivity.

ratrun

The splitting of the way into several segments is important as the route follows already mapped walking infrastructure. Otherwise ways get mapped twice, which needs to be avoided.

As you say that this is an offical route then please create a route relation, see route=hiking