Thanks! I've updated the road attributes accordingly and changed the old highway to secondary to indicate the decrease in importance.

Good day Schadow1. Thanks for updating this. Could you confirm if it is already fully paved/operational? Or are more works needed before it can replace the old Maharlika section as the preferred through-road?

Good morning. Thanks for mapping this college. I've changed the main tag from landuse=institutional to amenity=college and added some more details.

If a fee needs to be paid to use a road or to pass a gate you can use the tag toll=yes.

In this example, does everybody need to be pay the fee including residents of Tierra Benita? Or is this more of a bribe for the guard to let vehicles without sticker pass through?

By the way, is there a road connection at node/8318434630 ? On aerial imagery i looks like there is no proper connection, or maybe only passable on foot/bicycle.

I don't think we can. Any data from google is protected by a copyright that does not allow usage for improving OSM.

But it would be confirmation enough if you have visited the place in person or if you have local knowledge about it, no need to provide a public link as proof.

Thanks for adding this new road section! I made some improvments to the tags and the alignment.

The aerial imagery is still very outdated but on strava heatmap it is visible that this is quite a big road. Could you confirm if it's 4 lanes wide and concreted already?

Hey Joshua,

Are bicycles really prohibited from using this road, but motorcycles, cars and everyone else are allowed?

Or could it be that this tag was added based on rider feedback that the road is difficult to ride on due to very rough unpaved surface?

In this case maybe smoothness=very_bad would be more suitable? Then a routing algorithm for delivery riders could avoid it if possible, but routing would still work fine for someone planning a mountain bike ride.

Best regards,
Timmy

Hello Danny. Thanks for mapping so many street names in Mauban.

For place names like the one added in this changeset you can add a place=neighbourhood/quarter/village node instead of mapping it as a street name.

Did it already for Sitio 6: node/11405052187

PS: Please also make sure to always add the complete street names, no abbreviations and capital letters at the beginning of words ;)

Thanks for locating and restoring the old node. Duplicate is now deleted.

Good day and thank you for mapping the previously missing Gulf of Leyte.

It doesn't fit the OSM definition of place=sea though, same for the Surigao Strait. The tags natural=bay and natural=strait are sufficient.

Hello and welcome to OpenStreetMap.

Is Zenkids House really a shop that sells video games? Or is it maybe a gaming place / piso net? If the latter then you could change it to amenity=internet_cafe.

Hey Vince,

Due to the geographic isolation that comes with being an archipelago addr:country in the Philippines can be derived from boundaries with 100% accuracy. But I haven't considered the use case mentioned by you. I won't remove the tag anymore from now on.

Regarding addr:province, adding this tag seems to be standard practice in independent cities. While Baguio is administered independently isn't it still considered to be geographically located within Benguet? It is very common for official forms to have a mandatory field for province when asking for an address. What do you enter in those cases?

Moving on to addr:barangay, I'm not sure why this would be non-valid. It has been in local use much longer (since 2014) and has almost double the usage compared to addr:quarter. It is also used by more different mappers and it's more widespread geographically (25% of addr:quarter usage is in Baguio alone). On the data consumer side Nominatim treats both tags as equally valid and most other applications ignore both. Do you know any platform that only processes addr:quarter, but not addr:barangay?

But now to the practical side of things. Postal addresses are a topic entirely independent from OSM place tag assignment. Seav's LGU proposal is exclusively about the latter, he does not mention addresses at all. Just look at how addr:city is globally established for usage with whatever place name goes together with a postal code, regardless if it's mapped as place=city/town/village/suburb in OSM. Another example is how locally in the Philippines we use addr:province despite provinces being mapped as place=state.

