I stumbled upon this. Yes, the roads need work. I recommend you use the presets in JOSM for the road types. (Presents->Highways->Streets)

Here's some good rules of thumb for the smaller rural roads. If it has a street name, set it to residential.

If it doesn't have a name and goes to a building/property, set it to a driveway (set it to service and then you can change the service type to driveway).

If it looks like you need a 4x4 or offroad vehicle set it to track (Presents->Highway->Ways->Track).

If you really don't know, at least set it to a Road so at least people can drive on it. Presents->Highway->Streets->Road.

We can always reclassify roads in the future.

If you know the road is a private road, set the access=private tag. This prevents a lot of headaches for property owners.

I'm reverting your changeset to properly address the issue. Is a very common mistake to believe we only map public roads. I will be updating the roads with the correct tags to prevent navigational issue.

See here for the reasoning...
osm.wiki/Why_we_won%27t_delete_roads_on_private_property

osm.org/changeset/165741720

Hi. I'm the mappers who worked on the intersections that CurlingMan pointed out.

Anybody who has seen my mapping knows I am a massive fan of smooth curves....where they're appropriate.

The problem with the curves you made in the intersection is that they make some routes look beautiful at the cost of others looking unnecessarily bad. When traffic flows in both directions, the convention is to compromise and use straight lines instead.

But it's more than just an aesthetic choice.

The navigational routers often weigh how sharp a turn is in their best route calculations and may incorrectly rule out the best route if the angles they meet at are too sharp.

Also when an intersection point is too far off from the actual GPS position it'll have more issues with where to snap the vehicle to the road. This is mainly a problem with very wide intersections.

Those extra constraints is what I was trying to address when reworking them.

Forgot to include, addresses were taken from the Albemarle County GIS.

Note is wrong, it should be Note 4712548.

Thank you for bringing the ramp mistake to my attention, I have rectified it.

I'm aware you were having navigation issues with a nearby address, I'm sure routers where trying to incorrectly route through the alley instead of the driveway.

This was due to the driveway missing and some tags missing on the alley.

I have update the tags of this alley to be more consistent with the rest of OSM (while also trying to discourage routers from using it incorrectly. FYI, track is mostly just used on rural farmland plots.

Give it a few days (or a month) to take affect, if you still have navigation issues, reach out to me and I'll help you resolve them.

You're right. I've just been doing too much late night mapping. I have updated the tag.

Hi Jay, I see you've gotten into mapping. I have done a lot of mapping in the area as well (including this DMV).

These changes to DMV needs further work as the way you mapped it indicates that there are physical barriers between the lanes. This can end up confusing GPS systems as they might think you're in a lane that you're not and not realize you can still physically (although not legally) switch lanes.

So if you enjoy doing mapping there are two tags you should learn. The placement tag and the change tag.

osm.wiki/Key:change

The change lets you set the solid lines for the roads and is useful in a lot of situations like this.

Neither of these tags get visualized in the default web editor (Id) and honestly are easy to tag incorrectly without visualization, so most of us heavy mappers use JOSM with a plugin (Lane and Road attributes) to add and visualize them.

Let me know if you need any help.

Hello. We discussed this issue on the OSM discord. It falls into a grey area. Typically OSM doesn't like to close for construction unless the construction will take 6 months, but we also don't know the schedule.

This is cause items like GPS get updated infrequently and this area may continue to be avoided for years by them.

So as a compromise I had already updated the tags on the sections with the sinkhole to have a conditional tag stating no vehicle access for the next 2-4 months....which are just estimates based off news reports.

Of course this doesn't change any visual representation so it's easy to miss unless you literally know to go looking for it or watch the notes. Also most of the routers are ignoring this tag. GraphHopper was the only one respecting it.

I'm not saying what you did is wrong, knowing NJ construction schedules, it's probably right, all I ask you to do is monitor the two notes.

Is this the name of the track? I haven't seen a farm track with a name yet. The name may be better suited for the Owner tag.

osm.wiki/Key:owner

I noticed you placed some trees in the forest by I 287. While technically it's correct it gives the wrong impression of the area as have a sparse amount of trees, we have a landuse natural=wood which renders nicer.

Individual trees on grass is perfectly acceptable.

Based off the low edit count, I'm sure you were just learning the editor, but when you get a chance can you remove them and add the woods there instead?

Thanks. I haven't worked my way up to fix this area yet.

That relation should be fixed now.

I have addresses the original problem you were trying to solve in Changeset 162509470.

That section should now have correct turn lanes and destination per lane. If it continues to be a problem feel free to reach out and I'll help you resolve it.

Due to lack of a response, decided best course of action was to revert and apply the appropriate tags.

osm.org/changeset/162505727

Thanks for noticing. I check the notes a couple times a day. Quickly fixing notes is my way of encouraging people to contribute.

Hi. You are correct that map didn't have the destination mapped correctly, but the method you chose to fix is called splitting the ways.

Splitting the ways confuses navigation systems cause it implies you can't change lanes in that area. It also ends up being more maintenance in the long run. The rule of thumb is to only split when there is something physically preventing you.

It is a common mistake made by new mappers (I made it myself more times than I want to admit) because the web interface doesn't make the approved way obvious.

The approved way is to update tags per lane. See (Destinations Per Lane)

osm.wiki/Key:destination

Most people working on highways use the JOSM editor cause it has a better visualization for all the various tags which makes it easier to tell if they're tagged correctly.

To resolve the issue, the best option is to revert the changeset. If the previous version was mostly correct it can be faster and help preserve history of sections of roads. Then reapply the correct tags. (One tool is https://revert.monicz.dev/ and you just put in the changeset number)

The other option is to manually change it back. The downside to this approach in this case is if you delete the wrong road you lose the history of it.

Let me know if you want to learn how to do this yourself or if you would just like another mapper to resolve it for you.

Chipotle and Panda Express
https://www.mountolivetwpnj.org/media/11291

The Chipotle has hiring ads up and looks like it'll open very soon, Panda Express doesn't even have a sign up so maybe it changed.

External construction is done, I just left it to indicate they're not open and maybe they will have construction trucks parked there.

I drive by it about once a week, so I'm actively monitoring it.

Why did you add a cliff?

I stumbled upon your sidewalk while looking at a nearby note and I have to say I love the level of detail and care. It's so nice to see somebody put so much effort into something as mundane as a residential sidewalk. Keep up the good work.