You attached the historic=memorial to the subway tracks. I moved it to Arden Street.

Seems like attaching nodes to the wrong way is a very common pitfall in iD.

Please undelete the milestones. The milestones adjacent to the tracks (at least those I personally placed) are real physical objects located manually. clay_c also did a rough import of mileposts from FRA data.

I took a quick look and see that you've deleted these "NY" mileposts: MP 4 east of Secaucus, MP 6 at Portal Bridge and MP 8 near Sawtooth Bridges. MP 8 was deleted back in June. NY MP 8 is not to be confused with JC MP 8 next to Harrison. The latter is still there.

I was able to use this Overpass query (using the bounding box) to snapshot railway=milestone nodes as of January 1st, 2025. The query is so narrow that Overpass has no problem if you query the entirety of New Jersey or something even larger:
[out:json][timeout:25][date:"2025-01-01T00:00:00Z"];
nwr["railway"="milestone"]({{bbox}});
out body;
>;
out skel qt;

Let me know if you need help restoring these. iD may be insufficient.

This is a tough one. I'll try looking into it. My best guess is it should follow the railroad ROW.

can't edit any rail thing without seeing clay_c

The ETT was captured over several years:
https://web.archive.org/web/20190601000000*/https://www.acm.jhu.edu//~sthurmovik/movies/NEC_GO_301_1-18-10.pdf

I've re-uploaded it here for search engine visibility: https://archive.org/details/AMTK-NEC-employee-timetable-20100118-ssi

I request and/or collect NEC ETTs here: https://archive.org/details/@isstatenisland/lists/1/amtrak---northeast-corridor-employee-timetables?sort=-date

The west edge of the Times Square platform is only 4 feet off based on a rough trace I did from plans from the line extension. Great job.

The only reason this is marked is because it's traceable. railway=razed allows for otherwise demolished railways to be included through "secondary recognisable traces" even if it's just a linear pile of ballast.
railway=razed

Changed the name

Agreed. The address point should remain. Reverted in #146385430

"El." is short for elevated and it's nearly the same in Chicago parlance as "L".

It appears this was in fact spelled "L" with quotation marks: https://www.flickr.com/photos/127872292@N06/46583058612/in/album-72157652636620504/

Let me know if you think it should be "L" or "IRT Third Avenue Line" instead.

There are no Wikidata items for the various components of the Morris Canal. The few streets or other objects named after locks or planes have a more specific name:etymology but the same name:etymology:wikidata as you have noticed.

Consider the following:
"There is not always a 1-to-1 mapping between OSM and Wikidata. A Wikidata item may refer to several different OSM database objects, for example: a (boundary=administrative) municipality, place=neighborhood, place=city, and place=island might have the same name but be mapped differently in OSM. In this case consider splitting the Wikidata item (or ask for help if you are not sure how to do this).

Some Wikidata items represent features that are mapped as a series of several objects in OSM (e.g. long streets, streams). In such cases, the Wikidata item can be linked to from an appropriate OSM relation."

From what I understand, the tagging scheme I chose is not incorrect but could be improved with a hierarchy of new wikidata items for the several canal components.

Thank you so much for this. There are concrete pads for the new poles all over the upgrade zone from MP48.5 to MP55.7 (1100 feet east of CP Clark to HAM interlocking). Constant tension catenary poles are every 210 feet instead of the 1930s 270-300 foot interval. Check Bing over the next few years, I guess.

I should add they are physically marked with the respective name.

Perhaps. These are bridge "names" I see in the list of bridges regarded as properly marked (with the MP designation) in the ETT for the sake of determining bridge strike locations. As far as I understand, they're basically names. They're railroad bridges, so the railroad gets to name them I guess.

The reverted edit is not in vain.

In changeset #142009932 I added turnout 749A (Track 1 to Loop 1) because General Order No. 1001 (attached to Amtrak ETT December 5th, 2022) describes it:

> Track Loop 1 is extended 2,179 feet in length and placed into service ...

> Turnout No. 749A ... with movements from Line 1 to Loop 1 and... movements from Loop 1 to Line 1 has been placed in service.

Bing aerial imagery shows concrete ties where this new turnout was placed.

The transmission lines on top are Deans-Linden and Deans-Aldene. Both join/leave the NEC poles at the same spots.

The other ones (in groups of 2) are 25Hz lines for traction power. One day I'll make my way from the north checking/adding in information on the 25Hz system.

Correct; I just copied the setup of the bigger basin. I forgot I could just add a colinear way where the two basins meet.

It's fixed

Great edit; thank you. Maxar has shown to be the most accurate (but not necessarily the most recent) for this area.

node/2776282891 is now a Jenny Craig's but used to be McDonald's and the McDonald's website was still in the tags. This is a good example of peripheral problems with mechanical/mass edits.

That was a good laugh though.

A fantastic changeset

When you made the crosswalk across Broadway on the north side of 67th, you connected it to Track 3 on the subway. The terminal of the crosswalk happened to be near the way for the track.

This seems to be a common problem in the iD editor.

I've fixed it. changeset/124661305

Nope, but it will most likely mean demolition

I'll follow the case to see if the property gets seized (very likely)