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.

I forgot to mention, the 40 mph speed limits for NJ 21 came from Newark's 2024-11-07 Charter 23:13-1.b.4 Speed Limits Designated which states:

"Zone 2: 40 MPH between Miller Street and Murray Street."

I have validators enabled but I'm overwhelmed by the number of them in the area. I tried to fix as many as I could, but somehow that one slipped through. Thanks for catching it.

I'm still working on the area as I'm trying to figure out why OSRM has a poor route to the airport.

After failing to get a turn restriction sign added, I have readded the implicit turn restriction. I did not realize there was a tag for implicit and I believe your original changeset was correctly tagged and I was mistaken in my reversion.

I apologize for any inconvenience I have caused to your drivers in the last 3 months.

I must have dragged it accidentally when trying to navigate the map. I have moved it back. Thanks for catching that.

Howdy. I map nearby. I see you're adding some houses. Just thought you should know the proper way to add the addresses to building is not the name field, it's an address field with the number. The exact tag is addr:housenumber.

Thanks for catching my mistake.

OSM is intimidating in that there are a lot of tags and conventions that are slowly changing.

When flipping through backgrounds, you'll find they all have different offsets. If you're not sure what is correct, most people in the US align/offset the other aerials to Bing.

While your changes are public, there's actually very few people who will check your work unless you're mapping in area close to another person's. The number of daily mappers for Northern NJ can be counted on one hand with fingers to spare.

Lessons I learned the hard way...

1. Just cause it's on the map doesn't mean it's an approved way of doing things.

2. Don't glue/connect landuse to roads, go to the edge of roads. This is the most common mistake you'll see on the map that is very slowly being cleaned up.

You can join the discord or Reddit if you're not sure how to do something. Good chance you're not the first person to run into a problem.