Places, neighborhoods, the map and the rail

CLT Explorer holds 346 place records for Charlotte, filed into 22 neighborhoods, plotted on one map, and threaded onto the city's two rail lines. This guide is organized by what you are trying to do — find a place, read what the guide knows about it, arrive in a neighborhood, ride the line, or read the whole registry at once — and it is equally clear about what the guide does not hold. Where the site stays silent (no hours, no neighborhood boundary, no parking note) that silence is a decision, and this guide explains each one.

Updated: 2026-08-20

Contents

1. How many places? Three honest numbers
2. Finding a place
3. Reading a place page
4. Browsing a neighborhood — the arrival page
5. The map and its layers
6. The A–Z registry at /places and The Register
7. Getting around by rail
8. What this guide does not hold
9. Numbers, as measured

1. How many places? Three honest numbers

You will see three different totals on this site, and they are all correct. They count different things, and the site never averages them into one comfortable figure.

So: 346 records in all; 343 you can open a page for; 311 on the drawn map; about 212 with a calendar that says, in the data, that they run year-round.

Two things worth separating, because the word "open" does two jobs here:

• A record's lifecycle status is what has happened to the business. Today: 326 open, 2 seasonal, 1 temporarily closed, 6 permanently closed, 8 site-only (the building is gone), 3 unconfirmed.
• A record's seasonal calendar is a separate, sparser field, and only 213 of the 346 records say anything definite in it — 212 "open", 1 "closed". The rest say "unknown", and unknown is counted in neither direction. That is where "212 places open" comes from. It is a fact about the year, not about this minute, and the site is careful never to dress it up as "open now".

If you want to know whether a specific place is open right now, see the status chip in §3, which is drawn from a real posted week of hours and from nothing else — and which is absent on most pages, deliberately.

2. Finding a place

There are five doors to the same records. None is "the" canonical one — pick by what you already know.

How to use it. Every place has a stable URL of the form /poi/<slug> — for example /poi/noda-brewing-company, /poi/discovery-place, /poi/excelsior-club. Slugs are permanent: where two records were merged, the retired slug redirects to the surviving page rather than 404ing, so an old link still works.

What the output looks like. Every door lands you on the same place page (§3). The map and the A–Z both show the whole published set; the arrival pages and the ride pages show filtered sets and say so in words.

Tips.

• Closed and demolished places stay listed. They are labelled, never hidden — the Excelsior Club has a page, and it says the building's story rather than pretending you can visit.
• Three places are unconfirmed and have no public page at all (the Register counts them as "withheld"). If you followed a link to one and got nothing, that is why.

3. Reading a place page

A place page (/poi/<slug>) is laid out in the order of a decision: where is it → can I go → should I → what is it → who says so. On a phone that is a single column, top to bottom. On a wide screen the facts-and-actions column sits beside the reading column, but the reading order (and the keyboard tab order) is identical.

The blocks, in order

1 — The hero. Four lines: the neighborhood and street, the name, one sentence saying what the place is (the "one-liner" — every one of the 346 records has one), then the status chip and the category tags.

2 — The status chip: "Open now · closes 10pm". This is the block most worth understanding, because most of the time it is absent, and that absence is deliberate.

• The chip only ever appears when the record carries a real, structured week of hours — day by day, open and close. Twenty-eight places have that.
• A place whose record only says "open year-round" gets no chip, because "this business operates in this season" is not the same claim as "you can walk in right now", and the site refuses to upgrade one into the other.
• Where a place is provably shut, it says so: Closed today, Temporarily closed, Permanently closed, Seasonal — closed until May.
• Times are always Charlotte's clock (America/New_York), never your device's, and never the server's.

3 — The action row. Directions is the page's one highlighted button; call, website and Add to trip sit beside it in neutral styling. On the 14 history records — six permanently-closed, eight site-only — Directions does not render at all (routing you to a building that is gone is not a route), and Add to trip takes the highlight instead.

4 — The decide block ("Hours", or "Where it stood"). The week's hours in whatever shape the data actually has:

• a seven-row table with today marked, when the days genuinely differ (this is the majority of the structured records — Charlotte weeks vary a lot);
• one collapsed line when every day is the same;
• "Open 24 hours" where that is true;
• otherwise the season's own prose or the honest line "Hours unconfirmed".

Below it: price band (35 records have one — none is invented from cuisine or category), a reservation note where authored, the postal address, and a walk time from your home base if you have set one. On the 14 history records this section drops hours and price entirely and re-titles itself "Where it stood".

