Manual / MAP

Saved views

Setting up the map — the routes you look after, one route in one direction, two overlays on — takes a dozen clicks. A saved view is that picture, named, one click away.

What you are looking at

Under the filters in the Routes half of the sidebar there is a ＋ Save this view link, and after that a saved view each as a named link with a × beside it to remove it.

Press ＋ Save this view and the app asks you to Name this view, with a suggestion already filled in — the route number and direction if you have one selected, otherwise the operators you have picked, otherwise My view. Saving under a name you already have replaces it.

The Recent ▾ menu in the top bar has the same thing at its foot, as ＋ Save this view…, so you can keep the view you have just walked back to. It is the one door between the two lists, and they stay separate on purpose: Recent is automatic, private to this browser and forgotten after a while; saved views are deliberate, named and kept.

What a saved view remembers

It stores the address the app is on — the same one in your browser's address bar — so it restores everything the address carries:

• the route, its direction and which pattern is drawn;
• the open stop and the date its board is on;
• your Operator filter, and whether the sidebar is on Routes or Stops;
• which of Traffic, Incidents and Frequency are on, and the incident filters you set;
• whether you had switched Buses or Stops off;
• the Base map.

Because it is an address, a saved view is also something you can copy out of the address bar and send to a colleague. What they open is what you were looking at.

What it does not remember

Where the map is pointing. No saved view carries a camera. Restoring one re-selects the route and lets the map frame that route, which is why a link shared between two people shows the same thing rather than the same rectangle. A view with no route selected opens wherever the map happens to be.

How you read an overlay, as opposed to what you switched on. Your headway Watch and Alarm thresholds, the traffic overlay's Only congested roads box, and the incidents' Include tow trucks and retired records box are yours and stay yours; they are not part of what you were looking at, so they do not ride along. The headway list prints the thresholds it was judged by at its own head, precisely so a view someone else opens still says what it means.

The Clearance overlay. It is a standing reference layer rather than a view of something happening, so it is not carried in the address at all — and therefore not in a saved view. Switch it on where you need it.

Anything about the day. A saved view of a stop board carries the date you had chosen, not "today". Open a view you saved last week and its board is still on last week's date until you change it.

Where they are kept

Signed in, saved views live on your account and follow you to any browser you sign in on. On a deployment with no accounts, or while you are signed out, they live in the browser you are using and nowhere else — so a different machine, or a browser that has been cleared, has none of them.

Signed in, thirty is the most the account will keep.

What this is not

Not the same as making the map open like this. A saved view is a place to go; the button at the foot of the Layers panel — Open the map like this next time — changes where you start. Most people want both, and they are set in different places on purpose. See Turning overlays on and off.

Not a record of anything. Removing a saved view removes a shortcut, not data, and nothing about a diversion, a roster or a report depends on one.

When it looks wrong

A saved view opens on a different route, or on none. The address named a route the loaded timetable no longer has — usually because a newer timetable has been loaded since and route identifiers moved. Save it again from the route as it now is.

The list is empty on a machine where you had views. You are signed out, or on a deployment with no accounts, and these are the browser's own. Sign in, or save them again here.

The overlays did not come back. Check that the deployment you opened the view on actually has those overlays — a link written where Traffic exists opens without it where it does not, and no tile appears for it.