Distinguishing Geographic Concepts Through Concrete Examples

Hello, and welcome to Where Is It? This course begins with a deceptively ordinary question: when we say something is “somewhere,” what exactly have we asserted?

A map pin, a postal address, a room number, a city name, a database key, and “next to the elevator” can all answer where? Yet they do so by very different means. In this opening module, we build a vocabulary for telling those means apart. The aim is not to enforce one universal dictionary definition, but to make the assumptions inside a location claim explicit.

---

A first distinction: “where” is not one kind of answer

Consider the following statements about a university makerspace:

1. “The makerspace is at $40.4433^{\circ }\text{ N},79.9436^{\circ }\text{ W}$.”
2. “The makerspace is east of the library.”
3. “Go to Engineering Building, Room C-214.”
4. “The equipment record is asset MS-042.”
5. “The makerspace is in the Innovation District.”
6. “The makerspace begins beyond the access-control doors.”

All concern the same general setting, but each identifies a different feature of “where.” The first provides a coordinate-based location. The second gives a relative position. The third is an address designed to guide a person through a building hierarchy. The fourth concerns identity. The fifth invokes a region, whose exact status depends on who defines the district. The sixth invokes a boundary.

A useful working distinction is:

Term	Core question	Example	What it does not guarantee
Place	What meaningful or recognized setting is this?	“My campus,” “downtown,” “home”	A precise extent or coordinate
Position	How does this object stand relative to a system or other objects?	“Third in line”; “east of the library”	A stable postal or digital address
Location	Where is the object situated in a chosen space?	A GPS coordinate; “in Room C-214”	A unique identity
Address	What designation can be resolved to reach or retrieve it?	Street address, URL, file path, room number	Exact geometry or permanence
Identity	Which particular entity is this?	Asset ID, database primary key, registered feature ID	A current location
Reference	What anchor, convention, or named entity makes the description interpretable?	The library in “east of the library”; a map grid	All the surrounding circumstances
Context	Under what circumstances is this description interpreted?	Which campus, date, map, audience, or database?	A formal identifier
Boundary	What rule separates inside from outside?	A city limit, property line, access-control threshold	A physical wall or universally accepted edge
Region	What extent or collection is being treated as an area?	A municipality, watershed, sales territory, “downtown”	A sharp boundary

The terms overlap in ordinary language. “I live in Boston” might communicate a place, an administrative region, a metropolitan affiliation, or even a postal convention. The task is to identify the role a term plays in a particular claim.

---

Space and place: geometry is not the whole story

A coordinate system treats a location as a position in measurable space. A place adds recognition, use, memory, and meaning. A bus stop can have latitude and longitude, but it becomes your stop through routine and experience. Conversely, an unvisited coordinate may be perfectly locatable while remaining almost placeless to you.

The distinction matters outside geography. A memory address is a location in a computational address space, but it is not ordinarily a place. A library call number is both a shelf address and a classificatory position, but it says little about the reader’s relationship to the book. The course will repeatedly encounter this pattern: a system can locate something accurately while failing to capture what that location means.

---

The grammar of a location claim

Before accepting “X is at Y,” parse the statement. Ask these questions in order:

1. Object: What is being located? A person, building, legal entity, document, sensor reading, or event?
2. Identity: How do we know it is that object rather than another one with the same name?
3. Space: In what kind of space does “where” operate: geometric, hierarchical, relational, categorical, or computational?
4. Reference: What anchors the description? A coordinate grid, a landmark, a map, an organizational chart, or a database schema?
5. Context: Who is speaking, at what time, for what purpose, and under what conventions?
6. Boundary and region: Is the object point-like, extended, bounded, fuzzy, changing, or disputed?
7. Address and retrieval: If we have a label or path, what system resolves it into the thing sought?

These questions distinguish claims that appear equivalent but are not.

For example, “the café is at the station” could mean:

• inside the building legally designated as the station;
• adjacent to a station entrance;
• listed under the station’s name in a navigation app;
• reachable by following signs from the station;
• part of a socially recognized station district.

The sentence leaves its boundary rule, reference, and context unstated. That omission is often harmless in conversation. In engineering, mapping, law, logistics, databases, or research, it can produce serious ambiguity.

---

Boundary, region, and representation

A region is an extent treated as a unit. Its boundary may be legal, physical, statistical, conventional, or subjective. The key word is treated: regions are not always discovered as ready-made objects in the world. They are frequently produced by rules and purposes.

The diagram suggests several important cautions:

• A boundary is not the same thing as the region it encloses. A municipal border is a line or rule; the municipality is the area and administrative entity defined through it.
• A boundary may be represented differently at different scales. A coastline on a small map is not a complete physical account of tides, rocks, harbors, and changing sediment.
• A coordinate often represents only one selected part of an extended object. A point placed near the middle of a lake is a useful representation, not the lake itself.
• Some regions do not admit a determinate edge. “Silicon Valley,” “the South,” and “downtown” can be useful expressions even when informed people disagree about where they end.

