-itinerary - 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 [gap] is displayed in the itinerary list whenever the first node of a way differs from the last node of the preceeding way. +itinerary - 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 [gap] is displayed in the itinerary list whenever the first node of a way differs from the last node of the preceeding way.
@@ -192,4 +192,5 @@ Route type - 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: +@@ -212,9 +212,4 @@
- -way - The respective OSM primitive. It is visible in the JOSM main window and a list of ways constitutes the itinerary of a bus route. A way has an orientation from its first node 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 relation membership representing the itinerary: forward means that the vehicle passes the way in its orientation while backward means the opposite. @@ -223,5 +218,5 @@
-Track - 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. +track - 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.
@@ -233,5 +228,5 @@ -If you have a GPX file and want to create bus stops or stations 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 Select GPX file. After you have chosen a file, you can use the subsequently described items. If you close the dialog, the generated stops remain as ordinary nodes in the JOSM dataset - you cannot manage them any more from this dialog. +If you have a GPX file and want to create bus stops or stations 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 Select GPX file. After you have chosen a file, you can use the subsequently described items. If you close the dialog, the generated stops remain as ordinary nodes in the JOSM dataset - you cannot manage them any more from this dialog.
The large list in the center contains all tracks that have been found in the GPX file. They are described by their name. The features in the tabs Settings and Stops depend on the content of the track and can only be used if you choose a track here.
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:
Choose here which kind of stops you want to generate. Available options are bus stops, tram stops, light rail stations, subway stations and railway stations.
+ +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.
+ +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 Time on your GPS device. Then you can see the real GPS times of the points where the software guesses the stops to be. For other mapping methods, this field is meaningless.
+ +This field influences the behaviour of the suggest stops feature. It indicates for how much the tracklog must remain at (almost) the same position to guess the location to be a stop.
+ +This field influences the behaviour of the suggest stops feature. It indicates for what amount of meters the position in a tracklog may move to still assume the location to be a stop. 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.
+ +This tab is only accessible if you have selected a track from Tracks in this GPX file in the tab Tracks.
+ +The large list in the center contains all relations that are recognised as public transport routes. They are listed with the value of their tag ref, the value of their tag to and the ID of their relation. A relation is considered as public transport service if it has the tags type=route and route is set to one of the values bus, tram, light_rail, subway or rail.
+ +This button refreshes the list Existing route patterns.
+ +This button generates a new route pattern.
+ +This button deletes the currently marked route pattern.
+ +This button makes a copy of the currently marked route pattern.
+ +This button changes the direction of the route pattern: the values of the tags to and from are exchanged and the itinerary and the list of the stops are reflected.
@@ -335,7 +334,7 @@ - +The list contains the five tags that every public transport route must have:
The list contains further tags which are quite common for public transport routes:
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 standard data format. If you leave a key empty or delete the key, the respective key will be removed from the relation.
+ +This adds an empty line to the additional tags list.
This list contains all the current members of the relation you are editing that are ways. The intended format of a route relation expects a continuous list of ways that represents the itinerary the vehicle takes in reality. Whenever two ways don't fit head on tail, a marker [gap] is put between the two corresponding entries in an extra line to make breaks clearly visible. This is not a member of the relation but just a marker. You can change the role of a way in the right column. Choose forward if the vehicle passes the way along the orientation of the way and backward if the vehicle passes the way against the orientation of the way. To properly display relations that don't follow the Oxmoa scheme, all other roles including the empty role are also displayed and you can choose despite forward and backward also an empty role.
+ +Detects entries whose corresponding objects are marked on the map. Mark one or more ways on the map. Then a click on Find marks every entry in the current relation that corresponds to a way currently marked on the map.
+ +This button changes the view on the map such that all ways belonging to a marked entry become visible. If no entry is marked, then the view will show all ways belonging to an entry.
+ +This button marks all entries that are marked in the list as ways on the map and unmarks all other ways. It also copies a list of the marked entries to the plugin's internal clipboard, such that roles and the order can be reconstructed. If no entry is marked, then all objects belonging to an entry are marked and copied to the clipboard.
+ +This button adds all ways that are currently marked on the map as entries 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 Sort.
+ +This button deletes all currently marked entries.
+ +If one or more entries are marked, all marked entries are sorted. I.e. their order and role is changed such that they form a continuous itinerary. If this is not possible, the plugin tries to construct long continuous sequences of sections. If no entries are marked, the entire list is sorted.
+ + +If one or more entries are marked, their order is reflected and their roles get swapped between forward and backward, i.e. every entry is put after its successor. If no entry is marked, then the entire list will be reflected.
@@ -408,35 +407,35 @@ - +This list contains all the current members of the relation you are editing that are nodes. The intended format of a route relation expects a list of nodes that represents the stops in the order the bus takes them in reality. The roles can be changed to forward_stop or backward_stop but according to Oxmoa scheme, they should remain empty.
+ +Detects entries whose corresponding objects are marked on the map. Mark one or more nodes on the map. Then a click on Find marks every entry in the current relation that corresponds to a node currently marked on the map.
+ +This button changes the view on the map such that all nodes belonging to a marked entry become visible. If no entry is marked, then the view will show all nodes belonging to an entry.
+ +This button marks all entries that are marked in the list as nodes on the map and unmarks all other nodes. It also copies a list of the marked entries to the plugin's internal clipboard, such that roles and the order can be reconstructed. If no entry is marked, then all objects belonging to an entry are marked and copied to the clipboard.
+ +This button adds all nodes that are currently marked on the map as entries 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 Sort.
+ +This button deletes all currently marked entries.
+ +If one or more entries are marked, all marked entries are sorted. The sorting order depends on the itinerary, the settings for the distance limit and the orientation check box: the sorting algorithm attaches each stop to the nearest segment of the itinerary and then orders them in the order they are passed on the itinerary. Then all stops that can't be attached are added to the end of the list. If no entry is marked, all entries are sorted.
+ +If one or more entries are marked, their order is reflected. I.e. every entry is put after its successor.
This check box controls the behaviour of the button Suggest stops and the button Sort in the tab Stops. If you mark only one of the boxes Right hand side or Left hand side, only stops on the respective side are taken into account. If you mark both boxes, stops on both sides are taken into account.
+ +This text field also controls the behaviour of the button Suggest stops and the button Sort in the tab Stops. Only stops that have a distance less or equal the limit set here are taken into account.
+ +This button replaces the current list of stops by a list of all stops that are close to the itinerary with regard to the setting of the check boxes and the text field described above.