While existing tools are excellent for searching out permament RUSA routes for riding, I wanted to examine the riding history of the club. RandoVisual thus makes no effort to render or display all possible routes and will likely never build a listing of routes or search-oriented tools. Instead it tries to answer the question: "what have we collectively done?".

Secondarily, thanks to no small part to my dayjob I have an interest in exploring techniques to make exploring very large datasets blazing fast. RandoVisual thus serves as an outlet for experimentation of technique.

TODO :)

• capture further metadata about routes from rusa
• don't refetch from rwgps if we already have the route data
• move db to a serverless db
• deploy to cloud
• provide some basic on-click details about the routes
• cache the tiler so we don't crush the db network egress
• use PMTiles to not even need to dynamically tile anything
• poke RUSA about whether this is possible to do for brevets
• provide some FE filtering
  • start with changing year this way rather than via query param
  • distance
  • # of riders
• improve route info panel
• use TripsLayer to show routes populate over time
• render 3d maps of the routes at high zooms
• colorize routes based on rides done in that year
• move FE assets to a CDN
• build a new BE extractor to grab ride by year or month rather than by rider
• bug: non-visible routes can prevent selecting visible routes
• highlight and show route info on hover
• add CD
• add CI, tests, linting

• 9 December 2025
  • Don't render (rather than just don't show) filtered-out routes.
  • Add a filter for # of riders.
  • Add links to RWGPS.