I bumped it down to a school building.

My reasoning is if somebody was using OSM in the event of an emergency, we probably wouldn't want to route them to the CCM building (although there's worst places to route them).

When you start trying to categorize everything on the planet you'll find all sorts of grey areas. The tags are set up from generic to specific, so when we have doubts we tend to make it more generic.

Since you asked for a review, I looked over it.

Overall not bad. Remember to hit Q on buildings to square them up (I did it for you). Also the convention is to add +1 in front of phone numbers. Neither are big issues.

I don't know if CCM Public Safety qualifies as police or just a school building. Would a civilian be ok going there in the case of emergency?

Thanks for updating OSM. Feel free to hit me up with questions as I'm currently the most active mapper in the area.

I reviewed it. Nothing really was wrong with it, but since I was looking at it, I updated the Jersey Johnny's building layout slightly, added the opening hours, phone number and some more food specialties. I updated the city to reflect the one on the website.

Construction area looks good.

Did you forget to include '"mph" on a section of Horace Harding Expressway?

TIGER stands for Topologically Integrated Geographic Encoding and Referencing system. Most of the US roads were imported and not hand drawn by OSM mappers. The extra tags were left over from the import. People use the reviewed tag to find roads that have not been reviewed. Adding lane counts, surface and aligning them the aerials is enough to remove the tag.

name_1 is old and should be replaced with alt_name. You can add multiple alternative name values by separating them by a semi colon (;). There's also old_name for when a street is renamed and official_name which I only use for otherwise unnamed ramps.

Tiger tags are also no longer used, although the only one I routinely delete is the reviewed one.

Stuff like this is what makes mapping challenging. You can use plot addresses and the NJ Arcgis Centerline as tie breakers.

Nice source. You'll notice that in the PDF under "Rules of the Trails" that Motor Vehicle/ Dirt Bikes/ATVs / Horses are prohibited. There are access tags that you can add to trails to indicate they are prohibited and dogs are leashes are allowed. A lot of the features have assumed defaults, but it doesn't hurt to tag they're not allowed as it indicates something explicitly stated they're not allowed. (You only need to tag the ones that it mentions).

There's also an opening_hours that can be set to "sunrise-sunset".

There's an "alcohol = no" tag

There's also operator tag to indicator who maintains them, there's even operator:phone number so you can put in who to contact about the trail!

None of these are absolutely required to do, but the more information you can transfer from the PDF the more useful OSM becomes as people can easily search for trails that meet their requirements.

No trespassing trails should not be removed. They should just have the access=private tag added to them.

These are the kind of things that I love seeing on the map.

Nice work on the on ramp.

Sorry about that, I was asked to help map some farmland in Russia. I didn't realize I had some unchecked in work in the US.

Just a heads up, most houses in the US can be tagged as detached houses. It's a slightly more specific tag.

We understand your frustration. OSM runs into this issue routinely.

Service road is just a classification OSM uses. Driveways are considered a subset service roads.

This driveway has been tagged "private" to both vehicles and pedestrians, which means any routing engine will not use it.

Everything was tagged correctly, and removing correctly tagged features is considered vandalism which is why the change has been reverted.

Anybody making the mistake likely is not using OSM or should be reported to program using OSM data cause their program has serious bugs.

I have mapped the woods around the property to help people realize they can't drive/walk through the area.

At least one person noticed them. Please keep adding more to the map! I love these kind of details.

Why are all your changeset descriptions single periods?

How did Lyft find such a minor change so fast? Does Lyft have an automated GPS trace to compare against the map for differences? Do drivers report errors? AI analysis? Random spot check?

Not bad. I just think you need to add turn restrictions where the one ways join to prevent u-turns.

I got back from surveying it. The gate is indeed locked with a 4 digit code. The front of the gate sign says "Road Closed - Authorized Vehicles Only". It does feels like the sign is on the wrong side cause the rode is not closed on the other side.

Another gate just North of to it has a sign nearby that says "Wetland Mitigation Site". I suspect what happened is the that the surrounding industrial companies were dumping near a protected wetlands, so they closed the road and added a gate and camera.

They also have painted lane lines on both sides of the gate / turning circle

Because it is locked, I think the best compromise is to bump it down to a tertiary, which I have done.

It's gated, so it's not necessarily a dead end road.

It's named for linking Flanders to the South and Netcong to the North. But it also on a census line for Budd Lake / Flanders. The speed limit (40 mph) is consistent with the other secondaries in the area (primary on US 46 is just 45 mph, and US 206 is 50 mph), I only marked it that way cause I haven't confirmed if they repainted the lines.

So it's definitely not a residential road, it's at a minimum a tertiary road.

I did confirm the entire road is public and I'm actively working on the speed limits in that area. The next time I'm in the area during the day I'll see what the gate is about because I am pretty sure I misstagged it's access.

Glad you updated them, the power infrastructure is somewhat of a mystery to me.