The screens

The path map

The shadow path drawn on a real map, corrected for terrain.

The path map draws the same shadow geometry as the flat plot, but on real ground — so you can see which roads, ridges and clearings the path actually crosses. Open it with View Path Map on Event Detail, or by tapping the globe or plot on a Search Events result.

What the lines mean

The green line is the centre line. The two blue lines are the shadow edges, with the band between them shaded. The red lines are the uncertainty limits — the path could plausibly fall anywhere between them.

The grey lines are announced stations, each drawn as the chord that observer will see, with their station name written along it.

The telescope marker is a station's actual position. The blue dot, as everywhere, is you.

The path map over Sydney showing the shadow band, centre line, sigma limits and three named station chords
Three observers on this event, their chords labelled along the lines.
Tip

The station names follow the chords as you pan, staying in view rather than scrolling off with the line. If you would rather not have them, Hide Chord Names in Settings turns them off.

Shape models

For some asteroids the real shape is known — from the DAMIT and ISAM databases, built from lightcurve, spacecraft or radar data. When one exists, the map draws the asteroid's actual silhouette on the ground instead of leaving you to imagine it from the band alone: a real footprint, not a generic oval.

The badge above the silhouette names the source and model — DAMIT 6114, say, or ISAM 1046-1. A long press on it shows the model's quality; most published models are the best-determined grade, but not all.

2000 ET65's flat, elongated DAMIT 14904 silhouette drawn near the shadow band over the Blue Mountains, with the badge naming the model
The silhouette follows the map as you pan, exactly like the shadow band above it.
Choose shape model sheet listing DAMIT and ISAM entries for the asteroid, with the server's preferred one marked
Only shown when an asteroid has more than one published model.

Tap the badge, or the footprint itself, to see more. Most asteroids have exactly one model, so this jumps straight to the rotation preview below. Where several exist — different pole solutions, or a radar shape alongside a lightcurve one — a chevron on the badge hints there is a choice, and tapping opens Choose shape model first.

Preview rotation during event opens a larger, shaded view of the body. A slider lets you scrub through its attitude across the event's own timing — from before to after closest approach — so you can see how the body's own rotation, not just the ground track, shapes the chord you would actually time.

Rotation preview dialog for DAMIT 14903, a wedge-shaped model, with the slider dragged to +0.13h from closest approach
Dragging the slider re-projects the body at that point in the event, not just rotates a picture.
Worth knowing

Most events have no shape model at all — DAMIT and ISAM between them cover a fraction of the asteroids that get occultation events. For those the map still draws a plain outline sized to the predicted shadow, just with no badge and nothing to tap. That is normal, not a sign that anything failed to load.

Location permission

Android asking whether OW Mobile may access the device location, with Precise and Approximate options
Choose Precise — an approximate fix is not much use for occultation timing.

The first time you open the map, Android asks for location access. It is used to show where you are relative to the path, and to offer to move a station to your current position.

Declining is fine — the map still draws the path, you just do not appear on it.

Map layers

The layers button offers Map, Satellite and Terrain. Satellite is usually the most useful for judging a site: you can see tree cover, clearings and whether a promising-looking road is actually a track.

Your choice is remembered for the next map you open.

The layer menu offering Map, Satellite and Terrain
The current layer is marked.
The same path over satellite imagery, with the chord names now in amber
Over imagery the chord names turn amber, so they are not mistaken for Google's own white place labels.

Terrain correction

A shadow path is computed for a smooth Earth. The real ground is not smooth, and over mountains the difference is large enough to matter — a ridge a kilometre high shifts where the shadow edge actually falls.

Straight path lines crossing a mountainous region
Before: dead straight, as if the mountains were not there.

The app corrects for this, but the fine correction needs real elevation data for the area, which is downloaded on demand.

The terrain icon at the bottom left tells you where you stand. A small mark on the icon itself says which: a red cross means fine data is available for this area but not yet downloaded (the icon itself is grey); a green tick means the correction is applied to what you are looking at (the icon itself is blue).

The terrain icon in both states: grey with a red cross when correction is available but not applied, blue with a green tick once it is
Not applied yet, and applied — the icon's own colour and its small mark always agree.
  1. Zoom to the stretch of path you care about, until the terrain icon shows the red cross.
  2. Tap it. The app tells you which zone it needs and how large the download is.
  3. Accept. It downloads and applies itself — no need to tap anything else.
Dialog asking whether to download the elevation zone, naming the zone and its size
It names the zone and the size before committing you to the download.
Download progress dialog showing a percentage and a Cancel button
Cancelling leaves the path drawn as it was — nothing is half-applied.

The result is worth the wait in country like this. The lines bend and kink as they cross each ridge and valley, because that is where the shadow edge genuinely falls.

Zoom further and the correction resolves into individual terrain features — the line steps across each gully.

The same view with the path lines now bending along the terrain
After: the same view, the same lines, now following the ground.

How far the lines move depends entirely on the terrain underneath and the altitude of the star. A kilometre of relief can shift the shadow edge by a similar order — enough, here, to change whether a site well outside the naive straight-line path is actually inside it.

A 10 km view over New Zealand's South Island with the path lines swinging sharply off the straight prediction as they cross the Southern Alps
The same 10 km scale, a more dramatic case: over the Southern Alps the correction is not a gentle bend but a real swing.
Closer view showing the path lines deflecting around ridges
At 2 km you can see which ridges are doing the deflecting.

Corrections are applied to the part of the path you are looking at. Pan somewhere new within the downloaded zone and it follows; move outside it and the icon turns orange again, offering the next zone.

A one-time bubble points this out the first time fine data is available, and stops appearing once you have downloaded a zone.

Zoom right in and the correction resolves into individual features — the line steps across each gully and ridge, because that is where the shadow edge genuinely lands on the ground.

This is the level of detail that decides whether a particular roadside pull-off is inside the path or just outside it.

A very close view of a single path line kinking as it crosses ridges at 200 metre scale
At 200 m, one edge line stepping across the terrain.

Announcing a station from the map

Opened from a Search Events result you have not already announced a station for, the map can double as a way to pick a site: each of your Saved Sites is drawn as a tappable telescope marker, and tapping one announces a station there — no need to go back to the result tile.

Dialog asking to observe from a named saved site
It confirms the site by name before submitting.

This is off by default. On Map Station Selection in Settings turns it on — the ordinary route, the result tile's own Observe from… button, already covers observing from your single Home Site.

Managing downloaded zones and shape models

Zones stay on the phone so the correction is instant next time, and so it works with no signal in the field. Downloaded shape models are kept the same way, so a previously-viewed silhouette does not need refetching. Manage Downloaded Data in Settings lists both and what each is costing you in storage.

The zone covering your Home Site carries a padlock instead of a bin: it cannot be deleted, on the grounds that it is the area you are most likely to need. Shape models have no equivalent per-item list — just one total size and a single Delete for all of them.

Both are cleaned up automatically once old and unused enough, the same way, independently of each other.

The Manage Downloads screen: an Elevation Zones section listing two zones, one badged HOME SITE with a padlock, and a Shape Models section below with its own size and Delete button
Zone 47 is the Home Site zone, so it is protected. Zone 93 and the shape-model cache below can both be deleted.
Dialog asking whether to delete a downloaded elevation zone
Deleting asks first, and says what you would need to do to get it back.
Worth knowing

Deleting either loses nothing but the download. The path is still drawn, still corrected coarsely, shape footprints still show where DAMIT or ISAM has one, and anything deleted can be fetched again whenever you need it.