Bureau of sights and sounds

Changed somewhere else

“Keep both” saves your version as a second place, leaving theirs untouched. Attached routes stay with the original.

New list

Add to lists

Layers

Uncheck what you never use — the layer stays here, it just leaves the panel on the map.

Your own layer

The address needs {z}, {x} and {y}. Coverage is optional: given it, the layer stops asking for tiles outside, and its outline shows on a wide view.

Data

What is on the server

Full snapshot

Everything, routes included — one file, streamed straight from the server. This is the backup to keep.

Original route files

The .gpx and .kml files exactly as they were attached. They are not part of the snapshot — download them separately, or copy the files_dir folder from the hosting.

Export the current selection

Whatever the filters currently show, as points: name, coordinates, description and colour. Routes are not part of these formats.

Load a dataset

A .json snapshot or a places.js file from the browser version. It is sent in parts, so size is not a problem. Everything now on the server is replaced — a version is kept in history first.

Rebuild lookup tables

Tags, list links and season segments are derived from the records and kept in step automatically. Rebuild them if you loaded the database by hand, or if you are coming from the version where MySQL was only a spare copy. This also clears links to lists and territories that no longer exist — a loaded snapshot can carry them, and nothing else can see or fix them.