$$\def\bold#1{\bf #1} \newcommand{\d}{\mathrm{d}}$$ BTP - Manual

#### Power Uphill

bike mass [kg]
body mass [kg]
altitude gain [m]
climb length [km]
time [s]
speed [km/h]
power [W]
power/mass [W/kg]
climbrate [m/min]

### BTP - Manual

The BergTourenPlaner (BTP, English: climb tour designer) is a offline tool to plan tours, estimated power output, estimate time tables for a given route, find tours with the highest/least altitude gain, find climbs and create 3D-views. BTP is an open source project combining open source road network data of OpenStreetMap and the SRTM3 digital elevation model of the NASA. The contents of climbindex.eu were generated with BTP.

#### Quick Start

• First you should download the program from the Download page and unzip it to any folder. The folder contains all necessary program ingredients. Run the BTP3.exe
• To enable BTP full function volume you should download some *.hgt files containing the SRTM3-data and store in any folder. This folder has to be specified under 'Settings->SRTM3 data folder'. This source of void corrected data is recommended. Once BTP finds valid *.hgt-files in the specified folder, it will render the map new, a blank topographic map should appear. If no elevation data for the current coordinates was found the window might be unchanged. You may go to you region of interest pressing 'g'-key and enter your desired coordinates. E.g. you should download these hgt-files, press 'g' and type '46.5 12.92' to center the Monte Zoncolan.
• Now you may click on any road on the map an a green point will appear, the start point of your tour. Clicking on a another point the shortest track will be routed and displayed.
• If you move along the track there appear black and yellow circles. You can drag-and-drop the black ones and fix the track by clicking the yellow ones, which then form to black circles. Delete the track with ESC or delete key. Shorten it with backspace.
• Save this track with 'Track->save btr' and reload it with 'Track->load btr' to modify and plan another time.
• In the profile window the current track will be displayed, together with power and velocity estimations. Turn on/off the red and blue line with 'Power Analysis -> show ...'. Change the estimation parameters in the Power Analysis window (section 'Power Analysis')
• You may use the Power Analysis to investigate a gpx-file, independend of any btp-files. Use 'Data->Analyse gpx'. You can use 'open with' or command argument handling with BPT, accepting both gpy and btp file.

Following the advices you might be soon ready to analyse the massive stage final which had been once planned at the Giro d'Italia but than shortened to the zoncolan only due to riders striking

If the program does not start any more, try to delete the settings.stg file within the application folder.

#### Keybord commands

 ↑ (up) navigate to the north ↓ (down) navigate to the south ← (left) navigate to the west → (right) navigate to the east + (plus) zoom in + (minus) zoom out ESC delete track; if STRONG is calculating: stop calculation delete delete track; if STRONG is calculating: stop calculation ↵ (enter) start an "open end" routing. Lock a previewed track pressing 'n', accept it with a further enter press. Or just click by mouse instead. ⇐ (backspace) delete last segment of the track; press ctrl atditionally to delete last 10 segments ⇑ (page up) select among the pareto optimal STRONG tracks after a successful STRONG calculation ⇓ (page down) select among the pareto optimal STRONG tracks after a successful STRONG calculation 0,1,2,3,4,5 set allowed track type: 0 motorway, 1 national highway, 2 main road, 3 side road, 4 small road (usually still tarmaced), 5 untarmaced tracks, possibly still ridable with a race bike. Pressing atditional ctrl sets the minimum type, without ctrl set the maximum type. c route for most climbing per km, 'climb mode', adjust algorithm in 'Settings->STRONG settings' e editing mode, allows to select map elemens and delete or modify its type with the numbers f route for least accumulated height difference, 'flat mode' g 'go to' dialog to change map position, moves to lat/lon coordinates given in degree k route short, 'kurz mode', press ctrl to execute 'air-line routing' " " (space) route short, 'kurz mode', press ctrl to execute 'air-line routing' l select layer, generates STRONG layer from a finished STRONG calculation m route for highest Hm/km quotient, 'mountain mode', adjust algorithm in 'Settings->STRONG settings' n toggles preview: within any routing mode you have the possibility to press ENTER instead of choosing an end point with mouse. You then can move the mouse over the map and the specified track will be shown instantly. press 'n' to lock this view or unlock. Press Enter or click with the mouse to accept this track. s route STRONG, calculates shortes tracks at give maximum give accumulated altitude gain, 'STRONG mode', for details see STRONG, adjust algorithm in 'Settings->STRONG settings' t route for shortest time (a longer way through a valley might be faster than the short hilly track), 'time mode', time is calculated by the current Settings of the Power Analysis Window y redo (last track modification) z undo (last track modification)

At first it hast to be mentioned, that you can cut an existing data set any time you want with 'Data->save btp', which will save only the data shown on the current map. If the sample data on the Download page is not sufficient for you, you soon want to create your own dataset.

