USA Continental Divide not Completed in New Mexico, Topo map does not have Divide shown

Notice Continental Divide not finished in New Mexico. I am using ID editor and the USGS Topo map is stiched together maps from different sources and when one source lists the Continental Divide as a dashed line, it moves into a different Topo map and not more line, so I cannot continue my work (N36° 36’ 45.2" W107° 00’ 01.7")
Is there a diiferent Topo Map that shows the Divide continuing South? I can’t find any GPX file for the Divide. Noticed many sections do not have a DIVIDE RELATION listed.

The CalTopo layer is a curated mosaic of topo maps, stitching together various series and vintages inconsistently. USGS topoView has a more comprehensive selection of any series that was ever published for a given area. Esri publishes a FeatureServer of this imagery that you can use in iD or JOSM.

A couple of years ago I found continental divide data (shp or gpx?) on some official US web site.

There’s this one, but it doesn’t look very good

This looks better

https://www.arcgis.com/home/webmap/viewer.html?webmap=2c786babdaa34c93b7f9d37e82ba4748

if you can figure out how to download the data.

Possibly here: https://www.usgs.gov/national-hydrography/access-national-hydrography-products

1 Like

You can use the watershed boundaries from NHD to align the Continental Divide. As with other NHD data, you need to be cautious about the exact placement, but the sections where I looked at the NHD data for this it was pretty good.

The 3DEP topo lines can sometimes be helpful in confirming the placement of the divide, but if you’re comparing NHD data to 3DEP, you have to be careful in considering cases where the exact placement of the divide does not go all the way up to a local summit because the hill slopes drain in the other direction.

1 Like

How do I use the NHD/USGS TopoView in ID editor? I have pasted custom URL in the “custom” layer before.

You can’t use it directly, but Esri has published a mirror of the imagery with a full WMS ImageServer. Unlike most ImageServers, it’s time-enabled, so tools like the OSMUS proxy would require additional fiddling. I posted instructions for constructing a custom URL template based on the exportImage endpoint that you should be able to enter into either iD or JOSM. Note that iD has a bug where you need to set the URL before switching to the custom layer, or you can restart iD and switch to it.