Started by Menion, January 08, 2021, 15:08:43
0 Members and 1 Guest are viewing this topic.
Cannot create path-model:java.lang.IllegalAccessException: void btools.router.KinematicModel.<init>() is not accessible from java.lang.Class<o.tl>
Quote from: zossebart on January 27, 2021, 14:00:38I don't have a specific request for confirmed parameters, despite maybe the kinematic model parameters (totalMass, Maxspeed etc.), which are brouter-builtin.
Quote from: zossebart on January 27, 2021, 14:00:38Yes, my request is to do it like brouter-web and dynamically parse and display all parameters from brf file.I don't have a specific request for confirmed parameters, despite maybe the kinematic model parameters (totalMass, Maxspeed etc.), which are brouter-builtin.All other parameters I would like to use mostly exist in single profiles only and therefor I wouldn't recommend adding them as supported to Locus just because of this one profile.For example, I created an enduro-motorcycle profile on user-request which has a "non-standard" parameter to switch the avoidance of paths, or I consider adding another parameter to influence uphill routing on paths to my mtb profile etc...). Without support for generic parameters, I would have to generate separate profiles of all permutations of profile parameters like libor does, but it gets confusing and it's not easily switcheable for example in a routeplanner session (if the profile-variants aren't already assigned to the (limited) slots in Locus).As I wrote before, I think it's ok that the default setting only shows the whitelisted parameters (as is now). But I would like to have the possibility to enable "full dynamic parameter" mode in expert settings for power-users (which you clearly embrace with locus (intens, url favourites, bt-buttons, dashboards, quick pois, presets...should I go on with the list? )).Maybe you could group the whitelisted parameters at the top of the settings dialog and show the other "non-standard" parameters below. Maybe with a caption "additional settings" and in a fainter color?
Quote from: tapio on March 03, 2021, 09:59:49Can the internal profiles be accessed from file system side? Didn't find them. Just curious.
Quote from: poutnikl on March 03, 2021, 12:19:53I think it would be good if the LoProfile modification has been explicitly listed in the profile comments. It will help with eventual coordinated development of the profile/template, not to be just a one-time action. E.g. I can include generation of explicit Loxxxx profile into my profile generation script, that creates on demand all profiles from the current template. This is not limited to my profiles, as the script can take and modify any profile posted on GitHub.Or, you can create a modified script version to generate LoProfiles from the current versions of the sources, unless you do not have it already.