First you need to have a OpenStreetMap data file in the *.osm format. For that purpose execute the following steps

• first you need to get OpenStreetMap data. Go to geofabrik and the subregions you desire and finally download a .osm.pbf-file
• Download osmconvert and save it in the directory where you stored the .osm.pbf-file
• In the Window explorer navigate to this directory and type 'cmd' in the address line (alternatively shift-right click->Open Command Window Here)
• now type 'osmconvert.exe A -b=C,D,E,F -o=G', substituting A by the *.osm.pbf filename, C,D,E,F by minimum longitude, minimum latitude, maximum longitude, maximum latitude and G your destiantion filename *.osm. The file extension .osm is important.
• For the Zoncolan-example you might download Europe->Italy the lates osm.pbf file and cut it with the following command 'osmconvert.exe italy-latest.osm.pbf -b=12.7,46.35,13.1,46.6 -o=zoncolan.osm'

Now you can transform the osm file into a BTP-specific btp-file which will be mush smaller in size and fast to load. Follow these steps:

• Load the osm file in BTP with Data->read osm. Insure yourself that SRTM3 data was specified with 'Settings->SRTM3 data folder'. In principal there is no limitation of size for the osm-file. This strongly depends on your memory capacity. The available Memory should be atz least as mush as the size of the osm-file.
• On finish reading the osm-file, the data will be shown. It can be now saved using 'Data->save btp'. Only the data contained within the displayed area will be shown

#### Power Analysis

Based on either a given time stamp or the P-v-specific of the rider (which can be adjusted in C, see picture above) the average power output of the rider is calculated, given the environmental parameters given in A, B, D and E. Power analysis is executed every time a track is modified or loaded. To avoid this, close the Power Analysis Window, because for slow computers or long tracks the calculation is time consuming.

First one has to adapt the environmental parameters to the own situation. In A this can be done. Check 'fight wind', if you want the velocity kept even at head winds. In B you can change the Wind conditions by directly clicking at the compass card to adjust wind strength and direction, or you type it by hand

Normally (i.e. not analysing a gpx with time stamps) you now have to adjust the P-v-plot to achieve the desired average velocity or power. The whole calculation is based on the assumption, that the power output of the virtual rider only depends on its relative velocity (relative to the air), so the rider is pushing hard slowly climbing or fighting head winds and relaxes downhill or with tail winds. If you check the 'fight wind' checkbox in A, you P will depend only on the real velocity (over ground) and not on the relative velocity. In box F the dependence of the velocity from the slope of the road is printed, given the power-velocity-relation of C and the cwA-velocity-relation of D

In D you can adjust the aerodynamics of the rider. Again a velocity dependence of the rider can be defined, representing the different riding styles (out of the saddle, huts, lower bar, etc.). It together with the power-velocity relation rules the velocity, the rider will ride at a given slope

The Poweranalyses simulates necessary breaking due to sharp bending of the road. You can define a maximum radial acceleration and a maximum break acceleration, from which the maximum velocity is calculated, the rider is allowed to ride. In practice this applies especially in downhill sections.

Pressing 'Recalc' you can recalculate the average power output and velocity after changing parameters. In Box F you will find information not only about average power output

and average velocity but also about how the power is used. Eflat is the energy you would need to ride at this speed an a flat road. Ebrake is the energy which is lost due to braking (and subsequent acceleration). The remaining energy is wasted in the broad velocity distribution the rider is forced to due to winds and mountains. For more information have a look here. In plot g a histogram is shown indicating, how mush time was spend at a specific power.

#### The 3D-View

To understand the handling of the 3D-View some basic things have to be mentioned. A 3D-View is defined by the camera position (latitude/longitude/height), the viewing direction (elevation/azimut) of the camera and its zoom. You can define parameters of the environment (superelevation,fog) and picture size (width/height).

Based on this Data it is possible to assign every pixel of the picture a point on the map. To colour the 3D-View this map has to be known and is pre calculated as the texture. You might change the 'Map->settings' or change the track, now you want to update the 3D-View. This actually means updating the texture by pressing 'retexture'. If you only want to change camera position or fog or super elevation 'render' is sufficient.

When pressing '3D-View->show 3D' an default view will be rendered. It represents the view from bottom left corner of the map to the top right corner. If you see nothing, you should first try to set the 'height pos' to a reasonable value. If you enlarge the picture size you also see more. Once you see the terrain you can define a new camera position by left-click onto the picture. With right-click you can define the point where the camera should look. Of course you can type the related parameters by hand.

When you are satisfied with the picture composition you can adjust the texture. You can increase the 'Texture Megapixel' value as far as your computer allows. For a nice view you may turn off the scale in the 'Map->settings'. The fog can be defined by two values. The offset specifies a distance (in meters) where no fog at all should be considered. All terrain within this distance shows full saturation of colours. Pixels beyond this offset are desaturated exponentially with respect to its distance.