A complete public guide to every Flyover Map 3D input, mode, and render setting.
How to use the app from start to finish
This page is available before login and after login. It documents the current controls on the main render form, the options inside Advanced Customization, and the request parameters generated by the app.
- Enter an origin and destination, or enter one center point for orbit mode.
- Choose a route mode, texture, season, duration, quality, and output format.
- Optionally add stops and waypoint images for driving or straight-line routes.
- Submit the job and let the renderer continue in the background.
- Return later from your account history or the completion link when the MP4 is ready.
Route setup parameters
These are the inputs users work with first.
| Control | Options or format | What it does |
|---|---|---|
| Origin | Place name or typed coordinates such as 49.2827, -123.1207 |
Sets the start point for driving/direct routes, or the center point for orbit mode. The underlying values are origin, origin_lat, and origin_lon. The hidden latitude and longitude fields are filled automatically when a suggestion is selected. |
| Destination | Place name or typed coordinates | Sets the end point for driving/direct routes. The underlying values are destination, destination_lat, and destination_lon. This field is hidden in orbit mode because orbit uses a single center point. |
| Origin image | .jpg, .jpeg, .png, .webp |
Shows a photo overlay when the animation reaches the origin waypoint. The uploaded file is sent as origin_image. Available only for driving and straight-line routes. |
| Destination image | .jpg, .jpeg, .png, .webp |
Shows a photo overlay when the animation reaches the destination waypoint. The uploaded file is sent as destination_image. Hidden in orbit mode. |
| Stops | Any number of intermediate stops, each with an optional image | Adds ordered intermediate waypoints between origin and destination. Each stop uses fields such as stop_0_label, stop_0_lat, stop_0_lon, and stop_0_image, then repeats that pattern for additional rows. |
| Route file upload | GPX or JSON route file | Uploads a prebuilt path instead of using origin and destination lookups. The file is sent as file. GPX files are converted into the app's internal JSON point format before processing. Uploaded route files cannot be combined with stops or waypoint images. |
Advanced customization
These settings change how the flyover is generated and how the output is framed.
| Control | Options | Explanation |
|---|---|---|
| Route Mode | driving, direct, orbit |
driving follows roads through OpenRouteService. direct connects waypoints with straight segments. orbit creates a circular flyover around one center point. The selected value is sent as route_mode. |
| Orbit Radius | 10 to 200 km, whole-number input in the UI | Only used in orbit mode. It controls the orbit circle size and also drives credit deduction with the formula 2πr km. The submitted value is orbit_radius_km. |
| Terrain Texture | satellite, landcover, landsat, hillshade, dem |
Changes the surface look of the terrain. Satellite is the default realistic map texture. The others emphasize land use, infrared color, terrain shading, or elevation coloring. The selected value is sent as texture_mode. |
| Date Window | jun_aug, sep_nov, dec_feb, mar_may |
Selects the seasonal imagery window. This mainly affects satellite-style renderings and helps bias the map toward green summer, autumn tones, snow, or spring. The selected value is sent as date_window. |
| Video Quality | 480, 720, 1080 |
Chooses the base output size. The app combines this with the selected format to compute the final video_width and video_height sent to the backend. |
| Duration | 5 to 60 seconds in the UI | Sets total animation length. The submitted value is duration. The backend rejects values above 60 seconds. |
| Format | vertical 9:16, tall 4:5, square 1:1, wide 16:9 |
Changes the aspect ratio of the final MP4 for social, web, or presentation use cases. Combined with quality, it determines video_width and video_height. |
Mode behavior and restrictions
Some options only work in specific route modes.
Driving
Uses road routing between the selected points. Stops and waypoint images are supported.
Credit estimate on the form is shown as a straight-line baseline with a + because the actual charged distance follows the routed road path.
Straight Line
Connects origin, stops, and destination with direct segments. This is useful for conceptual paths, flight lines, or routes where roads are not relevant.
Stops and waypoint images are supported.
Orbit
Uses the origin field as the center point. Destination, stops, and waypoint images are disabled in this mode.
Radius must stay between 10 and 200 km.
Route File Upload
Use either a route file or typed locations, not both. Uploaded route files also cannot be combined with stops or waypoint images.
GPX uploads read track points first, then route points, then waypoints if needed. Uploaded paths are stored and processed as a non-orbit route.
Output resolution reference
The app computes final dimensions from your selected format and quality.
| Format | 480 option | 720 option | 1080 option |
|---|---|---|---|
| Wide 16:9 | 854 × 480 | 1280 × 720 | 1920 × 1080 |
| Vertical 9:16 | 480 × 854 | 720 × 1280 | 1080 × 1920 |
| Tall 4:5 | 480 × 600 | 720 × 900 | 1080 × 1350 |
| Square 1:1 | 480 × 480 | 720 × 720 | 1080 × 1080 |
Credit packages and billing
Credit purchases are processed through Stripe and priced in USD.
Current packages
100 km for $6.99 USD
200 km for $11.99 USD
300 km for $15.99 USD
How credits work
Credits are added after a successful Stripe payment. If a job fails and no video is delivered, the used credits are automatically refunded.
Completed jobs are non-refundable unless required by law.
Route file formats
You can upload either a GPX file or a JSON route file. JSON uploads should use an array of points with at least two entries.
[
{ "lon": -123.1207, "lat": 49.2827, "profile": "driving" },
{ "lon": -123.1132, "lat": 49.2798, "profile": "driving" },
{ "lon": -123.1054, "lat": 49.2761, "profile": "walking" }
]lon and lat. Optional key: profile. If profile is omitted, it defaults to driving. Extra keys are preserved in the route payload.
trkpt), route points (rtept), or waypoint points (wpt). The upload needs at least two points.
Credit and processing rules
These rules affect what users should expect after pressing Generate Video.
Credit deduction
- Driving charges the routed road distance.
- Straight Line charges the direct segment distance through all selected points.
- Orbit charges
2πrkm using the selected radius.
Background processing
After submission the job keeps running in the background. Users can close the page and return later; the app stores the active job state locally and also shows finished renders in history.
Autocomplete behavior
Location suggestions appear after about three typed characters. Selecting a suggestion fills the hidden latitude and longitude fields for a more reliable route request.
Login requirement
This tutorial page is public, but actual rendering still requires a signed-in account with available credits.