This is a first instance of a recurring course theme: a representation is not identical to the thing represented.

---

A concrete case: “Denver” is not one object

A geographic name can appear to settle identity, location, and boundary all at once. The U.S. Geological Survey’s Geographic Names Information System (GNIS) provides a counterexample. Its treatment of communities shows why a name alone is an inadequate locator.

GNIS distinguishes two possible referents:

Claim	Likely object	Boundary status	Identity mechanism
“I live in the City of Denver.”	A civil, administrative entity	Legally defined	A distinct GNIS feature record
“I live in Denver.”	A named populated place or metropolitan community	Often perceived and indeterminate	A separate GNIS feature record

The two records can share a similar name yet refer to distinct entities. The Civil feature has a legal boundary; the Populated Place record represents a community that may extend beyond it. Neither a postal ZIP Code nor a familiar city name automatically resolves the ambiguity.

This case separates several concepts sharply:

• Name is not identity. A name can be shared, abbreviated, translated, changed, or reused.
• Identity is not boundary. A record can identify an entity even when its extent is fuzzy.
• Coordinate is not extent. GNIS may use an approximate center for an areal feature, a highest point for a summit, or a mouth for a stream.
• Place is not always a legal region. Denver as lived metropolitan place is not reducible to Denver as a bounded political unit.

---

Address versus identity

Addresses are optimized for finding. Identities are optimized for distinguishing.

A postal address such as “12 Oak Street” can usually guide mail or a visitor, but it may change when a street is renamed or buildings are renumbered. The house can persist through the address change. Conversely, a property identifier or institutional asset number can identify a particular record even if it does not tell an ordinary person how to reach the physical object.

The same distinction appears in computing:

• A filename such as report.pdf is a human-oriented label and can be duplicated.
• A directory path is an address within a particular filesystem hierarchy.
• A content hash or database primary key can function as an identity mechanism.
• A URL may act as a network address, but redirects, ownership changes, and revisions can complicate what it identifies.

Thus, an address often has a resolution procedure: a postal service, navigation system, filesystem, router, catalog, or database uses it to retrieve or reach something. An identity may participate in retrieval, but it does not necessarily specify a route.

---

Reference and context: the invisible machinery

Relative descriptions make reference visible:

“The seminar room is north of the library.”

The library is the immediate reference or anchor. But the statement also requires context:

• Which library?
• Which campus?
• What orientation convention does the map use?
• Is “north” geographic north, the top of a floor plan, or a colloquial direction?
• Is the location current, or does it refer to an older campus layout?

A coordinate description also relies on reference, even when it looks self-contained. Latitude and longitude depend on conventions about an Earth model, zero meridian, angular units, and datum. These technical components will become central later, but the conceptual point is immediate: numbers are never location by themselves.

The statement “$(10,20)$” is therefore radically underdetermined. It might be:

• a Cartesian point with meters as units;
• a pixel position, with an origin at the upper-left corner;
• a row and column index in a matrix;
• longitude and latitude expressed in degrees;
• a game-board square;
• a pair of parameters in a model.

Without the space, axes, origin, orientation, units, and representation convention, the pair does not locate anything.

---

A compact classification protocol

When reading or writing a claim about where something is, use this checklist.

If the claim primarily answers…	Classify it as…	Example
“What meaningful setting is this?”	Place	“The old neighborhood”
“How is it arranged relative to something else?”	Position	“Second shelf from the top”
“Where is it in a specified space?”	Location	“At these map coordinates”
“What label lets a system reach it?”	Address	“Room C-214”
“Which exact entity is it?”	Identity	“GNIS feature ID 1234567”
“Relative to what anchor or convention?”	Reference	“East of the library”
“Under what shared assumptions?”	Context	“On the 2026 campus map”
“What separates interior from exterior?”	Boundary	“Inside the city limit”
“What extent is treated as an area?”	Region	“The drainage basin”

One claim may receive several classifications. “The parcel at 12 Oak Street lies within District 4” contains an address, a legal parcel identity, a location claim, a region, and an assumed jurisdictional boundary. Good analysis does not force it into only one category; it identifies what each component contributes.

---

Key takeaways

A location claim is more than a statement of position. It can involve a meaningful place, a geometric or structural position, a retrievable address, an entity’s identity, an interpretive reference and context, and an account of boundaries and regions.

Most importantly, these elements can come apart. A city name need not identify one entity; a coordinate can represent an extended feature without describing its boundary; an address can change while the object remains the same; and a region can be useful despite having no sharp edge.

Next, we will make the hidden structure of a locating system explicit: object, space, reference frame, dimensions, units, and representation. That framework will let us explain rigorously why $(10,20)$ is not yet an answer to “where?”