curviness
Find better roads. Navigate with Google Maps.
Plan your drive
Tap to select your current position as the starting point.
Enter a town or address. We will resolve it before planning.
Road quality is checked automatically. Known poor or unpaved surfaces are excluded where supported by available data; unknown road conditions are labelled UNVERIFIED, never assumed to be good.
Speed-limit preferences use mapped OpenStreetMap maxspeed tags where available. They favour alternatives, but are not guarantees; access roads and starting/finishing areas may be unavoidable. Always obey posted limits.
Preparing…
Show full activity log
Road data is cached for up to 6 hours. Failed OSM endpoints are briefly paused rather than repeatedly retried. Timeouts remain UNVERIFIED, never passed.
JavaScript has not started. Open this as a hosted HTTPS website in Safari.
Calculated route options
Alternatives must differ by at least 1 km AND 10 minutes AND have at most 40% shared road geometry with every earlier choice. When insufficient distinct routes exist, fewer than three are shown. Shared road percentages are approximate (50 m grid), not exact OSM road IDs. These cards only show real routing results. Distance and duration come from a road-routing service. Elevation is estimated from terrain samples. No offline or invented route scores.
The map will show the selected route.
Tap “Find my drive” to calculate routes. Time and distance create single-loop circular drives; Destination creates a one-way drive.
Road-quality sources
Online evidence engine — OSM is queried live when available. The La Rioja official road inventory is a cached, historic regional record; it is not a real-time inspection. Other countries require compatible data imports and are not yet covered by government records.
View evidence sources and limits
Route quality & limitations
Route diversity is enforced after ranking: each accepted alternative must differ by at least 1 km and 10 minutes from every selected route, with no more than 40% overlap of approximate road geometry. Fewer than three results is expected when the search does not produce enough distinct, road-quality-acceptable routes. Adaptive candidate directions are generated from a catalogue of towns in La Rioja and nearby Burgos, with extra mountain-road candidates when curviness is high, then tested on real roads; the app ranks calculated routes against the time/distance target, curviness preference. Elevation is displayed for information and does not affect ranking. Optional town stops are tested against new live road routes; they are removed only when this measurably reduces out-and-back driving without making the route too short. Remaining retraced road is penalised heavily in ranking. Preview always shows the final road-provider geometry, not an artificially shortened line. Curviness now changes candidate search priority as well as scoring; it does not guarantee a different result if only one route passes the other hard constraints. A 75% slider is a search preference, not a promise of 75/100 route curviness. Driving time is a hard ±20% constraint; longer candidates may be shortened by removing a waypoint before rejection (e.g. 72–108 min for 90 requested); candidates outside it are rejected and clearly counted. Circular drives must pass the single-loop check: once the route has departed the starting area, it may not return there until the final approach. Violations are rejected and counted in the activity log. The app scores sustained direction changes and penalises long straight sections at high curviness settings; it is still not exhaustive road-segment graph optimisation. Public endpoints may be rate-limited or block requests. The service can fail without implying that your iPhone is broken.
Avoid motorway/toll preferences are requested where supported; fallback providers may not honour them. Quiet roads are approximated using a rural waypoint bias, not real traffic. Road quality is checked against available OpenStreetMap tags; if the live service is unavailable routes are displayed as UNVERIFIED, not approved. Missing tags are UNKNOWN and no guarantee of smooth tarmac is made. The historical LR-207 report is retained as contextual evidence only: its approximate corridor is NOT used to reject otherwise valid roads. Only suitably georeferenced mapped bad sections can trigger road-quality rejection. Missing observations mean UNVERIFIED. Police enforcement, road closures and real-time traffic are NOT assessed. Curviness automatically supplies up to nine route-shaping waypoints, with no waypoint controls in the interface. Some mobile browsers support only three, and the app cannot verify which waypoints Google Maps actually accepts; Google Maps can recalculate between them. Download GPX to preserve exact calculated geometry. Always follow actual road signs and conditions.
Road-quality tags: © OpenStreetMap contributors (ODbL); public Overpass API availability varies. Road data: © OpenStreetMap contributors. Elevation: Open-Meteo / Copernicus DEM GLO-90 (approx. 90 m resolution). Test only; public routing APIs are not a production backend.