-
Notifications
You must be signed in to change notification settings - Fork 0
/
features
9 lines (9 loc) · 2.18 KB
/
features
1
2
3
4
5
6
7
8
9
understands the concepts of Bases, Routes (a simple series of Bases), Teams and (Base) Reports (which includes a notes section)
determines whether a Team has been through a given Base, and hence if every Team on applicable Routes has gone through a given Base (ready to pack up), the number of bases a Team has missed on its Route (and hence whether they've completed the entire Route) or even a simple timeline of a Team's movement
calculates the distance between two Bases, either direct or along the length of a given Route, using either given distances or displacement based on grid references (to any specified accuracy) and a configurable "wiggle factor"; similarly for height gain calculations; gives the total length of a Route
determines whether a Team has finished (arrived at final Base) or gone off Route (last known location not on Route) or give its last known location
gives a Team's statistics including walked distance, walking time, waiting at a Base time and average walking speed
all of the above bits and pieces culminate in the first actually useful function: determining the ETA of a Team at a given Base (next in route by default) by either using its average walking speed, or a set walking speed (for when a guaranteed underestimate is needed); ETA is continually updated with all the necessary information e.g. it will always calculate from the last known location and will give the ATA if the Team has already visited the given base; it makes use of naithsmith's rule for including the height gain into timings
determines the earliest and latest etas at a Base (useful for determining opening/closing times) with the opportunity to use both an underestimated walking speed and an overestimated speed, leading to extremely accurate outside limits
provides early warning of a Team's tardiness, with a configurable leeway, e.g. you might want a list of all Teams that are more than 30 mins overdue
stores the hike setup information for re-use, or for setting up in advance ready to use on the hike day; the information can be given in multiple ways, e.g. the distances between Bases can be simply defined along a Route, or automatic Team generation such as 12 teams on this route starting 6 minutes apart