Hi!
I changed the unusual highway=path:disused to the common disused:highway=path. See also osm.wiki/Lifecycle_prefix

Hi and welcome to OSM!
You changed the road class from highway=tertiary to the unusual value minor.
If I got that right the road is only used to get closer to the Philosopher Falls, so I think it is a highway=service + surface=unpaved.
See also highway=*

Hi Minh,
no idea what you mean. JOSM validator tells you when it finds duplicated ways. You have to decide which one is to be kept, normally I select the older one if both have the same tags. If they have different tags one has to deicde if the ways should be merged into one or not.

OK, I've removed all nodes in OSM which were last changed by mapper 91301101.
See changeset/53892373.
I see similar bad data from other mappers, e.g.here changeset/49097907
They all use source ditagis. Is that a valid source for OSM?

Hi!
I see that you mapped house numbers which is good but why did you add nodes with wrong tags like addr:place=a like this
node/5019216030 or with addr:housenumber=KS like this
node/5008712681 ?
Please correct the data or remove it.

Hi and welcome to OSM!
Please review typo highway=unclassfied
instead of unclassified on 6 ways,
e.g. way/541209115

Hi Minh,
I see that you finally managed to update the data. I still see many errors like duplicated ways, nodes with amenity=parking .
The tag amenity=parking is not meant for each parking space, you can use amenity=parking_space for this. See also amenity=parking

Yes, roads in OSM don't match with sat images and also both don't match with Strava data. Quite unusual. I am not a local and have no idea what data is best.

Hallo Stefan,
na ja, richtig oder falsch ist so eine Sache, bis heute scheint es kein anerkanntes tagging-Schema für die Fläche einer Verkersinsel zu geben. Ist ja auch fraglich, warum man die erfassen sollte. Aber egal, highway=traffic_island ist zumindest seltener als die Alternativen landuse=traffic_island , area:highway=traffic_island oder traffic_calming=island

Hi!
I've reverted mixed types highway=living_street;residential
on way/222401635 to highway=living_street, see changeset/53866881.
It seems that GoMap! produces these wrong tags, so please be careful and maybe contact the programmer to fix this problem.

Hi and welcome to OSM!
You changed the tag highway=primary to
highway="Jalan Desa Ranaka" here.
I guess that Jalan Desa Ranaka is the name of the road, so I changed it to
highway=primary + name=Jalan Desa Ranaka.
See also highway=*

Well,
I am not checking you but the list of highway=* values from taginfo. Whenever I see a new way with an unusual value and I think it is not just a typo I try to connect the mapper.

Hi!
Please review misplaced tag highway=traffic_signals
on way/149469091
and way/199548218

Hi and welcome to OSM!
I changed the unusual highway=service_road to service here changeset/53832667
See also highway=*

Hi!
I've changed highway=residential_link to secondary_link + oneway=yes, see changeset/53832589
Please use only those _link values listed in the wiki:
highway=*#Link_roads
See also http://gis.19327.n8.nabble.com/highway-residential-link-td5859566.html

Hi!
Please review highway="residential;unclassified" on way/191201005
It seems that the app GoMap! creates such wrong data ?

Hi!
I just stumbled over what looks like totally misaligned roads and found this changeset.
See e.g. node/1039759640
or the track starting at node/2524448338
Maybe the sat images changed since your changes? Current layer from Strava seem to say that DigitalGlobe sat images are good, but maybe out-aged.

Hi!
Please review typo highway=hi on way/540588776

I am not sure what you mean. I refered to nodes with e.g. addr:housenumber=ks or KS,
shop=123 or maybe addr:place=a.
This area is full of this data and it is nearly impossible to fix it without local knowledge.

OK, seems that the two alternatives are both accepted. So I've learned something new ;-)