Creating a Roadbook from GPX files with Openstreetmap data ?

Detailed Analysis

A Reddit user posting to r/ClaudeAI has raised an applied use case for Claude centered on cycling route planning, specifically the construction of a "roadbook" — a structured navigational document used in long-distance randonneuring — derived from GPX (GPS Exchange Format) files enriched with OpenStreetMap data. The user intends to cycle across Europe along designated cycleways and original paths, and seeks to integrate contextual point-of-interest (POI) data including elevation profiles, drinking water sources, restrooms, churches, and museums located within a five-kilometer corridor of a given GPX trace. The post represents an early-stage inquiry, with the user soliciting prompt engineering examples and optimization strategies from the community.

The use case highlights a meaningful intersection between Claude's language and reasoning capabilities and structured geospatial data workflows. GPX files are XML-based and parseable, meaning Claude can in principle ingest raw route data and transform it into formatted, human-readable navigational documents. When combined with OpenStreetMap's open-access geographic database — which catalogues infrastructure, amenities, and landmarks at granular levels — the workflow the user envisions would require Claude to synthesize coordinate data, proximity filtering, and categorical POI classification into a coherent, stage-by-stage document. This is a non-trivial task that touches on data parsing, geographic reasoning, and document generation simultaneously.

The query reflects a broader trend in the Claude user community: leveraging the model not merely for text generation but as an orchestration layer for structured, domain-specific workflows that previously required dedicated software pipelines. Randonneuring roadbooks have historically been produced with specialized tools or manual cartographic effort; the idea of using a general-purpose AI assistant to automate their creation from raw GPS data represents a democratization of technical capability for hobbyist and semi-professional cyclists alike. The five-kilometer corridor specification, in particular, implies a need for spatial buffering logic — something that would typically require GIS software — which Claude could approximate through coordinate bounding-box calculations or by directing API calls to Overpass API, OpenStreetMap's query interface.

From a prompt engineering standpoint, the user's challenge is characteristic of multi-step agentic tasks: the optimal approach would likely involve chaining prompts that first parse and segment the GPX route into logical stages, then query or simulate OSM data retrieval for each segment, and finally format outputs into a standardized roadbook template. Community members experienced with Claude's structured output capabilities and tool-use patterns — particularly those familiar with function calling or code execution for geospatial tasks — would be well-positioned to offer the example prompts the user is seeking. The post underscores how non-English-speaking technical users are actively integrating Claude into niche, real-world planning tasks, expanding the model's practical footprint well beyond conventional writing or coding assistance.