If an old NYPL map embed fails, keep the map’s catalogue reference before looking for a replacement viewer. A discontinued interface and a missing historical source are different problems.

The NYPL Map Warper repository carries an April 2021 deprecation notice, reread 19 October 2026. It says NYPL updates would cease and embedded views would stop working after archiving, while contributions and data would be retained for future research. This article does not claim to have tested a functioning export or viewer.

Save the source identity first

• Map: catalogue identifier, title, creator and publication date where documented.
• Geography: the locality and sheet actually covering the question.
• Representation: original image, aligned derivative or later annotation.
• Research task: the street, feature or historical comparison you want to investigate.

These fields remain useful when asking a library about access. An embed URL alone may identify an interface without preserving enough information to find its source map.

What alignment changes

The repository describes placing corresponding control points on a reference map and historical image, then stretching the image to fit. That explains a transformation. It does not make every feature an exact survey or remove the original map’s date and production limits.

For a New York street-history question, select the actual mapped locality. NYPL holds material depicting many places; the institution’s New York address does not make every map a map of New York.

Keep later work distinguishable

Store a derivative separately from its source. Label newly added outlines or comments as editorial annotations, and keep a note of the alignment or transformation used. When an old view cannot be reproduced, describe that limitation rather than treating an untested workaround as a current tutorial.

Use the actual map record for a claim about one building or street. The repository supports the workflow history, not a present property condition or access-rights conclusion. More city-resource guides appear in our local-services archive.