As I do not know the location, I cannot answer. But you are right, probably it would have been better to leave the node disconnected and add a "noexit=yes". But from my understanding usually a barrier is usually tagged in case that the way continues beyond.

This import has created a huge amount of unconnected ways. See http://tools.geofabrik.de/osmi/?view=routing&lon=8.82596&lat=58.47437&zoom=11&overlays=unconnected_major1,unconnected_major2,unconnected_major5. Please point me to where this import was discussed. I belive it should be reverted. Or do you plan to fix this manually?

Could you please check way/437821818 ? According to bing images and existing data this new road is not plausible.

In a private message I got the folllowing information "I just realized you have deleted the road between Manono and Mpiana and wonder why."

-> Now I see what you mean. I'm sorry for that, this happened by accident and I didn't notice. It seems that you already did restore it. So there is no need for a partial revert. Right?

I'm sorry, I cannot guess which way you are talking about. There were multiple geometrical problems in the data. The most prominent was way/261675844, which was obviously acciditially moved to an incorrect location such that it overlapped with other existing data.

Diese Änderung sieht sehr seltsam aus, sie ist voller Fehler (Unverbundene Knoten ohne Rücksicht auf die bestehenden Wege.) Wenn hier wirklich eine Umfahrung gebaut worden ist, dann bitte überarbeite und verbessere Deine Änderung gründlich, ansonsten werden ich sie rückgängig machen. Danke!

What happened here? This changeset looks really bad. As it is obvious that something is wrong here I deleted it.

Thank you. I tagged the information you gave here.

Thank you. Usually an OSMI update takes 24 hours. I believe that currently the new update gets active at between 10:00 UTC and 14UTC.

Please see all the red points at OSMI (=Open Streetmap inspector):

http://tools.geofabrik.de/osmi/?view=routing&lon=58.74440&lat=23.45595&zoom=11&overlays=unconnected_major1,unconnected_major2,unconnected_major5,duplicate_ways

The documentation of the tool can be found here:

osm.wiki/OSM_Inspector/Views/Routing

All the red nodes are not connected to a way nearby and from what I see most of these errors come from your two recent commits. These errors were not present yesterday.

The trigger for my comment was this

way/383745994

and this way

way/383745995

Based the bing background image in JOSM I cannot imagine that there is a residential way. There is no building anywhere nearby. I only see big rocks and the resolution is not that bad in this area.

Arcgis is a quite an unusal editor. Usual editors like JOSM provide the possiblity to add a source for each commit. Here I would expect GPS in your case. This is missing in your commit. Eventually Arcigs does not support it, but the comment "Network" didn not tell me anything either.

Thank you for not getting angry about my ciritical comments. I must say that I found these bad examples per incident. Most of the rest of the new ways look possible, although the precision of the locations look to be quite bad in general. Usually a sattelite background image is moved constantly into one direction compared to a usually more precise GPS track. But this does not seem to be the case with your change.

Could you please provide information about the source you are using. According to bin areal image the data looks to be of very bad quality. And there are a lot of geometrical errors contained, as the ways are often not connected to already exising ways.

I'm using OSMI.OSMI is the Open Streetmap Inspector. This is the view I'm using most of the times:

http://tools.geofabrik.de/osmi/?view=routing&lon=12.61778&lat=49.40295&zoom=6&overlays=unconnected_major1,unconnected_major2,unconnected_major5,duplicate_ways

Documentation can be found here:
osm.wiki/OSM_Inspector/Views/Routing

This is a terrible mechanical import of bad quality which should be reverted.

You are destroying the connectivity of the network. Please stop and revert this! See http://tools.geofabrik.de/osmi/?view=routing&lon=2.21356&lat=35.27907&zoom=7&overlays=unconnected_major1,unconnected_major2,unconnected_major5,duplicate_ways . Most of the errors seem to be cause by this commit!

Please check way/261017189 and the parallel oneway leading into the other direction: Theses segments are not connected and I can't guess the attached only_straight_on restriction relation.

Falls wirklich keine Verbindung besteht, dann setzt bitte ein noexit=yes auf den östlichen Endknoten. Laut Bing Lufbild sollte aber zumindest eine Verbindung mit dem Fussweg bestehen.
Wenn der östliche Ausgang für Taxis gesperrt ist, dann sollte wohl das westliche Ende verbunden werden, sonst hängt diese Strasse ja in der Luft.

Sorry und danke, ich habe erst jetzt mein Missverständnis bemerkt. Ich habe mich irritieren lassen durch die ähnlichen Ampel Icons von JOSM. Aber eigentlich sind es die Icons für highway=traffic_signals und crossing=traffic_signals eh leicht unterschiedlich. Ich habe es revertiert jetzt und verspreche, dass ich in Zukunft zwei mal schaue bei so etwas.

Als Contributor von graphhopper kann ich Deinen Einwand mit jetzigen Erklärung nun verstehen, aber das doppelte Tagging kann nicht die Lösung sein - hier handelt es sich doch eindeutig um Tagging für den Router.

Weil der 2.5 Meter entfernte Eintrag auf node/1115213365 für die selbe Ampel reicht.

I'm sorry I only understand German or English.