The config.JSON file contains editable configuration settings for the app. Some portions are useful for the user to be able to review within the App.
While the settings can be changed by altering the JSON file, v1 will add the ability to change settings and add new activities from within the app.
Track Criteria
All automated cleaning operations work by assuming min/max speeds, elevation gain, time/distances between points, etc.
Some are global and most are activity-specific (such as hiking).
 |  |  |
|---|
These are set in a config.JSON config file, and the results can be displayed in the app, both as set and as converted to the app's normalized units.
Below shows the global units for the settings. The ‘normalized’ column is a temporary reference showing the units converted to the consistent units always used in the app.
Units are specified higher up in a hierarchy, and optionally overwritten lower down the hierarchy tree for the remainder of a particular branch. For example, while the global length units are in ‘miles’ in this example, the units below for hiking elevation criteria indicate that they are feet. Since time is not overridden here or intermediate levels above, the ‘hours’ unit is still applied to time, so both of these rates are in 'feet/hr'.
Later development will show the precise set of units for each criterion on the criterion line and allow changing units at this display. Any units that are different from the current parent unit will be recorded as an appropriately local overwrite.
Attachments:
Options-TrackCriteria-480.gif (image/gif)
Controls_TrackCriteria_3_Activities.png (image/png)
Controls_TrackCriteria_2_Generic.png (image/png)
Controls_TrackCriteria.png (image/png)
Controls_TrackCriteria_1_Units.png (image/png)
Controls_TrackCriteria_1_Units_Override.png (image/png)
Controls_TrackCriteria_3_Activities_Details.png (image/png)
