The symbolic view of the Ride Guide showed mostly roads rendered so as to suggest grade.
I often rode my bike over lunch while I worked for Wyatt Software. I wrote this HyperCard stack as an experiment in geographic representation. It traces the first few miles of my regular 18 mile route.
I was also riding regularly with the Portland Wheelmen and learned a lot of countryside from their maps. Here I was experimenting to see if I could make a better route map. I figured that you had to see past the horizon to really grok the route.
The View from 9th Avenue. Steinberg New Yorker Cover inspired my intentional distortion.
A series of photographs wouldn't work. So I drew a half dozen route sketches that looked beyond the line of sight, kinda like the New Yorker's view of the country that shows the Hudson river as about half way to California.
Roads were drawn to suggest grades. My ride was full of rolling hills. None were too high but they gave the ride its character.
Significant landmarks would show in ghostly outline with clarifying titles.
The arrows are buttons that advance through the stack. They also cue changes of direction and offer an occasional choice of route.
.
I try recreating the first scene of the ride guide using google draw. I thought I'd try InkScape but it was way more complicated.
My thought was that we could federate some "virtual" reality with pages of scenes and buttons connected to Mech behaviors.
.
We're surprised how much redundancy there is in the svg file google draw wrote. Maybe we can delete a lot of it?
pages/wyatt-ride-guide
.replaceAll(/stroke="#000000"/g,'') .replaceAll(/stroke="none"/g,'stroke="#000000"') .replaceAll(/stroke-width="1.0"/g,'') .replaceAll(/stroke-linejoin="round"/g,'') .replaceAll(/stroke-linecap="butt"/g,'') .replaceAll(/fill-rule="evenodd"/g,'') .replaceAll(/fill="#000000"/g,'') .replaceAll(/fill-opacity="0.0"/g,'') .replaceAll(/ +/g,' ') .replaceAll(/(\d)\.\d*/g,"$1") .replaceAll(/" \//g,'"/')
{org: 4976, short: 1393}
.
What would I need to learn if I wanted grab features from OSM and add them to a wiki page such that a locality might be render from a few adjacent pages by something I design independently? matrix 
You will need to think about what kind of POI would catch your interest the best, enumerate all of them and we could help you formulate the right filter. The output can be chosen to be either XML or a simple CSV with coordinates, name and kind of POI. post
- It shows four road segments, Meadows, Bagby, Bonita and Hall. - It show approximate elevation as uphill vs downhill and an overpass over the (unnamed) Interstate-5. - It shows two buildings, both close, not destinations, only way markers. - It shows distant hills in the abstract. Some rides went over those hills.
I am imagining that I would browse an OSM map, pick features and place them on a wiki page as structured data elements. I don't have a specific need, only curiosity.
Although certain features do contain an elevation key, it is not mandatory, so local coverage varies. incline=* is used quite often, though, useful in many cases for bicycling. Most renderers use public domain SRTM-based data for their elevation backdrops with contour lines.
I'll read up on Overpass and maybe mock up some canvas thing running on fake data. Then the remaining challenge is selecting features to include and tuning the rendering to look good. osm
You would also find these keys useful: lanes, lane_markings, width, sidewalk, kerb, surface, smoothness, track_type, sac_scale, visibility, colour, landuse, landcover, traffic_calming, crossing, oneway, busway, cycleway, highway, bridge, tunnel, layer, level.