Explore the sources included alongside GLO field notes. Geographic indexes, township indexes and archive portals are different kinds of evidence; an index match does not establish scan alignment. MLRS and federal ROW searches run only when requested.
Map indexes are checked against published township geography where supported. A catalog entry is not automatically a geographic match, and a map image is not automatically aligned.
Geographic index — TopoView editions are discovered from the USGS spatial map catalog. Available GeoTIFFs and previews come from published map records; catalog limits and source availability can leave results partial.
Geographic index — Published georeferenced sheet and mosaic extents are compared with the township. An extent may include blank margins; the state-scoped catalog may not find a sheet indexed under a neighboring state.
Geographic index — Legacy quadrangle index records can match township geography and link to source GeoTIFFs. This is not a complete forest-map archive; no browser overlay or working PDF download is claimed.
Geographic index — The connected subset uses published transformed map masks to find geographic overlaps. When spatial discovery is unavailable, any catalog fallback is labeled as regional rather than a township match. Contributor georeferencing is not a survey-accuracy claim.
Geographic index — Geographic matches use published transformed masks and confirmed membership in the LOC railroad collection. A regional catalog fallback is not a township match; proposed as well as built railroads may appear.
Some connected archives return geographic project/map-index records; others publish township indexes or only a research portal. Those distinctions do not establish that a plan scan is georeferenced.
Archive / portal — Official project directories for PLSS states. These are project research links, not an exhaustive historical-plan archive or confirmed township matches.
Geographic index — Published project-centerline locations are compared with the township. A project location does not prove that a linked plan sheet covers that footprint; some records have no document link.
Geographic index — The connected index uses published ROW plan links and ROW polygons. It is an index match, not a verified georeferencing of the plan sheets.
Geographic index — Connected indexes cover as-built plans, ROW plats, and soils records, using the selected township or section geography. Some document links may lead to an external access page or request a MyWisconsin ID.
Township / section index — The public search is checked against the requested township/range and, where selected, published section numbers. Results are plan-folder index matches, not mapped sheet footprints; dates are not supplied.
Township / section index — The connected township/range index returns published map records and any file links present in the source row. This is not proof of scan alignment; unsupported township identifiers retain the archive link without a claimed match.
Archive / portal — A separate public archive with plan/project search fields but no published township, range, section, or polygon filter. Contract plans are not presented as township matches based on a related ROW map or place name.
Township / section index — The connected regional archive returns published township/range index entries across five libraries. It is not verified statewide coverage. Documents use session-bound archive controls, not shareable direct file links.
Geographic index — Published map-index extents and source PDF/ZIP links cover Alameda, Contra Costa, Marin, Napa, San Francisco, San Mateo, Santa Clara, Solano, and Sonoma counties only. Index geometry does not establish scan alignment.
Geographic index — Published ROW map footprints and available attachments cover San Diego and Imperial counties only. The district reports non-continuous digitized coverage; map dates and scan alignment are not inferred.
Archive / portal — Official records-office contacts for the remaining districts. District 4 and District 11 have their own limited map indexes above; no other district is represented as an automatic geographic lookup.
Archive / portal — Official statewide and district records contacts. A public historical-plan footprint index was not confirmed; this is a records-request link, not a township match.
Archive / portal — A published ROW parcel map and project/archive references. UDOT's ProjectWise archive links require credentials; this is not an anonymous historical-plan download or a township result.
Geographic index — Published highway ROW map indexes can match selected township or section geography and link to MnDOT eDOCS searches. These static maps stopped being updated in 2023; index footprints are not verified image overlays.
Manual-only search — GLO-Plot searches this source only after an explicit federal-ROW search request. Mapped case land descriptions are not surveyed ROW boundaries or plan scans; the records do not publish scan links.
Manual-only search — Case lands and mining claims are searched only when you explicitly request Search MLRS for a selected township/section. Published case geometry is not a map scan; document numbers are not download URLs.
Railroad evidence ranges from geographic map masks to state indexes and archival collections. Notebook collections are not represented as township hits.
Geographic index — Published RWMM indexes cover railroad maps, station plats, and historic railroad ROW plats. Available eDOCS links use source-published document IDs or search criteria; an index location does not establish an aligned overlay.
Archive / portal — NBMG provides a directory of georeferenced originals. A public map-footprint index for automatic township/section matching was not confirmed.
Archive / portal — Railroad valuation collections can include engineering and land field notes and acquisition schedules. No nationwide digitized notebook footprint index was confirmed.
Geographic index — See Historical maps for the connected, geographically indexed subset. The full collection is broader than the records with confirmed township overlap.
These sources can add monument history, hydrographic surveys, coastal sheets, and archival notebooks. Published mark locations are not automatically PLSS corners.
Geographic index — Published mark positions are filtered against the selected township or section boundary, with links to official PID datasheets. A mark is supplemental evidence, not necessarily a PLSS corner; the bounds service has a 500-mark response limit.
Geographic index — Published survey-footprint geometry is checked against the search area. NOAA survey pages may link descriptive reports, tidal documents, and other products; not every survey has every product.
Geographic index — Published coastal survey polygons or boundary lines can intersect the selected area. Open or clipped line matches are partial evidence, not complete sheet footprints; report availability varies and no scan alignment is inferred.
Archive / portal — Historical USGS archival holdings include field notebooks. No nationwide geographic notebook index was confirmed; browse the collection rather than treating it as a township match.