Hi, I'm not sure why you think PT_Assistant is simply a validator. It has many features to help you create bus routes and recently I added some features to help with conversion from PTv1 to PTv2. Those are not in the released version yet though, because I'm also adding some other features (experimental). For the past few years I mentored students to develop the plugin. This meant it only got developed 3 months per year though. So recently I started learning Java and now I'm doing some development on it myself. Something I wanted to figure out for a long time, is whether it would make sense to have the itineraries as superroute relations that contain route relations for the 'bundles'. Work in progress...
Would you have time for a Google Hangout this weekend? I would like to demonstrate how converting route relations to PTv2 works. Jo (Polyglot) On Fri, Nov 13, 2020 at 10:10 PM ipswichmapper--- via josm-dev < josm-dev@openstreetmap.org> wrote: > Sorry, I meant to say "what inherant flaws does PTV2 have". > -- > Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: > https://tutanota.com > > > 13 Nov 2020, 21:04 by josm-dev@openstreetmap.org: > > > Great! This should hopefully simplify the improvement of this addon. > > > > 1. What inherant flaws did the sudtem have? > > 2. How easy is it to determine if a way is "forward" or "backward" > automatically? > > > > Also, it seems that the relation editor can sort ways, so a rewrite of > this addon can remove this feature. > > -- > > > > > > > > 13 Nov 2020, 20:53 by roland.olbri...@gmx.de: > > > >> Hi all, > >> > >> thank you for the feedback. > >> > >>> Furthermore, this plugin is closed-source (as far as I know), so it > cannot be "fixed". > >>> > >> > >> The plugin is open source, see > >> > https://github.com/openstreetmap/josm-plugins/tree/master/public_transport > >> > >> The problem is that maintaining the plugin is a lot of work. I abandoned > >> the development long ago because public transport v2 would have meant > >> too much work, because the scheme has inherent flaws. Any such flaw does > >> fall on the developer multiple times, for implementation, for developing > >> test cases for all the undefined corner cases, for a UI that explains > >> what the software actually does. > >> > >> By contrast, updating to a single different set of tags for stop poles > >> is not a substantial problem. > >> > >>> This would mean you could immediately add all the stops in the click > of a button, and sort broken relations in a click of a button. > >>> > >> > >> Since writing this plugin, the relation editor has superseded most of > >> the way sorting features. Thus, it no longer makes sense to duplicate > >> the sorting capabilities in a distinct plugin. > >> > >> I would nowadays add buttons to the relation editor rather than a > >> separate relation editor. > >> > >> There is also an unfinished routing algorithm in the plugin. I never had > >> found a reasonable UI to exhibit that to the end user. > >> > >> Best regards, > >> > >> Roland > >> >
