|
33 | 33 | (clerk/col
|
34 | 34 | (clerk/with-viewer diagram/plan-viewer example-plan)))))
|
35 | 35 |
|
36 |
| -;; **rando-planner**: |
37 | 36 |
|
38 |
| -;; - allows users to break down the route with more control, providing |
39 |
| -;; visualization tools that help evaluating and comparing different |
40 |
| -;; plans |
| 37 | +;; When planning a long-distance bike ride, you face two main |
| 38 | +;; challenges: determining the route from point A to B, and organizing |
| 39 | +;; your journey—deciding how much distance to cover each day, when to |
| 40 | +;; take breaks, and where to refuel. Traditional route planners, such |
| 41 | +;; as Komoot, Strava, and Cycle.travel, primarily address the first |
| 42 | +;; challenge: designing the route. |
41 | 43 |
|
42 |
| -;; - assumes the user already has a GPX track defined (provided for |
43 |
| -;; example by the organizers of a bike event), and let the user plan |
44 |
| -;; the daily effort to a higher granularity. |
| 44 | +;; Komoot includes a tool for dividing the route into multiple days, |
| 45 | +;; but it simply distributes the distance evenly across |
| 46 | +;; them. Cycle.travel, on the other hand, allows users to break the |
| 47 | +;; route at specific points and even helps locate accommodations for |
| 48 | +;; overnight stays. |
45 | 49 |
|
46 |
| -;; - is based on Clerk, a notebook library for Clojure |
| 50 | +;; Rando-planner takes a different approach. It assumes you already |
| 51 | +;; have a GPX file of your route and focuses exclusively on the second |
| 52 | +;; challenge: planning your journey in detail. |
47 | 53 |
|
48 |
| -;; Traditional tools (such as Komoot, Strava, Cycle.travel, etc.) |
49 |
| -;; focus on planning the route itself. Komoot offers an extra tool to |
50 |
| -;; divide the route into multiple days, but they distribute distance |
51 |
| -;; uniformly across the days. Cycle.travel allows to break down the |
52 |
| -;; route at arbitrary points (and helps finding accomodation for the |
53 |
| -;; night). |
| 54 | +;; With rando-planner, users can divide the route into individual |
| 55 | +;; activities or daily plans. The tool provides visualization tools to |
| 56 | +;; assess daily effort with greater precision and compare various |
| 57 | +;; strategies for covering the distance effectively. |
54 | 58 |
|
55 |
| -;; rando-planner provides different types of visualization that can be |
56 |
| -;; used to study different strategies to cover the distance. |
57 | 59 |
|
58 | 60 | ;; This page has been composed with Clerk and rando-planner
|
59 | 61 |
|
|
63 | 65 |
|
64 | 66 | ;; ## Features
|
65 | 67 |
|
66 |
| -;; - Schematic visualization of the plan, that includes: |
67 |
| -;; - running count of kilometers |
68 |
| -;; - elevation |
69 |
| -;; - scheduled pauses |
70 |
| -;; - total amount of kilometers accumulated every day |
71 |
| -;; - sunrise and sunset indicators (WIP) |
72 |
| - |
73 |
| -;; - Map visualization (based |
74 |
| -;; on [Leaflet](https://github.com/Leaflet/Leaflet)) of the route, |
75 |
| -;; with markers corresponding to the location reached after each day |
76 |
| -;; is completed. |
| 68 | +;; - Schematic Visualization of the Plan |
| 69 | +;; - Displays a comprehensive overview of your route, including: |
| 70 | +;; - Running count of kilometers. |
| 71 | +;; - Elevation profile. |
| 72 | +;; - Scheduled pauses. |
| 73 | +;; - Total distance accumulated daily. |
| 74 | +;; - Sunrise and sunset indicators (currently a work in progress). |
| 75 | +;; - Daily Elevation Visualization |
| 76 | +;; - Provides a focused view of the elevation profile for each day, helping you gauge the effort required for specific segments of the route. |
| 77 | +;; - Map Visualization |
| 78 | +;; - Interactive mapping powered by Leaflet. |
| 79 | +;; - Highlights the route with markers indicating the location reached at the end of each day. |
77 | 80 |
|
78 | 81 | ;; ## Usage example
|
79 | 82 |
|
@@ -226,7 +229,7 @@ be morale-crushing."]])
|
226 | 229 | ;; end of the first day. Intermediate markers, when clicked, display a
|
227 | 230 | ;; popup that shows the label of the day that _ends_ there, and the
|
228 | 231 | ;; amount of kilometers planned for that day. With this information,
|
229 |
| -;; you can use other tools to find accomodation or other services |
| 232 | +;; you can use other tools to find accommodation or other services |
230 | 233 | ;; you're going to need on the road.
|
231 | 234 |
|
232 | 235 | ;; Here the new map, this time displayed taking advantage of all the
|
@@ -258,18 +261,24 @@ be morale-crushing."]])
|
258 | 261 | ;; - `:gpx`: This key refers to the location of a GPX (GPS Exchange
|
259 | 262 | ;; Format) file
|
260 | 263 |
|
261 |
| -;; - `:average-speed`: This key represents the average speed |
262 |
| -;; maintained during the activities. The value associated with this |
263 |
| -;; key is expected to be a numerical value denoting speed, expressed |
264 |
| -;; as km/h |
| 264 | +;; - `:average-speed` [Optional]: When appears only at this level, |
| 265 | +;; this key represents the average speed maintained during all the |
| 266 | +;; activities. The value associated with this key is expected to be |
| 267 | +;; a numerical value denoting speed, expressed as km/h. If |
| 268 | +;; `:average-speed` is used in a daily-plan (see below) then that |
| 269 | +;; value overrides this option. |
265 | 270 |
|
266 |
| -;; - `:daily-plans`: This key holds a vector of daily plans. Each |
267 |
| -;; daily plan is represented as a map containing information about |
268 |
| -;; activities planned for a single day. Inside each element in the |
269 |
| -;; vector: |
| 271 | +;; - `:daily-plans` [Optional]: This key holds a vector of daily |
| 272 | +;; plans. If no daily-plans is provided, rando-planner will use a |
| 273 | +;; default value (one single activity, long enough to cover the |
| 274 | +;; entire distance). Each daily plan is represented as a map |
| 275 | +;; containing information about activities planned for a single |
| 276 | +;; day. Inside each element in the vector: |
270 | 277 |
|
271 | 278 | ;; - `:date`: This key denotes the date of the daily plan in the format "YYYY-MM-DD". It is used to compute the sun rise and set times.
|
272 | 279 | ;; - `:label`: An arbitrary string, a label or description of the daily plan
|
| 280 | +;; - `:average-speed' [Optional]: The value associated with this key is expected to be |
| 281 | +;; a numerical value denoting speed, expressed as km/h. |
273 | 282 | ;; - `:activities`: This key holds a vector of activities planned for the day. Each activity is represented as a map containing:
|
274 | 283 | ;; - `:start`: This key denotes the starting time of an activity, in the format "HH:mm"
|
275 | 284 | ;; - `:type`: This key specifies the type of activity. At the moment only the type "ride" is in use. This key is reserved for future uses
|
|
0 commit comments