Translation is not wired up in this prototype

In the live site, choosing would render this page in — navigation, content, forms and all — and remember the choice for the rest of the visit.

What are you looking for?

Popular searches

HomeTravelersParking

Parking

Reserve a space before you travel, or just turn up — every lot, what it costs, and how far the walk is.

When do I leave?Driving directions

Book parkingSave time by reserving before your trip

Where a parking booking would actually go

Nothing was reserved — this is a demonstration. The fields match what the District’s current booking flow collects, so they map straight onto the existing system.

If Chauntry expose an API, we read live rates and availability into this page and post the reservation back, so the visitor books without ever leaving gspairport.com. That is the version worth having: one journey, one design, one place to fix things when they break.

If they do not, we hand off to park.gspairport.com with the dates already carried across, so the visitor is not asked the same questions twice. Payment and PCI scope stay with the existing platform, which is where they belong.

Every lotWhere the car goes

Where does the car go?

Switch on parking above to see the total for your stay.

GarageClosest

$12per day

Total depends on how long you stay

Spaces open

3 min to the terminal

410 spaces

Covered, skywalk to terminal

Continue
EconomyCheapest

$9per day

Total depends on how long you stay

Filling up

9 min to the terminal

34 spaces

Shuttle every 10 minutes

Uncovered

Continue
Surface

$10per day

Total depends on how long you stay

Spaces open

5 min to the terminal

220 spaces

Uncovered

Continue

How this connectsBooking runs on the District’s own platform

Preferred — read and write against Chauntry

GSP’s parking runs on Chauntry. If their API is available to the District, this page reads live rates and availability directly and posts the reservation back — the visitor books without leaving gspairport.com, and the lot cards above stop being illustrative.

Fallback — hand off with the details carried

If write access is not on the table, we hand off to park.gspairport.com with dates and times already populated. The visitor is not asked the same questions twice, and payment, card storage and PCI scope stay where they already are rather than moving onto the District’s website.

Either way, one journey

The point of putting the form here is that a visitor working out when to leave can settle parking in the same breath. Which system takes the booking is an implementation detail; being sent to a different-looking site to answer the same questions again is not.

Synthetic demonstration data. Lot availability, rates and walking times shown here are authored for illustration and are not live GSP data.

is not built in this prototype

The navigation is modelled at full depth so the information architecture can be reviewed, but only the pages needed to demonstrate the design system are built out.

Where a page moves or a URL changes between the current site and the new one, we set a 301 redirect so existing links, bookmarks and search rankings continue to resolve.

Site search is not wired up here

In the live site this returns results across pages, flights, amenities and documents from one index.

We would index the site at build time and query it server-side, so results work without JavaScript and every result is a shareable URL — the same pattern the flight board and fare filters already use.

Where a page has moved, the search result and the old URL both resolve: we set a 301 redirect so existing links, bookmarks and search rankings keep working.