# N05_E18 Great Lakes pilot: 1673–2026 hydrologic and Indigenous-history crosswalk **Research date:** 2026-08-09 UTC **Sector:** `N05_E18` **Canonical geometry:** 24 latitude bands × 24 longitude bands = 576 sectors; the cell spans 37.5°–45.0° N and 75°–90° W. This note does not redefine the cell. **Pilot position:** Great Lakes nine-sector octagon centered on the N05_E18 working anchor at Merrillville, Indiana. **Selected next unresolved path:** The prior N05_E18 notes repeatedly identified the need for older 1800–1950 drainage, portage, Indigenous/primary historical, and hydrologic crosswalk evidence. This run therefore adds a bounded historical source from the 1673–1830s transition and a modern machine-readable USGS hydrologic network crosswalk at the working anchor. It does not duplicate the existing 1834–2022 transport extracts or the prior modern station-result work. ## Research question What can be documented, without converting a local historical narrative into a cell-wide cultural or infrastructure score, about the pre-industrial transport and Indigenous-contact setting around the southern Lake Michigan–Kankakee–Calumet corridor, and how does the modern anchor relate to a reproducible hydrologic network and nearby monitored sites? ## Search envelope - **Historical place names and features:** Porter County, Lake County, Calumet River, Kankakee River, Lake Michigan, Fort Dearborn, Bailly Town, Detroit–Fort Dearborn road, St. Joseph mission route, Pottawatomie/Potawatomi, Miami, Fox, and Pontiac. - **Modern anchor:** Merrillville, Indiana, approximately 41.4828° N, 87.3327° W. - **Target variables:** water and drainage connectivity; canoe/portage and road connectivity; historical institutional and Indigenous-contact context; modern watershed/reach relation; nearby monitoring-site discovery. - **Target bands:** `1500-1800`, `1800-1950`, and `2000-present`. ## Raw observations ### A. Archive.org historical source metadata ```json { "sector_id": "N05_E18", "period_id": "1500-1800", "variable": "historical_institutional_profile", "subvariable": "early_contact_and_transport_context", "value": "A retrospective county history reports French missionary and explorer movement through the Kankakee/Lake Michigan region in the 1670s, later French and British trade, Pottawatomies in the regional political-military narrative, and a 1759 British transition.", "value_type": "reported_historical_narrative", "date_start": "1673", "date_end": "1759", "geographic_scope": "Porter County and connected Kankakee/Lake Michigan/St. Joseph routes; broader than one fixed cell", "comparability": "qualitative_only", "source_tier": "C", "source": { "repository": "Internet Archive", "identifier": "cu31924104606235", "file": "cu31924104606235_djvu.txt and scanned page images", "page_or_image": "printed pp. 14-15; scan leaves 17-18", "title": "Counties of Porter and Lake, Indiana : historical and biographical", "creator": "Weston Arthur Goodspeed and Charles Blanchard", "publication_date": "1882", "url": "https://archive.org/details/cu31924104606235" }, "extraction_method": "OCR locator checked against scan images", "source_language_or_bias": "late-nineteenth-century county-history retrospective; uses colonial and settler-centered terminology and should not be treated as an Indigenous-authored account", "confidence": "medium", "notes": "The source reports contact and movement; it does not provide a complete Indigenous political, demographic, land-use, or ecological record." } ``` The scan image for printed p. 14 describes French expeditions and later French/British activity in the region, including a statement about Pottawatomies in the 1763 St. Joseph episode. The scan image for printed p. 15 describes the 1803 Fort Dearborn expedition, regional travel routes, and trading figures. These page-level summaries were checked against the scan rather than relying on OCR alone. ### B. Archive.org historical hydrology and settlement context ```json { "sector_id": "N05_E18", "period_id": "1800-1950", "variable": "water_profile", "subvariable": "river_lake_portage_setting", "value": "The 1882 county history describes the Calumet River flowing westward through the northern part of Porter County, the Kankakee and Lake Michigan setting, canoe transport, and a 1831 road between Detroit and Fort Dearborn; it also describes Bailly Town as a trade and gathering center in 1822.", "value_type": "qualitative_observation", "date_start": "1803", "date_end": "1831", "geographic_scope": "Porter County, Bailly Town, Fort Dearborn, Calumet/Kankakee corridor; crosses local boundaries and is not a cell average", "comparability": "related_not_equivalent", "source_tier": "C", "source": { "repository": "Internet Archive", "identifier": "cu31924104606235", "file": "scanned page images and cu31924104606235_djvu.txt", "page_or_image": "printed pp. 12, 15-16, 20; scan leaves 15, 18-19, 23", "title": "Counties of Porter and Lake, Indiana : historical and biographical", "creator": "Weston Arthur Goodspeed and Charles Blanchard", "publication_date": "1882", "url": "https://archive.org/details/cu31924104606235" }, "extraction_method": "OCR locator checked against scan images", "source_language_or_bias": "retrospective local history; statements about Indigenous movement and removal are filtered through nineteenth-century settler narration", "confidence": "medium", "notes": "The account is useful for dated route and place-name leads. It does not establish transport volume, population, land-use intensity, or causal effects." } ``` The same source’s printed p. 12 describes the Calumet River, Kankakee, Lake Michigan, and local lakes in a geological/topographic chapter. Printed p. 16 describes the 1812 Fort Dearborn episode, Joseph Bailly’s 1822 settlement and trade with Native people, and the 1831 Detroit–Fort Dearborn road. Printed p. 20 describes Bailly Town as a gathering, trade, and religious center and notes the departure of Indians to western reservations. The latter is a source claim and a record of removal-era narration, not an independent estimate of population or a complete Indigenous history. ### C. Modern USGS NLDI position and reach crosswalk A direct request to the USGS Network Linked Data Index at the Merrillville anchor returned a GeoJSON flowline/catchment result: - Query point: `POINT(-87.3327 41.4828)`. - `comid` position result: `3399712`. - Hydrolocation snapped point: approximately `(-87.3339374, 41.4824398)`, reachcode `04040001000480`, measure `10.8735`. - NLDI basin response: one polygon feature for the catchment associated with `comid 3399712`; returned geometry contains 27 coordinate vertices. The returned polygon is a local catchment, not the full N05_E18 cell or the Great Lakes basin. Source URL templates used: - `https://api.water.usgs.gov/nldi/linked-data/comid/position?coords=POINT(-87.3327%2041.4828)` - `https://api.water.usgs.gov/nldi/linked-data/hydrolocation?coords=POINT(-87.3327%2041.4828)` - `https://api.water.usgs.gov/nldi/linked-data/comid/3399712/basin` This is a machine-readable modern network crosswalk, not a measured discharge, water-quality value, or historical reconstruction. ### D. Modern USGS NLDI linked monitoring-site discovery The NLDI upstream/downstream discovery responses returned nearby Water Quality Portal and NWIS-linked features. Examples include: | Direction / source | Identifier | Reported coordinates | Reported name or type | Interpretation | |---|---|---:|---|---| | Upstream WQP | `INSTOR_WQX-17399` | -87.3388016, 41.4850204 | `LMG-05-0045` | Nearby WQP site; point location, not a cell aggregate | | Upstream WQP | `INSTOR_WQX-8390` | -87.3247222, 41.4669444 | `LMG030-0016` | Nearby WQP site; point location, not a cell aggregate | | Upstream WQP | `USGS-412857087201001` | -87.3361473, 41.4825365 | NWIS/WQP site | Nearby site; separate record lineage must be checked before use | | Downstream NWIS | `USGS-04092975` | -87.3358889, 41.5044722 | Turkey Creek at SR 53 at Merrillville | Nearby NWIS surface-water site | | Downstream NWIS | `USGS-04092977` | -87.32375, 41.50744444 | Turkey Creek at 61st Av at Merrillville | Nearby NWIS surface-water site | | Downstream NWIS | `USGS-04092990` | -87.2583688, 41.53475918 | Lake George at Hobart | Connected nearby water feature | | Downstream NWIS | `USGS-04093000` | -87.25697989, 41.53614807 | Deep River at Lake George outlet | Connected downstream site | | Downstream WQP | `INSTOR_WQX-15694` | -87.3403808, 41.4854651 | `LMG-05-0030` | Nearby WQP site; point location, not a cell aggregate | The NLDI discovery records indicate a connected monitoring and hydrographic context around the anchor. They do not establish that all listed sites are within the same fixed grid cell, share the same waterbody, or have comparable analytes, methods, dates, or QA/QC status. Source URL templates used: - `https://api.water.usgs.gov/nldi/linked-data/comid/3399712/navigation/UM/wqp?distance=25` - `https://api.water.usgs.gov/nldi/linked-data/comid/3399712/navigation/DM/wqp?distance=25` - `https://api.water.usgs.gov/nldi/linked-data/comid/3399712/navigation/DM/nwissite?distance=25` ## Source interpretation 1. The 1882 account supplies dated local route and contact-history anchors that reach back to 1673 and forward through the 1831 road opening. It is historical evidence about how a late-nineteenth-century county history narrated the region, not a neutral or complete account of Indigenous institutions. 2. The historical source places canoe, road, trade, and religious/trading activity in a connected Lake Michigan–Kankakee–Calumet setting. Because the described routes and settlements cross county and cell boundaries, the observation is related to N05_E18 but not equivalent to a fixed-cell connectivity measure. 3. The modern NLDI result provides a reproducible bridge between a human anchor, a local NHDPlus reach/catchment, and nearby WQP/NWIS-linked sites. It identifies where comparable modern extraction could be performed later; it does not itself provide a sector-wide hydrology statistic. 4. The historical and modern records converge only at the level of water-linked connectivity and place relationships. They do not measure the same variable, use the same boundary, or support a direct time-series comparison. ## Derived observations (not scores) ### D1 — Historical-to-modern geography crosswalk | Evidence | Spatial footprint | Relation to fixed `N05_E18` | Comparability | |---|---|---|---| | 1882 Porter/Lake county history | County and connected corridor narrative | Partial and cross-boundary | Qualitative only | | 1882 route/settlement passages | Bailly Town, Calumet/Kankakee, Fort Dearborn, Detroit route | Local corridor, not cell-wide | Related but not equivalent | | NLDI anchor position | Point-to-reach/catchment around Merrillville | Small subarea inside the fixed cell | Modern machine-readable geometry; not historical equivalent | | NLDI linked sites | Nearby points along upstream/downstream network | Crosses local subareas and likely multiple administrative footprints | Site discovery only | ### D2 — Bounded historical transition sequence ```text 1673: French missionary/explorer movement reported in the regional narrative → 1759: reported British transition in northern Indiana context → 1803–1804: Fort Dearborn route and trading-post influence reported → 1822: Bailly Town described as a trade/gathering center → 1831: Detroit–Fort Dearborn road reported as cleared and used for mail → 2026: USGS NLDI provides a machine-readable local reach/catchment and linked-site crosswalk ``` This is a source-organized sequence, not a continuous chronology and not a causal model. ### D3 — No score derived No area-weighted water value, transport density, population estimate, Indigenous population value, energy measure, constraint score, adaptive-capacity score, or `provisional_quadrant` is derived from these records. The historical account is qualitative and geographically mismatched; the NLDI output is network geometry and site discovery rather than a measurement series. ## Model classification ```yaml provisional_quadrant: unresolved classification_status: not_assigned reason: historical and modern evidence are not comparable enough for the fixed formula; primary Indigenous and administrative corroboration is missing; the NLDI result is a crosswalk rather than a score input confidence: unresolved_for_quadrant ``` `provisional_quadrant` is a model output and is intentionally not treated as an archival fact. ## Confidence and missingness ### Observation confidence - **Archive.org metadata and item identity:** high; the item metadata identify the 1882 title, creators, Cornell University Library contribution, 771-page extent, and identifier `cu31924104606235`. - **Printed-page historical extraction:** medium; relevant pages were located in OCR and checked against downloaded scan images, but the source is retrospective and settler-centered. - **Historical geographic fit:** medium-to-low; the narrative concerns Porter/Lake County and connected routes, not the full `N05_E18` cell. - **NLDI position/reach/basin response:** high for the returned API observation; the API returned structured GeoJSON, but its catchment and linked sites are not a cell-wide hydrologic profile. - **Modern temporal comparability:** low; the NLDI crosswalk is current/retrieved 2026-08-09 and does not reconstruct historical network conditions. ### Missingness codes - `geographic_match_uncertain`: historical county/corridor sources and modern catchments do not equal the fixed cell. - `qualitative_only`: historical contact, trade, road, and waterway descriptions have no standardized counts or rates. - `historical_measure_not_available`: no continuous pre-1800 or early-modern discharge, water-quality, population, or transport series was found in this bounded run. - `source_bias_requires_corroboration`: the 1882 county history is not Indigenous-authored and uses period terminology. - `not_searched`: primary Indigenous-authored, treaty, archaeological, and administrative records were not exhaustively searched in this run. - `period_match_uncertain`: modern NLDI network structure is not a direct measurement of the 1673–1831 historical routes. Archival silence in this search is not treated as evidence of absence. ## Falsification and alternative explanations The observed route and settlement sequence could be explained by political control, colonial violence, treaty and removal policy, land speculation, military logistics, commercial capital, and Chicago’s market position as well as by water-linked geography. A stronger test would compare the same historical and modern variables across the full nine-sector Great Lakes octagon, include Indigenous-authored and primary administrative/archaeological evidence, and distinguish observed routes from later retrospective narration. A boundary sensitivity test is also required: the NLDI catchment, county/corridor footprint, watershed, and fixed grid cell are different units. A result that changes when moving among these boundaries cannot be generalized without a principled crosswalk. ## Unresolved gaps and next search path 1. Locate Indigenous-authored, tribal-government, treaty, archaeological, and primary colonial/territorial records for Potawatomi, Miami, Illinois, and neighboring communities relevant to the Lake Michigan–Kankakee–Calumet corridor; preserve community attribution and source language. 2. Retrieve primary treaty, land-cession, removal, mission, and trading-post records for the 1763–1831 interval. Do not use the 1882 retrospective as the sole evidence for Indigenous institutions or displacement. 3. Use the NLDI-derived reach and linked-site identifiers to pull site-level WQP/NWIS metadata and time series only after checking station coordinates, dates, analytes, units, qualifiers, methods, and revision lineage. Do not turn linked-site discovery into a water-quality average. 4. Resolve the existing `nwisin.01.02200882` / `674 mg/L` discrepancy separately; the new NLDI crosswalk does not correct or overwrite that record. 5. Add a reproducible historical route/portage boundary crosswalk and compare it with the fixed 24 × 24 geometry and the nine-sector octagon. 6. Keep the quadrant unresolved until comparable raw-observation tables, explicit missingness, formula version, alternative explanations, and matched-sector checks exist. ## Provenance register 1. **Goodspeed and Blanchard, *Counties of Porter and Lake, Indiana : historical and biographical*.** Internet Archive identifier `cu31924104606235`; publication date 1882; creators Weston Arthur Goodspeed and Charles Blanchard; Cornell University Library contribution; item metadata report 771 pages and 782 scanned leaves. OCR file `cu31924104606235_djvu.txt`; printed pp. 12, 14–16, 20; scan leaves 15–19 and 23. Item: . Direct OCR: . 2. **USGS Network Linked Data Index position.** Query point `POINT(-87.3327 41.4828)`; returned `comid 3399712` and local flowline geometry. . 3. **USGS NLDI hydrolocation.** Returned snapped point, reachcode `04040001000480`, and measure `10.873528411319496`. . 4. **USGS NLDI basin.** Returned one GeoJSON catchment polygon associated with `comid 3399712`; this is a local catchment and not the fixed cell. . 5. **USGS NLDI linked-site discovery.** Upstream/downstream WQP and NWIS site responses used for the bounded table above. , , and . 6. **USGS NLDI method context.** USGS explains that NLDI indexes data to river-network flowpaths/catchments and supports position, basin, and navigation services; it is a discovery/crosswalk system, not a substitute for the underlying time series. . 7. **Fixed grid and active procedure.** Canonical sector geometry and research rules: `ghojualamanchu/sectors/N05_E18_MERRILLVILLE.json`; `08-research-sop.md`. ## Record limits This is a bounded N05_E18 research result. It adds page-verified 1673–1831 historical waterway, route, and contact-history observations from an 1882 retrospective source, plus a current USGS NLDI point/reach/catchment/linked-site crosswalk. It does not establish Indigenous-authored history, a cell-wide hydrology or connectivity value, a population or transport estimate, a causal claim, a derived score, or a `provisional_quadrant`. The historical source’s settler-centered framing and the absence of primary Indigenous corroboration remain explicit gaps. No secrets or private data are included.