Hello, what is the basis for classifying roads here? A lot of them seem over-classified to me and don't match the rest of the state's classifications on OSM.

Some overhead signs refer to the road as 'Independence Expressway' (such as along I 227 and Eastway Drive) while traditional street signs along the road call it 'Independence Boulevard' (the edit I reverted called this the "Independence Freeway", which I can't find any evidence of). Considering that properties along the road are addressed to Independence Boulevard, it looks like 'Boulevard' is the correct suffix here and that the Expressway name is just an alternative name.

Trunk tags aren't primarily based on the road's physical construction (e.g. lane counts, speed limit, whether the road is divided or not, etc.), rather how it's used in the network. Though Pottstown and West Chester are nowhere near as large as Allentown is, Route 100 serves as a very busy commuter corridor, seeing much more traffic over a long distance than other nearby primary routes, per AADT data. And while Route 100 is nowhere near as congested as 662 between Reading and Allentown—considering its an important enough route that an expressway was built along it through Pottstown and that its the most direct route linking commuters and long-distance travelers between Allentown and West Chester and past Philly—I think trunk classification here would still make sense.

Hello,

The road that you are tagging as primary here is not actually part of West Main Road and is just a frontage road for accessing properties addressed to W Main Road. It's not used by through traffic and should not be tagged as primary or any higher than residential/unclassified. Additionally, these ramps here should not be tagged as motorway links since the motorway itself (Route 24) terminates at them, and that little section of Route 114 isn't actually part of the freeway.

Hello,

What was the reason for removing the trunk route between West Chester, Pottstown, and Allentown here?

Hello, and welcome to OpenStreetMap. When mapping bike lanes, please instead use cycleway tags on the roads the lanes are a part of rather than mapping them separately. See here: cycleway=*#Dedicated_bicycle_lanes

Hello, I have reverted many of your most recent edits in Northwest Las Vegas for the following reasons:

- Features which do not yet exist should not be mapped, as this is misleading since they will show up on the map as currently existing features that can be visited and accessed by people. While things are under construction, they may be mapped with the proper construction tags. When construction is complete, they can then be tagged as any existing building/road/area would.

- Using the name=* key to describe an object's construction status or common object name (e.g. using 'proposed park') is incorrect usage of that key. A literal proposed park with the name "Proposed Park" would imply that it is actually called "Proposed Park". While something is under-construction, the official name of that soon-to-be-completed object can be displayed, but any information about the object being proposed or under-construction could be instead added under the note=* key which makes it visible to editors but not on the map.

- Also regarding incorrectly naming objects, the landowner's name should not be added to the landuse, especially undeveloped land. While the private individuals' names are public records, it is reasonable not to expect to see their names plastered on a map. Furthermore, adding a name to a physical object implies that that is the real world name. For example, if a piece of land is owned by Mike Jones, adding the owner's name to the object's name implies that the sand on the ground itself is named "Mike Jones". If the sand here was significant enough that it had its own name, then should the name be added.

This small stretch technically serves that purpose. It links Route 159 to Interstate 91 and eliminates a small gap in the primary route between the two highways. If you were traveling north on 91 and were heading to a nearby destination along 159, you would use this road.

Initially, I changed I 40 back to standard motorway tags in another edit for a couple reasons:

highway=construction tags should only be used on roads that are actually under construction and do not yet exist (i.e. I 40 is being built here rather than closed for damages).

The second reason would be that road closures are only typically specified if they're permanent or will last multiple years. This is due to it taking usually taking long periods of various lengths for many of the third party maps and routing systems that use OSM's data to actually identify or render that the data has been updated. However, this may not actually be too big of an issue since I 40's closure seems to be more indefinite than from what I had previously gathered.

Just now, I've added access=no tags between exits 440 and 20 per the map you linked. There may be a better way to specify a temporary closure due to damages from weather or if there's a confirmed opening date. However, I'd probably remove the access=no tags if a reopening is in the near future, like within a few months, but that seems unlikely currently.

Hello,

I have noticed that you have incorrectly changed a lot of residential streets to living streets. Do you have a reasoning for this?

Actual 'living streets' are very rare in the United States and are more of a European concept. This could be best described as small/short alley or driveway-like road that doubles as a pedestrian street, typically paved with bricks and has a low speed limit (like 5 mph), and is located in a more urbanized area. A road that prioritizes cars, like one paved with asphalt, has a driveway for each house, and has a 15 to 25 mph speed limit would not qualify as a living street.

I also noticed that you have changed the service roads in a nearby shopping center to tertiary roads. A tertiary road is is typically what you would call a collector road in the US. An example of this would be Palmetto Road, which sees more traffic than the residential streets which spur off of it, and it provides access between more major roads and destinations like commercial areas. The correct tags for the service roads you changed to tertiary here would still be service roads.

Hello and thank you for your edits.

When mapping buildings, polygon should match the exact shape of the building that it is placed on and should not be a random shape. The vast majority of the houses you mapped here are simple square shapes which aren't angled correctly with the building they're representing, and some of them are even triangular or trapezoidal in shape. If in the future you plan to map more houses and/or correct these previous edits you've made, the best way to map buildings is by carefully tracing the area of the building—making sure you have every angle of the building traced—and then pressing 'Q' on your keyboard to even it out into a clean shape.

Alternatively, there is the Rapid Editor (https://rapideditor.org/rapid). This allows you quickly add houses to the map more accurately than just spamming polygons and more quickly than painstakingly adding each building shape, however it isn't the most accurate.

The main issue is that it is incorrect. Just because tagging it incorrectly won't cause any major navigation issues doesn't mean it's not correct. I could tag all of there warehouses here as supermarkets and they would still appear on the map and can be accessed by routing systems, but that doesn't mean they would not be incorrect.

It should not be a trunk road because it, by US definition, does not serve as one. In a suburban area like this, a trunk road is defined by the OSM Wiki as "the most important non-motorway roads that provide main, long-haul connections between population centers of regional importance". This here is a simple connector road between an Interstate and a relatively minor arterial road. It still does not make sense to me why such a short access road should be placed higher in the hierarchy than the road it leads to.

Tagging roads as different "colors" just to specify pedestrian access rather than for how they serve in the highway network would be tagging for the renderer. (osm.wiki/Tagging_for_the_renderer) I explained how to properly specify pedestrian access here without changing the tags of the road itself.

It depends on the OSM-based routing system, which there are many of, but I know for certain the best way to specify pedestrian access and ensure proper navigation is to map all walkways along the route and to apply tags like foot=yes, foot=no, foot=discouraged to specify pedestrian access. This is specification is even more important now since highway=trunk, which used to almost always refer to an expressway or boulevard, can now refer to any sort of segment of highway part of a major commuter or intercity route (i.e., a route as important as a motorway that may not meet motorway criteria for various reasons), including surface streets. With this change in direction for the tag, the road's color no longer solely reflects the highway's physical characteristics.

Hello,

Very short routes like this one, which only connects a motorway to a primary route, should not be classified as trunk. If there were a route as significant as a trunk route in place of MA 125, a trunk route would make sense here, but instead it should be primary since it only terminates at another primary route. We also should refrain from classifying roads based on the physical characteristics and rather based on the role they play in the road network. Physical characteristics are already implied with speed limit, lane count, and expressway tags.

Hello, I have reverted this section of Briley Parkway that you have upgraded to motorway back to trunk. The motorway tags should only be used on freeways like Interstates or the remainder of Briley Parkway which is up to freeway standards.

changeset/157316163

Hello. Streets, especially ones with street names, sidewalks, and access to other streets/alleys/driveways, should not be tagged as trunk links as you've done with segments of Berkeley and Clarendon Street and Charlesgate. Highway link tags should only be applied to highway ramps and slipways.

I suppose you could start a thread there.

This would meet motorway criteria in the US as a motorway island. It's about 6 miles long and has at least two interchanges along its route.

osm.wiki/United_States/2021_Highway_Classification_Guidance#Exceptions_and_Borderline_Cases

Hello, I don't think this section of Southern Parkway should have been downgraded to trunk. It's built up to freeway standards with full access control (at least east of the I 15 interchange, divided carriageways, and a high speed limit.

It looks like the entire project will be going for another two years, but in multiple phases that have subphases with closures of sections of Main Street that will last no more than a few of months each. This is considered "short-term" on the highway=construction tag documentation page (highway=construction).

I think the better way of going about this, if we want to avoid the problems cause by moving the highway=construction tags around the street every handful of months, would be to use access=* tags. This requires the effort of tagging each phase correctly, though. I think many people would agree, however, to leave it as primary since road closures like these are more subject to conditions than a project like rebuilding a bridge or paving a new road—but I think it may be better to have which sections are closed properly indicated.