5 — The take. The guide's editorial paragraph — the local-friend voice. Roughly 249 records carry one; the rest simply have no "The take" section, rather than a placeholder. Two rules worth knowing: the take never opens by repeating the one-liner you just read in the hero, and where it recommends somewhere else, that somewhere is a real link, not a name in prose.

6 — Access, details, worship, deals. Each renders only when the record has something to say. "Details" is genuinely the long tail — cuisine, the year it opened (dropped when the prose above already said the year), operator notes.

7 — Answered questions (FAQ). Ninety-six places carry a researched Q&A block. It sits between the facts and the sources, and the same array that renders on the page is what feeds the structured data — they cannot disagree. A place with no FAQ shows none: an invented question is worse than no FAQ.

8 — Photos, reviews, check-in. Visitor photos and reviews load after the page (only approved content appears). The check-in control is withheld on the 14 history records — you cannot be somewhere that no longer exists.

9 — Sources. Always the last thing in the reading column. Every fact group names its source and its trust level in one sentence with one truth value — "July 2026 — not independently verified" rather than a contradictory "verified July 2026 (unverified)". A record researched and found to have no official website says so; that is a finding, not a gap.

10 — Similar nearby. Five walkable alternatives, each with its own Add to trip. Chosen by category closeness first, then by walking distance from this place (not from your home base), capped at a 45-minute walk. Closed and demolished places never appear as suggestions. No place page ever ends in nothing: the heading shrinks its claim as the evidence thins — "Similar nearby" → "More in Dilworth" → "Closest to here".

11 — The neighborhood band. The web this place sits in: its district, its categories, the places, people, organizations, eras and story threads it connects to — one hop only, nothing second-degree. Every pill is a link.

Tips

• A permanently-closed or site-only page is a different page. Expect a "Lost Charlotte" line at the top ("the building is gone", or "closed for good in 1990"), no hours, no price, no directions, no check-in — and, where the record knows it, a link to what stands there now.
• The share-card preview for a page quotes only sentences the page actually prints. If a preview ever names a fact you cannot find on the page, that's a bug worth reporting.

4. Browsing a neighborhood — the arrival page

/districts lists all 22 neighborhoods as cards, grouped editorially (the four uptown wards, north of the center, south along the rail, the east side, the south side, the west side, and "More of the county"). Each card carries a derived count of the places the guide holds there — typed nowhere, so it cannot go stale.

/districts/<slug> is the arrival page, and its one job is: "I just checked in near NoDa — what's my first hour?"

What's on it, in order

1. The arrival paragraph — the first hour. The only authored prose on the page: where you are, a walkable first hour naming real places (each a link), how the rail reaches you or honestly doesn't, and one meal steer lifted from the member place's own record. All 22 districts have one. NoDa's, for example, walks you from Smelly Cat coffee, past the TAOH Outdoor Gallery, to a taproom, with the Haberdish order named.
2. The neighborhood map — a soft tinted field over where the district's places actually are, the rest of Charlotte behind it, the city limits around all of it. See §8 on why it has no edge. Each place is a button; selecting one fills a card below the map with its name, category, the guide's line and a link. Keyboard: arrow keys move between places, Escape clears.
3. Getting here by rail — the stations whose ten-minute walkshed this district anchors, across both lines, each linking straight to its band on the ride page. Eleven of the 22 districts have no station, and those pages say so in a plain sentence: "No rail station sits inside Dilworth — neither the Blue Line nor the Gold Line reaches it," with a pointer to the map. That is the intended output, not an error state.
4. The places the guide holds here — open and seasonal places only, grouped by their primary category, alphabetical inside each group, each with its one-liner. Closed and site-only records are deliberately absent: an arrival page promising you a bar that shut is the exact failure this list is designed to avoid. Those records are still on the map's History layer and in the A–Z.
5. Tours that come through — derived from tours' resolved stops, so a tour only claims a district it still visits. Renders nothing when no tour crosses.
6. One beat of its history — a single fact from the 677-fact archive whose headline names the district, quoted verbatim, hedges included ("Some accounts date…"), with a link to that year on the timeline where the sourcing lives. Some districts have no beat yet and show none. The search terms follow the corpus rather than the map: Second Ward's story is filed under Brooklyn, the Historic West End's under Biddle and Johnson C. Smith, East Charlotte's under Eastland.
7. Go deeper — the wiki entry for the district, and the same places on the map.

Tips

• /map?district=noda is a real deep link — it opens the map already flown to that neighborhood's places.
• The day-trips ring (32 places, an hour out — the Speedway, the lake, the mountains) is a district like any other with an arrival page, but it is deliberately outside the drawn map frame. See §8.

