This intersection does not exist.

Perhaps it speaks to a potential flaw in our street naming conventions.

Public Space Signage Wayfinding

“Hey, meet me at the hotel. It’s at… *checks sign* …the corner of Sheridan Garden Drive and Sherwood Heights Drive.”

– Some tourist, probably

In NYC you can have this.

In DC you can have this.

Does it aid wayfinding and mental map building?

But, this intersection does not exist.

This road is actually South Sheridan Way, not Sheridan Garden Drive (which itself is about 2km away).

S. Sheridan Way
The hotel, in the business of having unfamiliar visitors find them easily, is not likely to have gotten their own address wrong.

Perhaps it speaks to a potential flaw in our street naming conventions.

Google Streetview

You’ve seen it before: street names can be thematically related. In the example, Rosewood Lane is next to Teak Crescent which is next to Mahogany Lane which is next to Beechnut Road. All in tree-obsessed Oak-ville of course.

But, you see the forest for the trees.

For those that live in the area, the names can reflect its history and give a sense of unified place. But to outsiders, encountering the names for the first time, it makes it easy to confuse when remembering contextual aspects rather than the words themselves.

(Do you want Sundial Court or Sunrise Court one block over?)

Who are these signs for? Who is the end user?

Perhaps Sheridan Garden Drive and South Sheridan Way confused even the sign installer.

Perhaps related isn’t always better.