Minneapolis
city in and seat of Hennepin County, and largest city in State of Minnesota, United States

Minneapolis is a city in Hennepin County, Minnesota, United States, and its county seat. With a population of 429,954 as of the 2020 census, it is the state's most populous city. Located in the state's center near the eastern border, it occupies both banks of the Upper Mississippi River and adjoins Saint Paul, the state capital of Minnesota. Minneapolis, Saint Paul, and the surrounding area are collectively known as the Twin Cities, a metropolitan area with 3.69 million residents. Minneapolis is built on an artesian aquifer on relatively flat terrain and is known for cold, snowy winters and hot, humid summers. Nicknamed the "City of Lakes", Minneapolis is abundant in water, with thirteen lakes, wetlands, the Mississippi River, creeks, and waterfalls. The city's public park system is connected by the Grand Rounds National Scenic Byway.
Dakota people previously inhabited the site of today's Minneapolis. European settlement began north of Fort Snelling along Saint Anthony Falls—the only natural waterfall on the Mississippi River. Location near the fort and the falls' power—with its potential for industrial activity—fostered the city's early growth.
Begin with the source’s own compact description: “Minneapolis” is city in and seat of Hennepin County, and largest city in State of Minnesota, United States. The dossier treats that line as a proposition to test through Minneapolis, city and seat, not as a finished interpretation.
Why this record matters
The phrase “city in and seat of Hennepin County, and largest city in State of Minnesota, United States” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Aug 11, 2026. The linked authority identifier is Q36091. VIAF identifies the subject as 141350341. The Library of Congress control number is n79003965. Authority coordinates are 44.982, -93.269. 4 of 6 selected statements include explicit references; 3 carry qualifiers and 0 use preferred rank. The first chronological checks are 2020.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Minneapolis”, its source revision and the description used here.
- Expand the search: follow Minneapolis primary sources, Minneapolis archive and Minneapolis research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Minneapolis”?
- Which earlier names or jurisdictions may reveal additional records?
- Which authority defined the place, boundary or structure at the relevant date?
Search terms from this dossier
This entry incorporates text from “Minneapolis” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.