5. The map and its layers

/map is a full-screen interactive map of Charlotte. It needs WebGL and JavaScript; if either is unavailable you get a plain banner pointing you to the A–Z, which holds every place as text.

Layer chips

Along the bottom is a scrollable row of toggle chips — real buttons, keyboard-operable, each with a colour dot and (where it has any) a count of the places it would add.

On when the map first opens: Landmarks, Dining, Activities. Off until you tap them: Takeout, Breakfast, Nightlife, History, Mini golf, Fishing, Shopping, Beach access, Accessibility, Blue Line, Gold Line.

Two things to know about how chips behave:

• A place can be in several layers at once. Categories are tags, not folders. A brewery that is also a landmark appears under both toggles — but its pin is coloured by the single highest-priority layer it belongs to (Landmarks wins over everything), so the pin never flickers between colours as you toggle.
• History is how you see the closed places. Permanently-closed, site-only and unconfirmed records are hidden from the map entirely until the History chip is on. That is the same rule the arrival pages follow.
• The two rail chips own no pins. Blue Line and Gold Line draw the route, the stations and the vehicles running right now; their chip counts are live fleet sizes, not place tallies. Both start off, because a full-length polyline on first load would dominate a map about places.

Jump to a neighborhood

Top-left is a plain "Jump to" dropdown of the districts. Choosing one flies the camera to the box that actually contains that district's pins (not to an approximate box), so you always land framed on real places. The readout beside it tells you how many pins are currently drawn out of how many places are mapped.

You can also arrive pre-flown via /map?district=south-end. An unrecognised value is silently ignored and you get the plain city view — never an error page. /map?tour=<slug> likewise draws a tour route, and silently falls back to the plain map if the tour has fewer than two locatable stops.

Tips

• Zoom is meaningful: at city scale you get district label bands and the marquee places; as you zoom in, more pins earn their place.
• The map deliberately will not let you wander out of the region, and it will not rotate by drag — it's a guide map, not a survey instrument.
• The basemap tiles come from OpenFreeMap. If they're blocked or you're offline, the banner says so and sends you to the directory.

6. The A–Z registry at /places and The Register

/places is the guide's index — the paper-guidebook page. One row per published place, every published place, sorted by name and grouped only by initial letter. 343 rows today (the three unconfirmed records are excluded, because they have no page to link to). Names that don't start with a Latin letter land in a final # group.

How to use it. Use the alphabet jump-nav, or just Ctrl+F / Cmd+F — the page is built to be searched by the browser, and it needs no JavaScript to read. Each row carries the place's neighborhood, its cuisine where it's a sit-down restaurant, an open/closed chip where the data supports one, and a "closed" label where the place is history.

Near your base. If you set a home base, the list gains a second reading: the same rows sorted by how far they are from you. Letter headings are suppressed while that sort is on, because they would no longer mean anything.

The Register

Below the A–Z, at the #the-register anchor, is Plate XII — the same list as one sortable table, one line per place:

How to use it. Click a column header to sort (Tier, Price, Hours and Deals sort "most-interesting-first" on the first click); use the district <select> to filter. It arrives fully rendered and sorted A–Z before any JavaScript runs — sorting and filtering are additions, not requirements.

What the output looks like — and the point of it. Most cells in the Hours, Price, Deals and Opened columns are em-dashes, and they stay visible. The Register is the guide's coverage ledger printed as itself: its footer tallies the gaps rather than hiding them ("hours structured for 28 of 343 · prose-only for 90 · none recorded for 225 · corrections invited"). Missing facts sort after present ones in both directions, because absence is not a value.

7. Getting around by rail

Charlotte has two rail lines, and the guide treats them as the city's spine.

Note the two different hedge words, and that they are always printed. "Scheduled" means a real published timetable stands behind the number — 62 minutes is the longer direction of the two, so a rider who budgets it is never late because they trusted us. "Running time" means the figure is arithmetic over the stop times in the feed with no departure grid behind it.

The walkshed idea

Everything the ride pages claim rests on one rule: a place is "on the line" if it is within a half-mile — about a ten-minute walk — of its nearest station on that line. Two consequences the pages are explicit about:

• Each place lands at exactly one station, its nearest. Walksheds overlap on the ground, but a page listing the same brewery under two consecutive stations would read as a bug.
• Most of the city is off the spine, and the page says so up front. The Blue Line's walksheds hold roughly 113 places and the Gold Line's roughly 79; the guide holds 346. The ride pages point you at the map and the A–Z for the rest rather than posing as a city index.

Only places you can actually go are counted — open and seasonal. History, temporarily-closed and unconfirmed records are real data but are not "places on the line".

