What do you mean by "no restriction"? In this changeset, you removed a way from the Northlake suburb relation. The way that you removed from the relation appears to be a suburb line for Northlake, Charlotte, NC.

The Sycamore Street Northeast way tagged with "lanes=4" that you merged with the other way of the same name in this changeset has been restored in changeset/174623996. For future reference, see these OSM Wiki articles on lanes and turn lanes tagging:
lanes=*
turn=*#Indicated_turns_by_lane
turn=*

An FYI, you don't need to delete existing landuse or multipolygons if they reflect what is actually seen on the ground, and then redrawing them anew. It's better to leave them on the map and adjust their geometry. In this changeset, you deleted a school multipolygon and then redrew the school area. The school multipolygon that you deleted was valid and actually reflected the Christiansburg High School area in aerial imagery. It would have been better to leave the school multipolygon on the map and update its geometry or add/change tags if necessary.

You also deleted a residential multipolygon in this changeset. The residential multipolygon that you deleted actually reflected the residential area(s) seen in aerial imagery. The residential multipolygon didn't have to be deleted. You just have to adjust their geometry by adding nodes to the multipolygon or moving their nodes.

Make sure to help preserve the history on OSM by modifying existing elements instead of deleting them and redrawing them from scratch. Per the OSM Wiki, it states:

"When things change in the real world, be bold, and edit the map to reflect the current situation. But be aware that OpenStreetMap can store the editing history of an element. You can help preserve this history by modifying the existing elements instead of deleting them and redrawing from scratch."
osm.wiki/Good_practice#Keep_the_history

And also, "Be brave in what you add but careful in what you delete." i.e., not removing valid, in-scope detail from the map.
osm.wiki/Good_practice#Don't_remove_objects_that_you_don't_need_or_like

Just to follow up, you can read this OSM Wiki article about keeping the history: osm.wiki/Keep_the_history, so this is brought to your attention to keep in mind for the future.
When things change in the real world, make sure to be bold and edit the map to reflect the current situation. OSM stores the editing history of an element, so it's worth taking a few steps to preserve the history. Per the wiki, it states:
"When things change in the real world, be bold, and edit the map to reflect the current situation. But be aware that OpenStreetMap can store the editing history of an element. It can be worth taking a few extra steps to help preserve this history."

