How to read an urbex map: location, condition, and access

Read the location before interpreting the pin

A marker may represent an exact coordinate, an approximate area, or a feature spread across a large site. Check what the map says about precision before drawing conclusions from the marker’s position. A neat-looking point on a screen can still describe deliberately approximate information.

In uMaps, protected community records use approximate public pins; on standard records the exact locations open with earned reputation, a contribution key, or a uMaps Pro subscription, while the highest-risk records stay reputation-earned for every member. Imported open-data records do not require earned keys, and the published dataset preserves exact upstream coordinates. Neither kind of pin establishes a visitor entrance, authorized route, or permission to enter.

When keeping your own notes, preserve this distinction. Write “approximate area shown in app” when that is what you saw. Do not convert an estimate into a claimed exact location simply by copying it into another tool.

Separate a place’s former use from its current condition

A label such as abandoned or disused describes a reported state. It does not tell you everything about the structure, its ownership, or whether someone currently manages it. Read the supporting description rather than attaching your own assumptions to a category name.

OpenStreetMap’s tagging documentation distinguishes abandoned features from disused ones. It describes abandoned features as no longer readily reusable without significant repair, while disused features can remain in good repair. These are mapping conventions, not professional building assessments.

Source: OpenStreetMap: Abandoned features and lifecycle descriptions.

A historical use can also survive in a place name after the present use changes. Match the description to the observation date. If a record and a recent official page disagree, preserve the conflicting sources and look for a current explanation.

Treat access as its own information

OpenStreetMap maintains a separate family of access tags for restrictions on routes, buildings, entrances, and other features. A feature’s existence and its accessibility are different things in the data model. An unfilled access field does not give you a specific permission statement.

Source: OpenStreetMap: Access keys.

Look for the source and scope of an access note. Does it describe a public visitor area, an appointment with an operator, or something a contributor observed on a past date? A condition report that says a gate was open is not the same as an owner’s permission.

Use current official information and any agreed visit arrangements to resolve the practical question. If those are unavailable, keep access marked as unknown in your planning rather than treating a blank field as a positive answer.

Read reports as dated observations

Condition descriptions and hazard tags add context, but they have limits. A missing tag does not establish that no hazard exists. A photograph records one viewpoint at one moment, and a contributor’s description may cover only the part they observed.

When reviewing or adding a report, ask four questions: What was observed? When? From where was it observed? What remains unknown? A note such as “exterior photographed from the visitor path on this date” is more useful than a broad statement that the entire site was checked.

Keep direct observation separate from inference. Describe what is visible and cite any source used for additional history. A map becomes more useful when the boundaries of its knowledge are visible, not when every field sounds certain. Correct information you can verify and preserve uncertainty you cannot resolve.