6.4 Intersections & Cross-Streets

Why Intersection Types Matter for Dispatch

Very few real 911 calls come in with a clean street address. Callers on foot, callers in unfamiliar areas, and officers giving their own location all tend to describe where two streets meet instead: "I'm at the corner of Spruce and Pine," "we're at the dead end past the school," "it's the intersection where the road splits into two." CritiCall's Map Reading module tests whether a candidate can correctly classify what kind of intersection is being described and use it — sometimes as the destination itself, sometimes as the only location data available when no street address exists at all.

Core Intersection Types

• Four-way intersection — two streets that both continue through in all four directions past the crossing point; the most common and least ambiguous type.
• T-intersection (three-way) — one street continues through in both directions, while a second street meets it but does not continue on the far side, ending ("T-ing") into the through street.
• Dead end / cul-de-sac — a street that terminates entirely, with no through connection to another street, often ending in a circular turnaround.
• Cross street — any street that intersects the street being described; used as the standard fallback reference when an exact address is not available.
• Ambiguous duplicate names — a location where a "Street" and an "Avenue" (or similar) share an identical base name, so a description like "the corner of First and First" only makes sense if the two are clearly different road types, since a road cannot intersect itself.

Reading Caller and Officer Descriptions

CritiCall items translate plain-language descriptions into the intersection types above, and the "correct" reading usually hinges on one or two words in the description:

The "First and First" pattern is worth remembering as its own rule: two parallel streets never intersect, so a description implying two same-named streets crossing almost always means they are different road types — a Street and an Avenue, or a Street and a Boulevard — that happen to share a numbered name. The dispatcher's job is to confirm which type is meant, not to guess or dismiss the location as an error.

Cross-Streets as a Location Fallback

When a caller cannot provide an exact address — very common for pedestrians, out-of-towners, or panicked callers — the standard fallback is the nearest cross streets plus a direction of travel or a landmark, which the dispatcher then converts into an approximate location using the same address-range logic covered in address numbering.

Worked example: A caller says, "I don't know the address, but I'm near the corner of 4th and Elm, and the accident is about half a block further down Elm, toward 5th." The dispatcher does not need an exact street number to act. The stated cross streets (4th and Elm) anchor the location, and "half a block toward 5th" gives an approximate position between the two known cross streets — enough information to dispatch a unit immediately and refine the location further once responders arrive or the caller provides more detail.

Offset Intersections and Traffic Circles

Two less common but still tested intersection shapes round out the picture. An offset intersection occurs when a street does not line up directly across from the street it meets — for example, Spruce Street continuing on the far side of Main but shifted half a block north or south from where it approached. On a grid map, this shows up as two separate crossing points rather than one clean four-way corner, and a route or location description that assumes a straight through-connection will be wrong. A traffic circle or roundabout is a fifth basic shape: several streets meet at a circular junction rather than a single point, and a caller's or officer's position is best anchored to which spoke of the circle they are on, not to a single "corner."

Common Traps

• Confusing a T-intersection's "facing the dead end" phrasing with a true closed-off dead-end street; a T-intersection still connects through on the perpendicular street.
• Treating a duplicate street name ("First and First") as a dispatcher error rather than recognizing it likely describes two distinct road types sharing the same base name.
• Assuming an offset intersection is a single clean four-way crossing when the two street segments are actually shifted and meet at two separate points.
• Delaying dispatch while waiting for an exact address when nearby cross streets and a direction of travel already provide an actionable location.