Instead of deleting elements such as roads, buildings, or landuse and redrawing them, it's better to update the geometry of the existing objects, which retains their editing history. You don't need to delete existing roads or parking areas on the map and redraw them. Just update their geometry. Per the wiki, it states:
"Instead of deleting elements such as buildings or landuse and redrawing them anew, it is generally better to update the geometry of the existing objects, retaining their editing history. Similarly, make sure to preserve the identity of an element even when its tags become different" (but don't overdo it).

You can learn more about the placement of the OSM-way in this OSM Wiki article so this is brought to your attention to keep in mind for the future: osm.wiki/Proposal:Placement

Just FYI, be aware of the placement tag on Peppers Ferry Road Northwest ways 501233850, 501233849, and 1124508685. way/1124508685 (way/1124508685) has the tag "placement=left_of:3", and ways 501233849 (way/501233849) and 501233850 (way/501233850) have the tag "placement=left_of:4". The "placement=*" tag specifies the placement of the way relative to the road it represents. This can be seen on roads with more than one lane where the OSM-way is not drawn in the middle of the road, or where the number of lanes changes. For example, if a way is tagged with "placement=left_of:3", then the way is located to the left of lane 3. "3" indicates either the rightmost lane if the road is 3 lanes wide, or 2 lanes to the right from the left most lane. "1" indicates the leftmost lane on a multi-lane road and the number increases going to the rightmost lane.

In this situation, for the 4 lane section of eastbound Peppers Ferry Road Northwest (VA 114) coming up to North Franklin Street, you moved the 2 Peppers Ferry Road Northwest ways tagged with "placement=left_of:4" from the left-hand side of lane 4 (the rightmost lane) to the center of the road between lanes 2 and 3 (between the turn lanes and the main lanes). It is not always possible to draw the OSM way in the middle of the road in every situation, especially if roads join or fork, or the number of lanes changes. Every situation is different. In the OSM Wiki article on the placement of the OSM-way, it states:

>"Why not simply draw the OSM-way always in the middle of the road?"
>>"Because it is not possible in every situation, especially if roads join/fork or the number of lanes changes. Imagine two roads which join: how would you draw the OSM-way around the point where the roads join?"
osm.wiki/Proposal:Placement

For this situation, on the 4-lane section of eastbound Peppers Ferry Road Northwest coming up to North Franklin Street, it would've made sense to leave the ways on the left of lane 4, since the two left turn lanes begin on the left-hand side of the eastbound carriageway, the two left turn lanes turn left onto North Franklin Street and the right 2 lanes (the main lanes) continue straight on Peppers Ferry Road in a straight line. So it would make sense to leave the Peppers Ferry Road Northwest ways in the middle of the main lanes (between lanes 3 and 4).

Is there a reason you tagged way/845861056, formerly part of the Northlake suburb relation, as a primary road? I can see it overlapping the I-485 inner on-ramp at the West W T Harris Boulevard interchange, I-485, the I-485 Inner to I-77 ramp, Statesville Road (US 21), and Lakeview Road. I can also see the way crossing I-77 at the I-77/I-485 interchange. way/845861056

I checked the version history of the Northlake suburb relation and found that way/845861056, which is what you tagged as a primary road, was part of the suburb relation, as seen in versions 1 and 2 of the suburb relation (Well, the way wasn't tagged as a primary road back then). relation/12345455

I can also see that in changeset/173291613, you removed way/845861056 from the Northlake suburb relation, as seen in FacilMap here: https://facilmap.org/#q=changeset%20173291613
changeset/173291613

Hi CAM-Gerlach, the yield sign is still there. It was not removed recently. It's just that you added another yield sign right next to the one I added over 2 years ago. This changeset's comment states that I removed the "extra yield sign" since I already mapped a yield sign here over 2 years ago and you mapped an extra yield sign on this same spot almost 3 months ago in August. In case you didn't see there was already a yield sign mapped here right before you mapped another one on the same spot, here's the yield sign node I added on the off-ramp exiting onto Prices Fork Road: node/10596461442

It looks like I can spot the shadow of the yield sign in the VBMP imagery and can confirm the yield sign is located right before the street lamp post at the point where the US 460 westbound off-ramp meets Prices Fork Road (as seen on Bing Streetside imagery).

An update that the URL in the source tag is no longer incorrect as it no longer includes ";streetlevel imagery" in the URL. When I created this changeset, the URL in the source tag previously included ";streetlevel imagery" in the URL, causing it to be incorrect.

The latest TTT route map and schedule can be found here: http://www.bt4uclassic.org/schedules/TTT.pdf

I did not remove Industrial Park Road, the VT CRC roads (Research Center/Kraft/Pratt Drive), Southgate Drive, Beamer Way, Washington Street, Kent Street, and Alumni Mall from the Smart Way Bus (SW) route relation because doing so would take a lot of time.

Smart Way Bus no longer services the Virginia Tech Corporate Research Center as of 1/9/2025. The latest Smart Way map can be found on https://www.valleymetro.com/services/smart-way-services

Hello iismitch55, I noticed that you merged a section of Sycamore Street Northeast tagged with "lanes=4" (way/1149741764) next to North Franklin Street and Spradlin Farm Drive with another Sycamore Street Northeast way tagged with "lanes=2" (way/20360745), resulting in you creating a single Sycamore Street Way from Laurel Street to North Franklin Street tagged with "lanes=2". You can clearly see in the aerial imagery that the short section of Sycamore Street Northeast next to the North Franklin Street/Sycamore Street/Spradlin Farm Drive intersection is 4 lanes (one lane going out of the intersection and 3 lanes going into the intersection). I can also tell by local knowledge of this area. You should have left the Sycamore Street Northeast way tagged with "lanes=4", "lanes:backward=1", "lanes:forward=3", and "turn:lanes:forward=left|left;through|right" (way/1149741764) that you merged with the other Sycamore Street Northeast way (way/20360745) on the map.

Also, I noticed that you deleted some parking areas and parking aisles in this changeset and redrew them. I don't think that you need to delete parking aisles and parking areas and then redraw them. You just have to adjust existing parking aisles and parking areas on the map by adding/deleting and moving nodes on the way or area. I looked at some of your map edits in this same area and saw that you did the same thing, deleting parking aisles and parking areas and then redrawing them on the map. I don't think you need to delete a few parking areas next to each other in the same place and then redraw the parking area to cover the entire parking area (if that's true with parking spaces designated for different uses, purposes, or groups of users, such as faculty/staff parking, visitor parking, parking for different types of vehicles, parking spaces for different types of parking permits, etc.). You can just leave the parking areas on the map and adjust them to align with those seen in aerial imagery. You can also use different tags for different types of parking, such as "access=public", "access=private", "access=customers", "access=permissive", or "access=permit", and to specify who is allowed to park there, use the "private=" tag. Link for values to use for "private=": private=*

I don't think you need to merge a few parking aisle ways connected to each other on the map and merge them into one. I think it's best to just leave them as it is and adjust them if necessary.

Correction: Changeset comment should have said "Added track speed limits on NS Blue Ridge District from Bedford to Lynchburg".

The link in the source tag no longer works now. Here is an archived snapshot of the link on the Wayback Machine: https://web.archive.org/web/20230517223133/https://www.virginiadot.org/business/resources/APD_Docs/Tech_Proposals/93074_-_Technical_Proposal_-_Orders.pdf

See osm.wiki/Keep_the_history

This changeset has been partially reverted by changeset/153012699 for a deleted node. changeset/153012699

It's unknown if user eschaper1 is still alive today. That user did not explain why he/she dragged this power pole node. Anyways, the dragged power pole node has been reverted.

This changeset has been reverted in changeset/135555604. See changeset/135555604

It's unknown if user eschaper1 is still alive today. That user did not explain why he/she dragged this power pole node. Anyways, the dragged power pole node been reverted.

Linked blocks:
osm.org/user_blocks/6752
osm.org/user_blocks/6994
osm.org/user_blocks/7012
osm.org/user_blocks/7034
osm.org/user_blocks/7051