Correction: should have said “Hillside Centre”.

Correction: should have mentioned Highway 779

missed out this changes: extend CN double track to east of Carvel

Clarification: comment should have said “Kitchener, ON”

I didn’t select it, but appears to be just a problem with the app repeating previous deletion from another changesets. I cleared my cache, and the edits that caused the large bounding box are now gone.

Sorry for the large bounding box, but seems to be a problem with Go Map.

Then, you might want to bring up the issue with the nav provider (i.e. Mapnsoft), that navigation deactivates due to the change in classification. Are they also using OSM data as well?

Back again on the classification issue, why the QE2 has sections tagged as trunk and most motorway is because of the presence of intersections. Again, motorway is for any freeway (no intersections or property accesses, access only through interchanges) and trunk usually for core routes of the NHS that are not freeways (either expressways or ordinary highways).

That’s a bug with the car navigation system, and you should be careful with osm.wiki/Tagging_for_the_renderer . Maybe you better bring up that navigation issue with Genesis rather than fixing the data just to make the car nav work.

You may also look at osm.wiki/Canadian_tagging_guidelines to determine when a road is tagged motorway (freeway/controlled-access highway) or a trunk (important highway link that is not a freeway, usually an expressway/limited-access highway). If you’re having any questions, then why not bring that up on talk-ca: https://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-ca

You should better understand what a trunk and a motorway mean in the Canadian context. A motorway is usually used to tag a freeway (no property access and intersections, and access only through interchanges) and a trunk is usually used for a stretch of highway that isn’t a freeway but an important road link (usually as a expressway or an ordinary two-lane highway linking major cities).

In thia case, you’ve retagged sections of Highway 2 without taking in consideration the many intersections that make one of the highway’s segments fail motorway (freeway) status. Well, most of Highway 2 between Edmonton and Calgary is tagged motorway (freeway) following the usual criteria, but how is the classification messing up navigation?

In addition, having address using the common short names used in common speech that commonly drops stuff like suffixes (for brevity's sake) as against those posted in road or business signage, posters/ads, calling cards, documents, etc., looks weird, to be frank, except for the possible exceptions (like EDSA).

This has been discussed back in 2020 on talk-ph, but the talk to officially adopt use of full street names regardless of what official signs say (with possible exceptions, such as EDSA, STAR Tollway) seems to have stalled. I think we shouldn't set OSM Philippines apart in terms of road naming convention by saying unless it has "Ave.", "Blvd.", "Ln.", "Hwy.", and etc., Spanish "Calle" or "Avenida", Tagalog "Daan" or "Kalye", or Bisaya, Ilocano, or Kapampangan-language "Dalan", we drop "Street" either as implied, not posted or "redundant", and have data users think of it as implied.

Whether to keep or drop "Street" might be a personal thing this time, but I think we need to get things changed. I agree we should officially adopt the convention of using full road names (with some possible exceptions for easy recognition). Naming of places is a separate matter from the naming of roads.

Just noticed this lately, this edit removed a lot of street name suffixes I added (while keeping it on the others). I think we should move toward using full street names (official street name signs might drop them, but they are included in the name used in addresses)

[Lipa, Batangas] add/modify roads and POIs, tag bus stops

Bing: currently has aerials for Congressional under construction past Panteon. There is ongoing bridge construction to the Islands, but is still not on present aerial coverage.

I see this edit is done to fill a network gap created by the Daang Hari flyover (currently classified as primary), but I would better think all the stretches of road from Kawit to Dasma parallel to Aguinaldo are immer roads. I'll undo this plus and the classification of the flyover.

Just a note, please realign any imagery to existing GPX tracks (Bing and Maxar images for Batangas City area is offset).

Huh, primary? For national tertiary, depends on situation. I think it could've been correct Molino-Paliparan (and Bacoor Boulevard) are just secondary and Aguinaldo south of Tirona all the way to Tagaytay primary (as well as Tagaytay-Nasugbu and Naic-Ternate-Nasugbu), but that would be a drastic change unless CALAEX Kawit-Silang gets opened (eliminating redundancy). Aw, there 's too much secondaries around DBB, and the previous map was just the right thing. Secondary could have been applied to Congressional extension to The Islands instead to main road at St. Charbel, and dead-end secondary should've been fine (considering future extensions).

A week ago after a major edit around Laoang, but why restore them to trunk? Even with the construction of missing road link, it's still far from trunk status.

Those are mostly approximation from official sources. I've already marked part TR5 Lucena-Matnog (then QBX or QUEBEX) as proposed (pending notice to proceed for Lucena-Gumaca), but for TR4 Sto. Tomas - Lucena, agree they should be retagged as only the Taong section (around Villa Escudero) is being built.