Thanks for fixing this and for your relentless efforts of fixing bad OSM data in general 😄

Good day. Would you mind sharing your reverting workflow? Especially for cases when you notice that affected objects have already been edited in the meantime.

Method seems to have improved since changeset/180762095 as now tags of already conducted repairs are preserved.

But somehow this revert has removed numerous nodes from way member list for no apparent reason, causing several new geometry and connectivity issues.

Place node histories have been restored in changeset/181254779

Good day. Looks like you missed some follow-up edits made after the reverted changeset but before your revert. As a consequence your edit removed numerous lifecycle disused prefixes and check_dates while restoring unnecessary tags that have been previously deleted.

Fixed in changeset/181032160

Welcome to OSM and thanks for your edits!

Indoor mapping is quite complicated, if you plan to do more of it I would recommend having a look at this guide on the OSM wiki: osm.wiki/Simple_Indoor_Tagging

Some basic things to consider:
- highway=footway for outdoor ways, highway=corridor for indoor ways
- name tag is only for actual names, not descriptions
- building parts and rooms that share physical walls should also be connected in OSM

If you would like to get in touch with fellow local mappers, here's a list of channels maintained by the OSM PH community: osm.org/wiki/PH

Accidentally deleted objects restored in changeset/181024216

Good afternoon. Could you please have another look at the name tags of Daang Hari Extension/Open Canal Road? Which of the two names is the current official name for the road?

When editing names please make sure to select all affected segments to avoid name alternating forth and back.

Also if a road has several names then these should be preserved in alt_name/old_name or variants. Right now there are numerous segments that have both name and alt_name set to Open Canal Road while the name Daang Hari Extension was removed by your edits.

It appears that the wiki documention on this issue is a bit inconsistent. While the page for toll only explicitly mentions roads, the page for fee contains this statement:

"toll=* - to indicate that a road, bridge, ferry, or other way is tolled - that you must pay to use it. This key is used instead of fee=*."

According to taginfo there are 3300 occurrences of path + toll but only 1300 for path + fee. Even for footways toll is more commonly used with 1900 occurrences vs. 1600 for fee.

Considering a similar discussion on toll vs. fee for ferry routes (https://community.openstreetmap.org/t/toll-yes-or-fee-yes-for-ferry-routes/119341) it seems that mappers use both tags for different but overlapping purposes. Best way forward might be to improve wiki pages to document both use cases and propose verifiable criteria for differentiation.

Hi Totor. Is it possible that this bridge was added by mistake?

way/1456613967 ?

Here's recent ground-level imagery from this location:
https://www.mapillary.com/app/?lat=10.02742151014101&lng=123.42190968704995&z=19.510770631175262&focus=photo&pKey=1703469860632509

Hi and thanks for your awesome contributions to OSM!

I noticed that you added bicycle=no on several ways around here. Access tags in OSM are intended for legal restrictions.

If it is not forbidden to ride a mountain bike here then more suitable tagging would be to add details like smoothness or sac_scale to indicate how rough or difficult the trails are for bicycles.

Reverted in changeset/180381564

Haven't visited the peak of this particular hill. Where did you learn about this mine? Really interesting to learn how extensive mining activities around this area used to be in the past.

Good day. May I ask why you removed the toll=yes tag here?

All hikers, cyclists and motorbikes are required to pay a toll when using this trail.

It would be possible to map this scenario with conditional access tags.

Something along the lines of (just used random times for the example):
foot=no + foot:conditional=yes @ Su 05:00-12:00 + bicycle:conditional=yes @ Su 05:00-12:00 + motor_vehicle:conditional=no @ Su 05:00-12:00

Good morning. Just for clarification, this way is usable by bicycles but not for motorbikes? Thanks!

Good afternoon and welcome back!

Just some small reminders about tagging conventions:

- To map who or what a streets is named after please use name:etymology:wikidata/wikipedia. Only use wikidata/wikipedia on streets if the the streets itself has a wikidata object and wikipedia article (see: name:etymology=*)

- The main name tag should contain the name variant that is most commonly used on signage, for addresses and so on. Very long forms of a name that are only rarely used in everyday life are better suited for official_name tag

- Highway=unclassified despite its name is a a classification that is widely used for roads that are more important than residential streets but not important enough for tertiary classification (osm.wiki/Philippines/Mapping_conventions#Classifications)

Thanks for continuing to help improving OSM

Good day, welcome to OpenStreetMap and thanks for your edits!

Looks like you had some issues mapping this bridge closure. Bridges are often mapped as two separate objects, one for the bridge itself (way/1124403267) and one for the road (way/117836837) that goes across the bridge.

To indicate that the bridge is closed access tags (access=*) need to be added to the road.

I added access=no for now but if the bridge is still usable by pedestrians at the moment then this exception could be tagged with an additional foot=yes.

node/13605403143

Good afternoon. The point-of-interest that you added is already uploaded to OpenStreetMap. It doesn't need approval but other mappers can make changes and add more details.

I removed the promotional description and moved some of the information to start_date and contact:youtube. I also changed the category from amenity=events_venue to office=company as this seems to be more fitting and made some other minor tagging improvements.

Please kindly double-check if everything looks right and feel free to add more details or update data in the future.

Thanks for contribtuting to OSM!

Possibly this could be tagged as amenity=taxi + taxi_vehicle=auto_rickshaw (see: taxi_vehicle=*)