# Read animated maps in iCouldPlay: separate map panning from marker movement

Language: en
Canonical: [Read animated maps in iCouldPlay: separate map panning from marker movement](<https://allluckly.cn/en/guides/icouldplay-animated-map-pan-marker-relative-position/>)
中文：[中文 HTML](<https://allluckly.cn/guides/icouldplay-animated-map-pan-marker-relative-position/>)
English: [English HTML](<https://allluckly.cn/en/guides/icouldplay-animated-map-pan-marker-relative-position/>)
Published: 2026-11-11T00:00:00+08:00
Modified: 2026-11-11T09:40:26+08:00
Author: Bison

Use two fixed landmarks and three moments to record screen coordinates, relative position and scale changes without deriving real speed from pixels.

English translation of the [Chinese original](<https://allluckly.cn/guides/icouldplay-animated-map-pan-marker-relative-position/>), translated on 2026-11-11. Original publication dates, attribution, code and version notes are retained.

A marker sliding left in an animated map does not necessarily mean westward movement: the view may be panning. Watch lawful map material or an original illustration in iCouldPlay and use fixed landmarks to separate screen position from map-relative relations. Records are manual; no map tracking, coordinate recognition or geographic measurement is assumed. Pixel values below define a paper example. Leave observations untested if no corresponding video is made.

## Distinguish the map view from player display

Record video name, version, duration, source and display mode, then locate map north indicator, scale information and legend. Keep player display mode, device orientation and speed fixed, checking for cropping. Panning within source map imagery differs from the player cropping the whole video. Record visible extent when boundaries are absent rather than inventing a scale bar. Choose two fixed landmarks, school A and bridge B, not moving vehicle icons. These invented labels are positions in this illustration, not real geographic information or navigation guidance.

## Specify the original three-moment example

Use a north-up, unrotated, constant-zoom 2D paper plan, comparing horizontal coordinates only in pixels. At0s school A is x=200, bridge B x=500 and red marker x=300; at2s they are100,400,200; at4s100,400,260. Keep one frame/display size and unchanged vertical relations. Without animation production, arrange three paper panels and label them a plan, not an iCouldPlay test. Measure x from the image’s left edge; a temporary left/right convention is not longitude, and north-up does not establish projection or scale units.

## Check common panning through landmark spacing

From0 to2s school and bridge both shift100px left while separation stays500−200=400−100=300. The marker also moves300→200,100px left, while its offset from school remains100. In this known translation-only illustration, common sliding does not mean the marker left its map position. Record screen displacement−100 and unchanged relative offset separately, not “travels100 metres west.” In real footage, leave identity unresolved if landmarks change version, merely share names or a cut introduces another map; similar labels do not establish continuous motion.

## Then inspect marker movement relative to landmarks

From2 to4s landmark coordinates and300px separation stay fixed. The marker moves200→260, its school offset100→160, an increase of60px. Because scale and orientation are explicitly fixed, this supports rightward map-relative movement in this illustration. Dividing60 by2 does not establish30 real metres per second: pixels are not metres and two file seconds may represent compressed story time. Separate calculable screen change from missing ground distance and real time. If coordinates are unreadable, record only visible relative trends without invented precision.

## Rebuild comparisons after zoom or rotation

Growing separation between fixed landmarks may indicate map zoom or player display change, so do not reuse an earlier per-pixel interpretation. A rotating north indicator also changes the geographic meaning of screen-right. Record spacing, north, scale information and cropping for each segment. Establish and label a new reference if landmarks disappear. Two landmarks reveal some view changes, not absence of every tilt, perspective effect or local distortion. Stop precise pixel conversion in complex3D scenes, retaining anchors and unknowns rather than treating mapping-software measurement controls as iCouldPlay controls.

## Retain reference points during playback and replay

Watch normally first, then use available pause/seek controls at three content anchors. With whole-second timing, retain approximate times plus school/bridge states rather than claiming exact frames. Verify the same version, map and display mode on replay; temporarily disable optional captions obscuring landmarks and restore them. Record a frozen map with jumping marker and whether sound continues without instantly diagnosing teleportation or network failure. A screenshot records display output; later scaling/sharing may change pixel scale. Do not combine screenshot and original-video coordinates without checking.

## Leave unknown scale and real speed unresolved

Retain file time, A/B identities, screen positions, landmark separation, marker-to-A offset, scale and orientation status. Record unchanged offset at0–2s and an increase of60 at2–4s separately rather than one whole-video verdict. Without reliable ground scale or real-time mapping, distance and speed remain unknown, not zero; unknown does not mean stationary. If a scale bar exists, check that it updates with zoom and applies to the visible region before considering map measurement. This observation task does not recover real trajectories, coordinates or vehicle operating data.

## Reopen and explain conclusions through relative relations

Reopen the same file and play from a segment showing school and bridge clearly, checking notes against the picture. Preserve first notes and state whether a correction concerns version, view or transcribed coordinates; restore normal captions/display. Explain how common panning can cause screen-left movement and what fixed conditions support marker-relative change, rather than reciting numbers. A new map needs new landmarks and scale evidence, not the example’s300px separation. Submit a paper deduction if no sample was made, not a test report or claimed automatic tracking/geolocation verification.

## Related tutorials and sources

[Compare moving edges and display cadence in iCouldPlay](<https://allluckly.cn/en/guides/icouldplay-pan-motion-artifact-comparison/>); [iCouldPlay animated charts: recheck axes and labels at each observation point](<https://allluckly.cn/en/guides/icouldplay-animated-chart-changing-axis-record/>).

Sources checked on 11 November 2026: the [official iCouldPlay App Store listing](<https://apps.apple.com/cn/app/id6755653178>) and [Apple Lookup](<https://itunes.apple.com/lookup?id=6755653178&country=cn>) show version 1.1.1, requiring iOS / iPadOS 15.0 or later. This workflow uses ordinary playback and manual records through controls actually present. External editing and sample creation are not newly promised iCouldPlay features. Confirm capabilities against installed version, engine and source. Examples and plans are not step-by-step device tests or guarantees about every device.

Concept references: [USGS on map scale](<https://www.usgs.gov/publications/map-scales>) distinguishes map and ground distance; [Esri map and scene navigation](<https://doc.esri.com/en/arcgis-pro/latest/get-started/navigate-your-data.html>) distinguishes pan, zoom and rotation. These sources describe map concepts, not built-in iCouldPlay map tools. All three-moment coordinates are original.