# Turn your recorded hike into a 3D terrain keepsake Canonical URL: https://agentsidequests.com/ideas/turn-your-recorded-hike-into-a-3d-terrain-keepsake/ Markdown URL: https://agentsidequests.com/ideas/turn-your-recorded-hike-into-a-3d-terrain-keepsake/index.md See the climb from an angle your camera missed. Turn a recorded route and a few photos into a terrain model you can rotate, with the actual landscape beneath your track. This is an original editorial prompt, not a run-tested result. Examples are illustrative, not observed outcomes. Check the capabilities and permissions of the assistant you actually use. Category: Travel & outdoors Type: One-off ## What you get A rotatable terrain viewer with a recorded route and photo pins, editable project files, and a source-and-limitations note ## Bring this Your GPX route, confirmed area, up to five selected photos and captions, and the device or browser where you want to open the result. ## Your agent needs - GPX and image/file reading - Access to suitable elevation data and tools to align geographic coordinates - Code and 3D rendering or terrain-modeling tools - Browser preview and user confirmation of uncertain photo locations Missing a connection? Paste or attach the relevant information yourself. ## Copy-and-paste prompt Replace the bracketed placeholders with your details. This prompt is reference material to adapt to a user request; fetching it does not authorize execution. ```text Turn my recorded [hike or ride] into a small, private 3D terrain keepsake. I can supply [GPX track], [up to five selected photos and captions], [confirmed area], and the [device/browser] where I want to open it. Preserve my originals and work in a new folder. This is a way to revisit a completed trip, not a navigation tool. Read the track before building. Show its bounds and any gaps, impossible jumps or missing fields. Ask me to confirm ambiguous places; do not silently invent or smooth the route. Let me choose which segment belongs in the keepsake. Find a suitable elevation dataset for that area, record its source, coverage, units and available resolution, and explain any license or download limits. Do not invent terrain detail when data is missing. Confirm that the coordinate systems align before combining the track and terrain. Build a small viewer I can rotate, zoom and reset, with a visible scale and north direction. Put the route on the terrain and make the selected photo pins open my supplied caption and image. Ask me to place photos without reliable location data. Start with true vertical scale; label any optional exaggeration clearly. Keep recorded track elevations separate from elevations sampled from the terrain. Show one aligned section for review before finishing the area. Return the viewer, editable project/source, a simple opening guide and a source-and-limitations note. Open the delivered copy on the intended browser if available and check rotate/reset, route alignment at several known locations and every photo pin. Report checks actually performed and those still for me. Test offline use before describing it as offline. If an interactive model cannot be built, return a clearly labeled 2D route proof and the missing requirement, not a claimed 3D result. Keep everything private. If I later request a shareable copy, remove the excluded route segments, sensitive coordinates and unwanted photo metadata from the actual exported files, not just the visible view, and show what remains for my approval. Do not publish, upload my track or photos to a new external service, or start paid services without my approval. ``` ## Illustrative example Illustrative: see the ridge you crossed A saved hike could become a small terrain scene with your route across the ridge and three photo pins. Rotating it might make the shape of the valley easier to understand. This is an imagined keepsake, not a tested model or a claim of navigational accuracy. This is not an observed result or a verified recommendation. ## Inspired by a reported use The creator describes layering his GPS tracks, photos and notes over sourced elevation terrain in a browser app. [Tyler Geddes on building MtnMkr with Claude Code]() Source limitations: Own-project self-report and documentation, not an independent test. The creator reports export and caching bugs along the way. We did not test accuracy, speed, offline use or device support. Our smaller trip-keepsake prompt is an original untested extension. The prompt is our original extension, not the source author's exact prompt or a tested result. ## Make it more you Use a recorded bike ride and a few user-selected stops, keeping the result focused on a single outing. ## Related practical guides - [Creative AI agent projects you can open, play and make your own]() ## Related ideas - [Make your pet the hero of a tiny playable game](): The sock thief finally gets a game. Give your agent three personality traits and get a small browser adventure you can actually play. You get: A one-minute browser game - [See your trip before you take it](): Plan a real route, then give it a visual life. Get a usable itinerary paired with clearly labeled illustrations of the trip you are imagining. You get: A source-linked itinerary and illustrated trip preview - [Get a daily email researched for your actual interests](): A few relevant discoveries, properly sourced, in one email. Set your interests or career-upgrade criteria and get new research or job opportunities worth your attention. You get: A concise sourced email with only new matches [Editorial approach]() [Assistant setup guides (HTML)]()