Deviating from this practice of using a single tag for a specific address component leads to multiple problems and complications. To start with, only a small part of barangays (small to medium sized urban ones) are place=quarter in OSM. Most are tagged as village, fewer as suburb and some even as neighborhood, hamlet or town. It's also not unusual that mappers change place tags of a barangay without updating all addresses referring to that place. And it then gets even more confusing considering that quarter is also commonly used for large puroks, sitios and other non-administrative places encompassing several smaller neighbourhoods. Because of this a data consumer that wants to know the barangay of an address currently needs to make wild guesses wether it's found in addr:quarter, addr:village, addr:suburb or if it's missing altogether. And for mappers it's a mess too, many seem to just omit the barangay and only add addr:street/city/postcode.

Addr:barangay avoids all these issues by being very clear and unambiguous. An added advantage is that new mappers will immediately understand this tag and are therefore more likely to intuitively start using it.

I was actually wondering the same thing.

But given that survey was mentioned as the source I thought there'd probably be a sign or at least some local usage of the name.

Would anyone know what you're talking about if you'd suggest to meet up at the SM Mini Park?

Given that both variants are documented as equal I prefer the full url because it is better supported by some OSM applications.

For example on the OSM main website and also in GoMap!! urls in contact:facebook are direct links while there is no such integration for the shorter usernames.

In this and other changesets you've added the tag motor_vehicle=yes on a large number of gates.

In mapillary image from 2021 it is clearly visible that those gates are closed to traffic. Did you conduct a more recent survey where you found out that this is no longer the case?

Also, the current combination of access=no + motor_vehicle=yes means that cars/motorcycles are allowed to use these gates but pedestrians/bicycles are not. This seems quite unlikely. If the gates are really open now it would be better to modify the access=* tag than to additionally add motor_vehicle=*.

Good day Оксана1818, why did you remove the designation tag on this road?

Also please always mention which sources you use to make your edits (ground survey, local knowledge, imagery, database x, etc.) and please use better changeset comments (See: osm.wiki/Good_changeset_comments).

This part of the provincial boundary was very likely traced by hand purely based on guesswork (see history version 1 from 2014). It would be great if you could improve the alignment to be more accurate.

By the way, are you using any sources other than existing openstreetmap data when adding municipal boundaries? If yes please always mention them in your changesets.

In this case it seems that the actual boundary of Pigcawayan is somewhere in between the currently mapped provincial boundary and the municipal boundary you added. Have a look at the area around Panatan which is part of Sultan Kudarat municipality.

Boundaries of Barira will need to be revised too, there's currently a big overlap with Pigcawayan.

Thanks for your efforts!

I think it's better to use established tags over inventing a new one whenever possible.

Two different address components indicating a place smaller than a barangay are very commonly found in addresses here. Examples are subdivison + purok, sitio + purok etc.

For the specific example in this changeset a possible approach would be to move "Alabang" to addr:barangay (just as we're using addr:city for all municipalities/cities independently from their place tag in OSM).

Then addr:quarter can be used for "Filinvest City". This way the order of the address components is clear for data consumers (neighbourhood before quarter). A newly invented tag like addr:estate most likely would just be ignored by data consumers and even if they consider it, they'd have no idea in which part of the address it belongs.

Besides the fact that semicolon-separated values are well-established, using this tagging also improves likelihood of redundant wikidata elements being reviewed and fixed.

Some wikidata enthusiasts might regularly check all unusual wikidata tags in their area of interest but they wouldn't watch out for a undocumented wikidata:1 tag.

Btw in this specific case, wikidata entries have already been merged (thanks to seav) and wikidata tag in OSM is now updated too.

Good morning.

Due to urban place tag hierarchy (neighbourhood < quarter < suburb) place=quarter only seems to be suitable for very small barangays where puroks are the only level of named subdivisions.

In large barangays like those affected by this changeset place=quarter is already needed for puroks that encompass one or several smaller place=neighbourhood or by non-administrative named areas that encompass several puroks.

Some examples of this three level hierarchy are Capitol Homes in Purok Uraya in Brgy. Mankilam or Esmeralda Homes in Purok Malinawon in Brgy. La Filipina.