GPSLarpHelp

How do I simulate walking or driving a route?

A single fixed position is not what you want. You want the reported position to move — along streets, at a speed that reads as a person on foot or a car on a road.

Pick a start and an end. GPSLarp fetches a real street route between them and moves the reported position along that geometry. Left alone, walk goes at 1.4 metres per second — about 5 km/h — and drive spreads the route's own estimated duration across it, so the pace varies with the road. Both are defaults you can change: a speed slider beside the route lets you set the pace instead, and the Mac drives the whole journey either way.

The limit to plan around before anything else

The Mac has to stay running and connected for the entire journey. The movement is not handed to the phone to play by itself — GPSLarp holds the connection and pushes each position as the journey reaches it. Quitting the app, letting the Mac sleep, closing the lid, or losing the connection ends the journey wherever it had got to. A two-hour drive means two hours of an awake, connected Mac.

01Where the route comes from

Neither mode draws a straight line between your two points. GPSLarp sends the start and the end to a routing service over the internet, and that service returns real street geometry — the shape an actual route between those points has, with its turns and its detours in place. Which service is asked depends on the mode, and the box below is worth reading before a walk behaves differently from how you expected.

Walk and drive ask different services, and that has consequences

Corrected. This box used to say "A walk follows a driving route" — that both modes asked for a driving route and walk simply played it at a walking pace, so a walk would never take a footpath and would obey one-way restrictions a person on foot would ignore. That was true and it is not any more. Walk mode now asks a pedestrian routing service and drive mode asks a driving one. They are run by different organisations, on different addresses, and the mode you pick decides which of them is asked.

Three things follow from it, and the first is the one that reaches you as a failure:

  • A walk can fail while a drive between the same two points still works, because the two requests go to two different services and either can be unavailable on its own. GPSLarp says so when it happens rather than quietly serving a driving route instead — see section 05.
  • A walking route may take paths a car cannot, and it is not bound by one-way restrictions in the way a driving route is.
  • Which company sees your two points depends on the mode, which is why the privacy note further down is phrased the way it is.

There is deliberately no fallback. A walk the pedestrian service cannot answer is refused, rather than being served as a driving route under a walking label — that substitution is exactly what the old behaviour was, and it is the reason this box existed in its previous form.

You may be offered a choice of routes for the same pair of points — the fastest one plus up to two alternatives — in the way a navigation app offers a choice. You pick which one to use before anything starts moving.

From there the application builds a track: the route's points, each with a timestamp saying when the position should be there. Playing that track is the journey — GPSLarp works through it and reports each position to the phone as its moment arrives.

Screenshot pending — GPSLarp showing a routed path between two points
The line follows streets because a routing service computed it from real road geometry, not because it was drawn between the pins.

02How fast each one moves

Left alone, walk moves at 1.4 metres per second. That is roughly 5 km/h, an ordinary walking pace, and it is the same on a flat street and up a hill, the same on a short route and a long one — it does not vary with the terrain.

Left alone, drive uses the routing service's own estimate of how long the route takes, and spreads the movement across the geometry accordingly. So that speed is not one number — it varies with the road, faster where the service expects a fast road and slower where it does not.

Both are defaults, and you can set the speed yourself. A slider sits beside the route once one is planned, with a box you can type an exact figure into. The two modes offer different ranges: walking runs from 1.5 to 15 km/h in half-steps, driving from 10 to 160 km/h in steps of 5. Set it and the whole journey is timed at that figure instead — the distance divided by the number you chose, spread along the route — so a route planned once and replayed with the same number is sent at the same pace each time.

Drive mode has one extra control that walk mode does not: a traffic chip beside the slider, which hands the pace back to the routing service's own estimate for that route. It is how you get back to the driving default after typing a figure. Walk mode has no equivalent chip, so once you have moved the walking slider there is no button that returns it to the 1.4 m/s default — reopen the app, or plan the route without touching the slider. That is a gap on our side rather than something you are doing wrong, and it is written down as KI-1002.

This page said the opposite until 2026-08-20, and it was wrong. It stated that there was no speed control in the application, and answered “can I change the speed?” with “no”. There is one, it is in the shipped build, and it always was. If you read that and went looking in a preferences pane, the control was never there — it is beside the route, and it only appears once you have planned one.

And the correction itself was wrong about the numbers, on the same day. It put both modes' lowest speeds at the figure the application clamps to internally rather than the figure the slider actually starts at, and it described preset buttons that are not there. Walking starts at 1.5 km/h, driving starts at 10 km/h, and the only chip beside the slider is traffic, in drive mode. The figures on this page are now read out of the application's own source by a check that fails the build when they disagree, which is what should have been true the first time.

If you want to control the movement yourself rather than follow a route, that is what the joystick is for — you push it and the position goes where you push, at a speed you set by how far you push it.

03Setting one up

01Connect the iPhone and select it

Same starting point as everything else. If the phone is not in the device list, start at GPSLarp can't find my iPhone.

02Choose walk or drive

The two modes differ only in how the timing is worked out. Both follow real street geometry; walk imposes a constant pace on it, drive takes the pace from the route.

03Set the start and the end

The route card carries a field for each: a Start and an End, either of which takes an address typed straight into it. The first click on the map drops the start; every click after that moves the end, and the route is worked out again as soon as it does — so a destination chosen by mistake costs one more click rather than starting over. A Swap button reverses the two. Setting an exact latitude and longitude covers the details, including what happens when a typed coordinate pair does not resolve.

Or more than two, with the multi-stop toggle. The route panel carries a button that switches multi-stop on, and the map then takes a click for each stop in the order you click them — the legs are joined into one continuous journey rather than several separate ones. Planning a route with several stops covers it properly, including what happens when one leg cannot be routed.

04Pick a route if you are offered a choice

Up to two alternatives may come back for the same pair of points. They are different roads and therefore different distances, which is one of the two things that decide how long the journey lasts; the speed control in section 02 is the other.

Corrected 2026-08-20 (Rule 4). This paragraph ended “which — since you cannot change the speed — is the one thing that decides how long the journey lasts”, and was left behind when the rest of the page stopped saying there was no speed control. It is the same false claim in a subordinate clause, which is where it survived a correction pass.

05Start it, and leave the Mac alone

Once it is running, the Mac is doing the work for as long as the journey lasts. Stop the journey from GPSLarp when you have finished, or see putting the real location back, which covers every way of ending it.

Screenshot pending — a journey part-way along its route
The position advances along the track from the Mac. Nothing is playing on the phone by itself.

04What it needs and what it costs

It needs the internet, twice over. Once for the map, and once for the route itself — there is no offline routing. What still works without a connection is on using GPSLarp without an internet connection.

Planning a route tells somebody else where you are going. The two endpoints are sent to a public routing service run by a third party in order to get the geometry back. That is a real privacy consequence and it is worth naming rather than burying: the service sees the pair of points. And because walk and drive ask different services, the mode you pick decides which organisation that is — the same journey planned twice, once each way, is disclosed to two of them. The privacy policy lists the services the app contacts directly from your machine, and What does GPSLarp send from my Mac? names them.

Every account gets one free walk and one free drive. They are counted separately — using the free walk leaves the free drive intact. What you get without paying has the whole arrangement.