Reading a ride page

/lines/blue reads north first — UNC Charlotte at the top, I-485 at the bottom — because north is up on a map. /lines/gold reads west first, from its origin terminal at French Street, because an east–west line has no map-vertical to inherit.

Each station is a band down one continuous rail, and each band carries:

• the station name, and "Station 9 of 26";
• its neighborhood — or, for a station outside every guide district, the honest line "on the corridor — between guide districts" (three Gold Line platforms are like this: French Street, Johnson C. Smith University and Bruns Avenue);
• an arrivals board in both directions, which always states whether its minutes are the agency's live prediction or the published timetable;
• the places within a ten-minute walk, alphabetically. A station with none says "No guide places within a ten-minute walk of this platform yet" — an absent band would read as a missing station.

Between the bands, live trains appear in the sequence — a train renders between the two stations it is actually between, not in a summary box. Positions come from the live feed only; there is no schedule fallback pretending to be a position. When nothing is reporting, the status line says so ("No trains reporting right now — service winds down after 1am") rather than going blank.

The CTC transfer

The two lines meet at the Charlotte Transportation Center. On the Blue Line ride page the CTC band carries "Change here for the Gold Line", linking straight to that platform's band on the other page, and vice versa. This is derived from a symmetric link in the station data rather than written by hand, so the two sides can never disagree about where the transfer is. /lines states the same thing once, in a sentence, above both cards.

Tips

• Every station band has an anchor: /lines/blue#station-east-west-blvd jumps straight to it. The arrival pages link this way.
• "Station" is the Blue Line's word and "platform" is the Gold Line's, throughout — that is copy driven by the data, not an inconsistency.
• If you set a home base near a station, place pages will tell you the walk from it.

8. What this guide does not hold

Stated plainly, because in each case the silence is the honest answer and not an oversight.

No district boundaries — anywhere. The guide has no polygon for any of its neighborhoods and draws none. On the arrival-page map a district is a soft tinted field with no edge at all, centred on where its places actually are and reaching to the furthest of them, with a caption stating its ground radius ("about 3km from its centre — it is where NoDa's places sit, not a boundary"). The reasoning is short: an edge would be a claim, and no municipal dataset carries a boundary for a name this guide invented anyway — "Steele Creek & Whitewater", "Matthews & Mint Hill" and "LoSo & South Boulevard" are the guide's own composites. The far-zoom label bands on /map are approximate boxes for labelling only, and the "jump to" control deliberately flies to the box of the district's real pins instead of using them.

No roads. The repo holds no road geometry, so the schematic city map draws none. It draws what it actually has: every place's real coordinates, every station's, and the city limits.

The day-trips ring is outside the drawn frame. Its 32 places are an hour out; including them more than doubles the map's latitude span and squashes Charlotte into the middle 40% of the picture. They are counted and named in the caption instead — never silently dropped — and the day-trips arrival page still exists and still works.

Parking. The place-page schema has a parking field and 13 records carry one. There is no municipal lot inventory, no metered-zone map and no street-parking rule set in the data, so a page with no parking note prints nothing — not "parking information unavailable", and emphatically not a plausible-sounding guess.

Hours, for most places. 225 of the 343 published places have no hours recorded at all, and 90 more have only prose. See §3 and §6.

Accessibility detail — and this one is a gap, not a decision. Eighteen records carry a short, hand-written access note, and where one exists the place page prints it. There is no structured accessibility data — step-free entry, restroom, parking-to-door — on any of the 346 records, so the Accessibility chip on the map currently has nothing to select, and the site will not infer accessibility from a category or a building type. If step-free access decides whether you can go, call the place. We would rather say that than draw you a symbol we cannot stand behind.

Deep cuts, on the place page. Thirty-eight records carry a deep cut — a researched, sourced extra fact that did not fit the main description. Today it surfaces as a Deep Cut badge in search results (hover or focus the badge to read it) and in the plain-text version of a page. It does not yet appear on the place page itself, so a deep cut is currently something you find by searching rather than by reading.

9. Numbers, as measured

Measured against the shipped corpus on 2026-08-20. Where a number is derived at build time, the site recomputes it and will not go stale; the figures below are here so a reader knows the scale.

Where a number is computed by the site itself, the site recomputes it on every build and cannot go stale. The figures here are a snapshot so you know the scale before you start.

Found something wrong? Email corrections@clt.theperfectship.com. It goes to a person, not a queue, and it gets answered within five business days. See also the Colophon for how the guide checks its facts.

See also: the user guide index · FAQ · troubleshooting · glossary