Changeset 20874 in osm
- Timestamp:
- 2010-04-09T17:03:03+02:00 (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
applications/editors/josm/plugins/public_transport/resources/public_transport.html
r20872 r20874 145 145 <p> 146 146 <a id="notion.itinerary"/> 147 <strong>itinerary</strong> - The way a bus service actually takes. Note that buses or other vehicles can't make jumps, thus there cannot be gaps in an itinerary. For that reason, a line <em>[gap]</em> is displayed in the <a href="#subsection.itinerary.list" />itinerary list</a> whenever the first <a href="#notion.node">node</a> of a <a href="#notion.way">way</a> differs from the last <a href="#notion.node">node</a> of the preceeding <a href="#notion.way">way</a>.147 <strong>itinerary</strong> - The way a bus service actually takes. Note that buses or other vehicles can't make jumps, thus there cannot be gaps in an itinerary. For that reason, a line <em>[gap]</em> is displayed in the <a href="#subsection.itinerary.list">itinerary list</a> whenever the first <a href="#notion.node">node</a> of a <a href="#notion.way">way</a> differs from the last <a href="#notion.node">node</a> of the preceeding <a href="#notion.way">way</a>. 148 148 </p> 149 149 … … 192 192 <a id="notion.route_type"/> 193 193 <strong>Route type</strong> - You don't want to see an international high speed rail service and a local school bus to be mapped in the same way. For this purpose, we need some further taxonomy to classify public transport services into. As a preliminary classification, we use the following: 194 </p> 194 195 <ul> 195 196 <li><em>Bus</em>: Any service that operates completely or partly on ordinary streets with rubber tyred vehicles.</li> … … 199 200 <li><em>Railway</em>: Services that operate on wide area railway networks.</li> 200 201 </ul> 201 </p>202 202 203 203 <p> … … 212 212 213 213 <p> 214 <a id="notion."/>215 <strong></strong> -216 </p>217 218 <p>219 214 <a id="notion.way"/> 220 215 <strong>way</strong> - The respective OSM primitive. It is visible in the JOSM main window and a list of ways constitutes the <a href="#notion.itinerary">itinerary</a> of a <a href="#notion.bus_route">bus route</a>. A way has an orientation from its first <a href="#notion.node">node</a> to its last node. In JOSM, this is visualised by the direction of the arrows that represent the way. Thus, a vehicle can pass a way in or against its orientation. This is indicated by the role of the <a href="#notion.relation">relation</a> membership representing the <a href="#notion.itinerary">itinerary</a>: <em>forward</em> means that the vehicle passes the way in its orientation while <em>backward</em> means the opposite. … … 223 218 <p> 224 219 <a id="notion.track"/> 225 <strong> Track</strong> - A data structure from GPX files: GPX files are organised as a collection of waypoints and tracks. While waypoints are just points, each track is a sequence of points representing an arbitrary motion. The track contains the information when the vehicle was where. Usually, a GPS logger starts a new track each time you put its power on.220 <strong>track</strong> - A data structure from GPX files: GPX files are organised as a collection of waypoints and tracks. While waypoints are just points, each track is a sequence of points representing an arbitrary motion. The track contains the information when the vehicle was where. Usually, a GPS logger starts a new track each time you put its power on. 226 221 </p> 227 222 … … 233 228 </div> 234 229 235 If you have a <a href="#notion.gpx_file">GPX file</a> and want to create <a href="#notion.stop">bus stops or stations</a> from it, use this dialog. Each time you open this dialog, you must select from which GPX file you want to create stops. For this purpose, please choose a file in the file open dialog <em>Select GPX file</em>. After you have chosen a file, you can use the subsequently described items. If you close the dialog, the generated stops remain as ordinary <a href="#notion.node">nodes</a> in the JOSM dataset - you cannot manage them any more from this dialog. 230 <p>If you have a <a href="#notion.gpx_file">GPX file</a> and want to create <a href="#notion.stop">bus stops or stations</a> from it, use this dialog. Each time you open this dialog, you must select from which GPX file you want to create stops. For this purpose, please choose a file in the file open dialog <em>Select GPX file</em>. After you have chosen a file, you can use the subsequently described items. If you close the dialog, the generated stops remain as ordinary <a href="#notion.node">nodes</a> in the JOSM dataset - you cannot manage them any more from this dialog.</p> 236 231 237 232 <div> … … 240 235 </div> 241 236 242 < a id="subsection.tracks.list"/>237 <div><a id="subsection.tracks.list"/></div> 243 238 <h4>List <em>Tracks in this GPX file</em></h4> 244 The large list in the center contains all <a href="#notion.track">tracks</a> that have been found in the <a href="#notion.gpx_file">GPX file</a>. They are described by their name. The features in the tabs <a href="#section.settings">Settings</a> and <a href="#section.trackstops">Stops</a> depend on the content of the track and can only be used if you choose a track here. 239 <p> The large list in the center contains all <a href="#notion.track">tracks</a> that have been found in the <a href="#notion.gpx_file">GPX file</a>. They are described by their name. The features in the tabs <a href="#section.settings">Settings</a> and <a href="#section.trackstops">Stops</a> depend on the content of the track and can only be used if you choose a track here.</p> 245 240 246 241 <div> … … 249 244 </div> 250 245 251 In this tab you configure the values for the nodes you create or manage with the dialog. Depending on the method you use to create stops, different parts of this tab might be relevant: 246 <p>In this tab you configure the values for the nodes you create or manage with the dialog. Depending on the method you use to create stops, different parts of this tab might be relevant:</p> 252 247 <ul> 253 248 <li>If you map from waypoints, only the combo box <a href="#subsection.settings.type">Type of stops to add</a> is relevant to you.</li> … … 256 251 </ul> 257 252 258 < a id="subsection.settings.type"/>253 <div><a id="subsection.settings.type"/></div> 259 254 <h4>Combo box <em>Type of stops to add</em></h4> 260 Choose here which kind of <a href="#notion.stop">stops</a> you want to generate. Available options are <a href="#notion.route_type">bus</a> stops, <a href="#notion.route_type">tram</a> stops, <a href="#notion.route_type">light rail</a> stations, <a href="#notion.route_type">subway</a> stations and <a href="#notion.route_type">rail</a>way stations. 261 262 < a id="subsection.settings.gps"/>255 <p>Choose here which kind of <a href="#notion.stop">stops</a> you want to generate. Available options are <a href="#notion.route_type">bus</a> stops, <a href="#notion.route_type">tram</a> stops, <a href="#notion.route_type">light rail</a> stations, <a href="#notion.route_type">subway</a> stations and <a href="#notion.route_type">rail</a>way stations.</p> 256 257 <div><a id="subsection.settings.gps"/></div> 263 258 <h4>Text field <em>Time on your GPS device</em></h4> 264 265 <a id="subsection.settings.stopwatch"/> 259 <p>If you map with a tracklog and a stopwatch, put here the time on your GPS device when you have synchronised your logger and your stopwatch. For other mapping methods, this field is meaningless. It is initially set to the time of the first trackpoint in the track.</p> 260 261 <div><a id="subsection.settings.stopwatch"/></div> 266 262 <h4>Text field <em>Time on your stopwatch</em></h4> 267 268 <a id="subsection.settings.time_window"/> 263 <p>If you map with a tracklog and a stopwatch, put here the time on your stopwatch when you have synchronised your logger and your stopwatch. Usually, this will be zero. If you map with a tracklog only, set this field to the same value as <a href="#subsection.settings.gps">Time on your GPS device</a>. Then you can see the real GPS times of the points where the software guesses the <a href="#notion.stop">stops</a> to be. For other mapping methods, this field is meaningless.</p> 264 265 <div><a id="subsection.settings.time_window"/></div> 269 266 <h4>Text field <em>Time window</em></h4> 270 271 <a id="subsection.settings.threshold"/> 267 <p>This field influences the behaviour of the <a href="#subsection.settings.suggest_stops">suggest stops</a> feature. It indicates for how much the tracklog must remain at (almost) the same position to guess the location to be a <a href="#notion.stop">stop</a>.</p> 268 269 <div><a id="subsection.settings.threshold"/></div> 272 270 <h4>Text field <em>Move Threshold</em></h4> 273 274 <a id="subsection.settings.suggest_stops"/> 271 <p>This field influences the behaviour of the <a href="#subsection.settings.suggest_stops">suggest stops</a> feature. It indicates for what amount of meters the position in a tracklog may move to still assume the location to be a <a href="#notion.stop">stop</a>. It also sets the minimum distance between two stops: a location is only guessed to be a stop if it is at least this amount of meters away from the last guessed stop.</p> 272 273 <div><a id="subsection.settings.suggest_stops"/></div> 275 274 <h4>Button <em>Suggest Stops</em></h4> 276 275 … … 280 279 </div> 281 280 282 This tab is only accessible if you have selected a track from <a href="#subsection.tracks.list">Tracks in this GPX file</a> in the tab <a href="#section.tracks">Tracks</a>. 283 284 < a id="subsection.trackstops.list"/>281 <p>This tab is only accessible if you have selected a track from <a href="#subsection.tracks.list">Tracks in this GPX file</a> in the tab <a href="#section.tracks">Tracks</a>.</p> 282 283 <div><a id="subsection.trackstops.list"/></div> 285 284 <h4>List of created stops</h4> 286 285 … … 290 289 </div> 291 290 292 < a id="subsection.waypoints.list"/>291 <div><a id="subsection.waypoints.list"/></div> 293 292 <h4>List of waypoints in the file</h4> 294 293 … … 305 304 </div> 306 305 307 < a id="subsection.overview.list"/>306 <div><a id="subsection.overview.list"/></div> 308 307 <h4>List <em>Existing route patterns</em></h4> 309 The large list in the center contains all relations that are recognised as <a href="#notion.bus_route">public transport routes</a>. They are listed with the value of their tag <em>ref</em>, the value of their tag <em>to</em> and the ID of their <a href="#notion.relation">relation</a>. A relation is considered as public transport service if it has the tags <em>type=route</em> and <em>route</em> is set to one of the values <em>bus</em>, <em>tram</em>, <em>light_rail</em>, <em>subway</em> or <em>rail</em>. 310 311 < a id="subsection.overview.refresh"/>308 <p>The large list in the center contains all relations that are recognised as <a href="#notion.bus_route">public transport routes</a>. They are listed with the value of their tag <em>ref</em>, the value of their tag <em>to</em> and the ID of their <a href="#notion.relation">relation</a>. A relation is considered as public transport service if it has the tags <em>type=route</em> and <em>route</em> is set to one of the values <em>bus</em>, <em>tram</em>, <em>light_rail</em>, <em>subway</em> or <em>rail</em>.</p> 309 310 <div><a id="subsection.overview.refresh"/></div> 312 311 <h4>Button <em>Refresh</em></h4> 313 This button refreshes the list <em>Existing route patterns</em>. 314 315 < a id="subsection.overview.new"/>312 <p>This button refreshes the list <em>Existing route patterns</em>.</p> 313 314 <div><a id="subsection.overview.new"/></div> 316 315 <h4>Button <em>New</em></h4> 317 This button generates a new <a href="#notion.bus_route">route pattern</a>. 318 319 < a id="subsection.overview.delete"/>316 <p>This button generates a new <a href="#notion.bus_route">route pattern</a>.</p> 317 318 <div><a id="subsection.overview.delete"/></div> 320 319 <h4>Button <em>Delete</em></h4> 321 This button deletes the currently marked <a href="#notion.bus_route">route pattern</a>. 322 323 < a id="subsection.overview.duplicate"/>320 <p>This button deletes the currently marked <a href="#notion.bus_route">route pattern</a>.</p> 321 322 <div><a id="subsection.overview.duplicate"/></div> 324 323 <h4>Button <em>Duplicate</em></h4> 325 This button makes a copy of the currently marked <a href="#notion.bus_route">route pattern</a>. 326 327 < a id="subsection.overview.reflect"/>324 <p>This button makes a copy of the currently marked <a href="#notion.bus_route">route pattern</a>.</p> 325 326 <div><a id="subsection.overview.reflect"/></div> 328 327 <h4>Button <em>Reflect</em></h4> 329 This button changes the direction of the <a href="#notion.bus_route">route pattern</a>: the values of the tags <em>to</em> and <em>from</em> are exchanged and the <a href="subsection.itinerary.reflect">itinerary</a> and the <a href="subsection.stops.reflect">list of the stops</a> are reflected. 328 <p>This button changes the direction of the <a href="#notion.bus_route">route pattern</a>: the values of the tags <em>to</em> and <em>from</em> are exchanged and the <a href="#subsection.itinerary.reflect">itinerary</a> and the <a href="#subsection.stops.reflect">list of the stops</a> are reflected.</p> 330 329 331 330 … … 335 334 </div> 336 335 337 < a id="subsection.tags.required"/>336 <div><a id="subsection.tags.required"/></div> 338 337 <h4>List <em>Required tags</em></h4> 339 The list contains the five tags that every <a href="#notion.bus_route">public transport route</a> must have: 338 <p>The list contains the five tags that every <a href="#notion.bus_route">public transport route</a> must have:</p> 340 339 <ul> 341 340 <li><em>type</em>: Must always have the value <em>route</em>.</li> … … 346 345 </ul> 347 346 348 < a id="subsection.tags.common"/>347 <div><a id="subsection.tags.common"/></div> 349 348 <h4>List <em>Common tags</em></h4> 350 The list contains further tags which are quite common for <a href="#notion.bus_route">public transport routes</a>: 349 <p>The list contains further tags which are quite common for <a href="#notion.bus_route">public transport routes</a>:</p> 351 350 <ul> 352 351 <li><em>direction</em>: The destination shown in front of the vehicle and/or at the platform (an alternative for the tag <a href="#subsection.tags.required">to</a>).</li> … … 357 356 </ul> 358 357 359 < a id="subsection.tags.additional"/>358 <div><a id="subsection.tags.additional"/></div> 360 359 <h4>List <em>Additional tags</em></h4> 361 Additional tags can be added here. These tags might be of use for specific software or describe special local features but aren't part of the <a href="#notion.oxmoa">standard data format</a>. If you leave a key empty or delete the key, the respective key will be removed from the <a href="#notion.relation">relation</a>. 362 363 < a id="subsection.tags.add"/>360 <p>Additional tags can be added here. These tags might be of use for specific software or describe special local features but aren't part of the <a href="#notion.oxmoa">standard data format</a>. If you leave a key empty or delete the key, the respective key will be removed from the <a href="#notion.relation">relation</a>.</p> 361 362 <div><a id="subsection.tags.add"/></div> 364 363 <h4>Button <em>Add a new Tag</em></h4> 365 This adds an empty line to the <a href="#subsection.tags.additional">additional tags list</a>. 364 <p>This adds an empty line to the <a href="#subsection.tags.additional">additional tags list</a>.</p> 366 365 367 366 <div> … … 370 369 </div> 371 370 372 < a id="subsection.itinerary.list"/>371 <div><a id="subsection.itinerary.list"/></div> 373 372 <h4>List of member ways</h4> 374 This list contains all the current members of the <a href="#notion.relation">relation</a> you are editing that are <a href="#notion.way">ways</a>. The <a href="#notion.oxmoa">intended format</a> of a route relation expects a continuous list of ways that represents the <a href="#notion.itinerary">itinerary</a> the vehicle takes in reality. Whenever two <a href="#notion.way">ways</a> don't fit head on tail, a marker <em>[gap]</em> is put between the two corresponding <a href="#notion.entry">entries</a> in an extra line to make breaks clearly visible. This is not a member of the <a href="#notion.relation">relation</a> but just a marker. You can change the role of a way in the right column. Choose <em>forward</em> if the vehicle passes the way <a href="#notion.way">along</a> the orientation of the way and <em>backward</em> if the vehicle passes the way <a href="#notion.way">against</a> the orientation of the way. To properly display <a href="#notion.relation">relations</a> that don't follow the <a href="#notion.oxmoa">Oxmoa scheme</a>, all other roles including the empty role are also displayed and you can choose despite <em>forward</em> and <em>backward</em> also an empty role. 375 376 < a id="subsection.itinerary.find"/>373 <p>This list contains all the current members of the <a href="#notion.relation">relation</a> you are editing that are <a href="#notion.way">ways</a>. The <a href="#notion.oxmoa">intended format</a> of a route relation expects a continuous list of ways that represents the <a href="#notion.itinerary">itinerary</a> the vehicle takes in reality. Whenever two <a href="#notion.way">ways</a> don't fit head on tail, a marker <em>[gap]</em> is put between the two corresponding <a href="#notion.entry">entries</a> in an extra line to make breaks clearly visible. This is not a member of the <a href="#notion.relation">relation</a> but just a marker. You can change the role of a way in the right column. Choose <em>forward</em> if the vehicle passes the way <a href="#notion.way">along</a> the orientation of the way and <em>backward</em> if the vehicle passes the way <a href="#notion.way">against</a> the orientation of the way. To properly display <a href="#notion.relation">relations</a> that don't follow the <a href="#notion.oxmoa">Oxmoa scheme</a>, all other roles including the empty role are also displayed and you can choose despite <em>forward</em> and <em>backward</em> also an empty role.</p> 374 375 <div><a id="subsection.itinerary.find"/></div> 377 376 <h4>Button <em>Find</em></h4> 378 Detects <a href="#notion.entry">entries</a> whose corresponding objects are <a href="#notion.select">marked</a> on the map. Mark one or more ways on the map. Then a click on <em>Find</em> <a href="#notion.select">marks</a> every <a href="#notion.entry">entry</a> in the current <a href="#notion.relation">relation</a> that corresponds to a <a href="#notion.way">way</a> currently marked on the map. 379 380 < a id="subsection.itinerary.show"/>377 <p>Detects <a href="#notion.entry">entries</a> whose corresponding objects are <a href="#notion.select">marked</a> on the map. Mark one or more ways on the map. Then a click on <em>Find</em> <a href="#notion.select">marks</a> every <a href="#notion.entry">entry</a> in the current <a href="#notion.relation">relation</a> that corresponds to a <a href="#notion.way">way</a> currently marked on the map.</p> 378 379 <div><a id="subsection.itinerary.show"/></div> 381 380 <h4>Button <em>Show</em></h4> 382 This button changes the view on the map such that all <a href="#notion.way">ways</a> belonging to a <a href="#notion.select">marked</a> <a href="#notion.entry">entry</a> become visible. If no entry is marked, then the view will show all <a href="#notion.way">ways</a> belonging to an entry. 383 384 < a id="subsection.itinerary.mark"/>381 <p>This button changes the view on the map such that all <a href="#notion.way">ways</a> belonging to a <a href="#notion.select">marked</a> <a href="#notion.entry">entry</a> become visible. If no entry is marked, then the view will show all <a href="#notion.way">ways</a> belonging to an entry.</p> 382 383 <div><a id="subsection.itinerary.mark"/></div> 385 384 <h4>Button <em>Mark</em></h4> 386 This button <a href="#notion.select">marks</a> all <a href="#notion.entry">entries</a> that are marked in the list as ways on the map and unmarks all other <a href="#notion.way">ways</a>. It also copies a list of the marked entries to the plugin's <a href="#notion.clipboard">internal clipboard</a>, such that roles and the order can be reconstructed. If no <a href="#notion.entry">entry</a> is marked, then all objects belonging to an entry are marked and copied to the clipboard. 387 388 < a id="subsection.itinerary.add"/>385 <p>This button <a href="#notion.select">marks</a> all <a href="#notion.entry">entries</a> that are marked in the list as ways on the map and unmarks all other <a href="#notion.way">ways</a>. It also copies a list of the marked entries to the plugin's <a href="#notion.clipboard">internal clipboard</a>, such that roles and the order can be reconstructed. If no <a href="#notion.entry">entry</a> is marked, then all objects belonging to an entry are marked and copied to the clipboard.</p> 386 387 <div><a id="subsection.itinerary.add"/></div> 389 388 <h4>Button <em>Add</em></h4> 390 This button adds all <a href="#notion.way">ways</a> that are currently <a href="#notion.select">marked</a> on the map as <a href="#notion.entry">entries</a> in the list. The entries are added in arbitrary order before the first marked entry. If no entry is marked, then the new entries will be appended. You can order the just added elements by marking them and clicking <a href="#subsection.itinerary.sort">Sort</a>. 391 392 < a id="subsection.itinerary.delete"/>389 <p>This button adds all <a href="#notion.way">ways</a> that are currently <a href="#notion.select">marked</a> on the map as <a href="#notion.entry">entries</a> in the list. The entries are added in arbitrary order before the first marked entry. If no entry is marked, then the new entries will be appended. You can order the just added elements by marking them and clicking <a href="#subsection.itinerary.sort">Sort</a>.</p> 390 391 <div><a id="subsection.itinerary.delete"/></div> 393 392 <h4>Button <em>Delete</em></h4> 394 This button deletes all currently marked <a href="#notion.entry">entries</a>. 395 396 < a id="subsection.itinerary.sort"/>393 <p>This button deletes all currently marked <a href="#notion.entry">entries</a>.</p> 394 395 <div><a id="subsection.itinerary.sort"/></div> 397 396 <h4>Button <em>Sort</em></h4> 398 If one or more <a href="#notion.entry">entries</a> are marked, all marked <a href="#notion.entry">entries</a> are sorted. I.e. their order and role is changed such that they form a continuous <a href="#notion.itinerary">itinerary</a>. If this is not possible, the plugin tries to construct long continuous sequences of sections. If no <a href="#notion.entry">entries</a> are <a href="#notion.select">marked</a>, the <a href="#subsection.itinerary.list">entire list</a> is sorted. 399 400 < a id="subsection.itinerary.reflect"/>401 <h4>Button <em> </em>Reflect</h4>402 If one or more <a href="#notion.entry">entries</a> are <a href="#notion.select">marked</a>, their order is reflected and their roles get swapped between <em>forward</em> and <rm>backward</em>, i.e. every <a href="#notion.entry">entry</a> is put after its successor. If no entry is marked, then the <a href="#subsection.itinerary.list">entire list</a> will be reflected. 397 <p>If one or more <a href="#notion.entry">entries</a> are marked, all marked <a href="#notion.entry">entries</a> are sorted. I.e. their order and role is changed such that they form a continuous <a href="#notion.itinerary">itinerary</a>. If this is not possible, the plugin tries to construct long continuous sequences of sections. If no <a href="#notion.entry">entries</a> are <a href="#notion.select">marked</a>, the <a href="#subsection.itinerary.list">entire list</a> is sorted.</p> 398 399 <div><a id="subsection.itinerary.reflect"/></div> 400 <h4>Button <em>Reflect</em></h4> 401 <p>If one or more <a href="#notion.entry">entries</a> are <a href="#notion.select">marked</a>, their order is reflected and their roles get swapped between <em>forward</em> and <em>backward</em>, i.e. every <a href="#notion.entry">entry</a> is put after its successor. If no entry is marked, then the <a href="#subsection.itinerary.list">entire list</a> will be reflected.</p> 403 402 404 403 … … 408 407 </div> 409 408 410 < a id="subsection.stops.list"/>409 <div><a id="subsection.stops.list"/></div> 411 410 <h4>List of member nodes</h4> 412 This list contains all the current members of the <a href="#notion.relation">relation</a> you are editing that are <a href="#notion.node">nodes</a>. The <a href="#notion.oxmoa">intended format</a> of a route relation expects a list of <a href="#notion.node">nodes</a> that represents the <a href="#notion.stop">stops</a> in the order the bus takes them in reality. The roles can be changed to <em>forward_stop</em> or <em>backward_stop</em> but according to <a href="#notion.oxmoa">Oxmoa scheme</a>, they should remain empty. 413 414 < a id="subsection.stops.find"/>411 <p>This list contains all the current members of the <a href="#notion.relation">relation</a> you are editing that are <a href="#notion.node">nodes</a>. The <a href="#notion.oxmoa">intended format</a> of a route relation expects a list of <a href="#notion.node">nodes</a> that represents the <a href="#notion.stop">stops</a> in the order the bus takes them in reality. The roles can be changed to <em>forward_stop</em> or <em>backward_stop</em> but according to <a href="#notion.oxmoa">Oxmoa scheme</a>, they should remain empty.</p> 412 413 <div><a id="subsection.stops.find"/></div> 415 414 <h4>Button <em>Find</em></h4> 416 Detects <a href="#notion.entry">entries</a> whose corresponding objects are <a href="#notion.select">marked</a> on the map. Mark one or more nodes on the map. Then a click on <em>Find</em> <a href="#notion.select">marks</a> every <a href="#notion.entry">entry</a> in the current <a href="#notion.relation">relation</a> that corresponds to a <a href="#notion.node">node</a> currently marked on the map. 417 418 < a id="subsection.stops.show"/>415 <p>Detects <a href="#notion.entry">entries</a> whose corresponding objects are <a href="#notion.select">marked</a> on the map. Mark one or more nodes on the map. Then a click on <em>Find</em> <a href="#notion.select">marks</a> every <a href="#notion.entry">entry</a> in the current <a href="#notion.relation">relation</a> that corresponds to a <a href="#notion.node">node</a> currently marked on the map.</p> 416 417 <div><a id="subsection.stops.show"/></div> 419 418 <h4>Button <em>Show</em></h4> 420 This button changes the view on the map such that all <a href="#notion.node">nodes</a> belonging to a <a href="#notion.select">marked</a> <a href="#notion.entry">entry</a> become visible. If no entry is marked, then the view will show all <a href="#notion.node">nodes</a> belonging to an entry. 421 422 < a id="subsection.stops.mark"/>419 <p>This button changes the view on the map such that all <a href="#notion.node">nodes</a> belonging to a <a href="#notion.select">marked</a> <a href="#notion.entry">entry</a> become visible. If no entry is marked, then the view will show all <a href="#notion.node">nodes</a> belonging to an entry.</p> 420 421 <div><a id="subsection.stops.mark"/></div> 423 422 <h4>Button <em>Mark</em></h4> 424 This button <a href="#notion.select">marks</a> all <a href="#notion.entry">entries</a> that are marked in the list as nodes on the map and unmarks all other <a href="#notion.node">nodes</a>. It also copies a list of the marked entries to the plugin's <a href="#notion.clipboard">internal clipboard</a>, such that roles and the order can be reconstructed. If no <a href="#notion.entry">entry</a> is marked, then all objects belonging to an entry are marked and copied to the clipboard. 425 426 < a id="subsection.stops.add"/>423 <p>This button <a href="#notion.select">marks</a> all <a href="#notion.entry">entries</a> that are marked in the list as nodes on the map and unmarks all other <a href="#notion.node">nodes</a>. It also copies a list of the marked entries to the plugin's <a href="#notion.clipboard">internal clipboard</a>, such that roles and the order can be reconstructed. If no <a href="#notion.entry">entry</a> is marked, then all objects belonging to an entry are marked and copied to the clipboard.</p> 424 425 <div><a id="subsection.stops.add"/></div> 427 426 <h4>Button <em>Add</em></h4> 428 This button adds all <a href="#notion.node">nodes</a> that are currently <a href="#notion.select">marked</a> on the map as <a href="#notion.entry">entries</a> in the list. The entries are added in arbitrary order before the first marked entry. If no entry is marked, then the new entries will be appended. You can order the just added elements by marking them and clicking <a href="#subsection.stops.sort">Sort</a>. 429 430 < a id="subsection.stops.delete"/>427 <p>This button adds all <a href="#notion.node">nodes</a> that are currently <a href="#notion.select">marked</a> on the map as <a href="#notion.entry">entries</a> in the list. The entries are added in arbitrary order before the first marked entry. If no entry is marked, then the new entries will be appended. You can order the just added elements by marking them and clicking <a href="#subsection.stops.sort">Sort</a>.</p> 428 429 <div><a id="subsection.stops.delete"/></div> 431 430 <h4>Button <em>Delete</em></h4> 432 This button deletes all currently marked <a href="#notion.entry">entries</a>. 433 434 < a id="subsection.stops.sort"/>431 <p>This button deletes all currently marked <a href="#notion.entry">entries</a>.</p> 432 433 <div><a id="subsection.stops.sort"/></div> 435 434 <h4>Button <em>Sort</em></h4> 436 If one or more <a href="#notion.entry">entries</a> are <a href="#notion.select">marked</a>, all marked entries are sorted. The sorting order depends on the <a href="#notion.itinerary">itinerary</a>, the settings for the <a href="#subsection.meta.maxdist">distance limit</a> and the <a href="#subsection.meta.rightleft">orientation check box</a>: the sorting algorithm attaches each <a href="#notion.stop">stop</a> to the nearest segment of the <a href="#notion.itinerary">itinerary</a> and then orders them in the order they are passed on the <a href="#notion.itinerary">itinerary</a>. Then all <a href="#notion.stop">stops</a> that can't be attached are added to the end of the list. If no <a href="#notion.entry">entry</a> is marked, all entries are sorted. 437 438 < a id="subsection.stops.reflect"/>435 <p>If one or more <a href="#notion.entry">entries</a> are <a href="#notion.select">marked</a>, all marked entries are sorted. The sorting order depends on the <a href="#notion.itinerary">itinerary</a>, the settings for the <a href="#subsection.meta.maxdist">distance limit</a> and the <a href="#subsection.meta.rightleft">orientation check box</a>: the sorting algorithm attaches each <a href="#notion.stop">stop</a> to the nearest segment of the <a href="#notion.itinerary">itinerary</a> and then orders them in the order they are passed on the <a href="#notion.itinerary">itinerary</a>. Then all <a href="#notion.stop">stops</a> that can't be attached are added to the end of the list. If no <a href="#notion.entry">entry</a> is marked, all entries are sorted.</p> 436 437 <div><a id="subsection.stops.reflect"/></div> 439 438 <h4>Button <em>Reflect</em></h4> 440 If one or more <a href="#notion.entry">entries</a> are marked, their order is reflected. I.e. every <a href="#notion.entry">entry</a> is put after its successor. 439 <p>If one or more <a href="#notion.entry">entries</a> are marked, their order is reflected. I.e. every <a href="#notion.entry">entry</a> is put after its successor.</p> 441 440 442 441 <div> … … 445 444 </div> 446 445 447 < a id="subsection.meta.rightleft"/>446 <div><a id="subsection.meta.rightleft"/></div> 448 447 <h4>Check box <em>Stops are possible</em></h4> 449 This check box controls the behaviour of the button <a href="#subsection.meta.suggest">Suggest stops</a> and the button <a href="#subsection.stops.sort">Sort</a> in the tab <a href="#section.stops">Stops</a>. If you <a href="#notion.select">mark</a> only one of the boxes <em>Right hand side</em> or <em>Left hand side</em>, only <a href="#notion.stop">stops</a> on the respective side are taken into account. If you mark both boxes, stops on both sides are taken into account. 450 451 < a id="subsection.meta.maxdist"/>448 <p>This check box controls the behaviour of the button <a href="#subsection.meta.suggest">Suggest stops</a> and the button <a href="#subsection.stops.sort">Sort</a> in the tab <a href="#section.stops">Stops</a>. If you <a href="#notion.select">mark</a> only one of the boxes <em>Right hand side</em> or <em>Left hand side</em>, only <a href="#notion.stop">stops</a> on the respective side are taken into account. If you mark both boxes, stops on both sides are taken into account.</p> 449 450 <div><a id="subsection.meta.maxdist"/></div> 452 451 <h4>Text field <em>Maximum distance from route</em></h4> 453 This text field also controls the behaviour of the button <a href="#subsection.meta.suggest">Suggest stops</a> and the button <a href="#subsection.stops.sort">Sort</a> in the tab <a href="#section.stops">Stops</a>. Only <a href="#notion.stop">stops</a> that have a distance less or equal the limit set here are taken into account. 454 455 < a id="subsection.meta.suggest"/>452 <p>This text field also controls the behaviour of the button <a href="#subsection.meta.suggest">Suggest stops</a> and the button <a href="#subsection.stops.sort">Sort</a> in the tab <a href="#section.stops">Stops</a>. Only <a href="#notion.stop">stops</a> that have a distance less or equal the limit set here are taken into account.</p> 453 454 <div><a id="subsection.meta.suggest"/></div> 456 455 <h4>Button <em>Suggest Stops</em></h4> 457 This button replaces the current <a href="#subsection.stops.list">list of stops</a> by a list of all stops that are close to the <a href="#notion.itinerary">itinerary</a> with regard to the setting of the <a href="#subsection.meta.rightleft">check boxes</a> and the <a href="#subsection.meta.maxdist">text field</a> described above. 456 <p>This button replaces the current <a href="#subsection.stops.list">list of stops</a> by a list of all stops that are close to the <a href="#notion.itinerary">itinerary</a> with regard to the setting of the <a href="#subsection.meta.rightleft">check boxes</a> and the <a href="#subsection.meta.maxdist">text field</a> described above.</p> 458 457 459 458 </body>
Note:
See TracChangeset
for help on using the changeset viewer.
