Jet Lag: The Game · Hide+Seek

Is your city a good map?

Pick your city off the map below — or bring your own GTFS feed, the schedule file almost every transit agency publishes — and it works out how many distinct places there are to hide, which of the deck's questions actually split the map, which curses are unplayable here, and what all of that adds up to out of 100. Everything runs in this browser: the feed goes straight from the agency, or from your disk, into this tab, and is never uploaded anywhere.

Fetching a URL only works if the agency's server sends CORS headers, and plenty of them do not. When that happens, download the zip yourself and drop it in above.

Looking for a feed? Try the Mobility Database or Transitland.

Every field here is an override. Most of them are inferred from the feed if you leave them alone; departure time, board slack and border shape are fixed defaults instead. Change one and you are saying you know better than the feed, which is sometimes true.

Small

Medium

Large

A stop_id from the feed. Overrides the inferred round-start station.

Rectangle

Circle

Out-of-play stations. Comma-separated stop_ids.

Routes your group agreed are off limits. Comma-separated route_ids.

Where the map files are served from — the directory holding manifest.json. Blank uses the published one.

Skip OpenStreetMap (much faster) Skipping the map files keeps everything the feed alone can answer and excludes every question, curse and sub-score that needs map features — excluded, not guessed at.

Ignore the cached transit feed The transit feed is cached in this browser and reused. Turn this on to download it again — worth doing when the operator has published a new one. It does not affect the map files, which are always read from the network.

Use only the cached transit feed Never download the feed: use the cached copy, or stop if there is none. The map files are still read over the network unless OpenStreetMap is skipped as well.

Use the shape I drew as the game border The drawn shape's bounding box becomes the border instead of one fitted to the network, and the border shape above is forced to a box. Border box overrides this if you fill it in.

Analyse

Most of a run is spent reading the map files; skipping them above is much faster.

The verdict

Every point, traced

Where the points came from

Before you play

What this means for your game

House rules

What works, what fights you

Key numbers

The map at a glance

Every figure is measured on this feed, on the representative day for the service type selected above. Tiles with a gold rule and a “changes by day” chip move when you change the day; the rest are map-wide or come straight from the rulebook.

The network

The map you’re playing on

How long things take

Getting around

The deck

The questions

The curse deck

Every curse in the hider's deck, checked against this map's geography and this feed's network. A count is the number of qualifying features inside the border — outside does not count, because outside does not exist for this game.

Provenance

Where these numbers come from

Every number above, traced to the query that produced it.