In TrailWise, all 'paperwork' impediments to use of tracks are referred to as 'Restrictions'. Typically this will be a TRO (Traffic Regulation Order), a Voluntary Restraint request, a Permit to Use scheme, etc. This does NOT include physical problems like obstructions, washouts, narrowings, or illegal deterrants to use - please instead record these as 'Problem' features on the relevant track.
Before starting, gather the information you need; identify which track sections are affected (often more than one), any relevant dates, which kind of users are affected.
To actually enter details, start with one track and use the 'Restrictions' button. When complete, you can choose to add any further tracks to the same Restriction. Trailwise will try to provide a list of connected tracks to choose from.
Seasonal Restrictions
This will be a restriction that is in place only for certain periods during each year, every year. Such as a 'winter' closure. Be sure to specify dates in the right order so that TrailWise can work out which is the closure period - example Oct 31 to Mar 1 for a 'winter' effect.
Temporary Restrictions
This will be a restriction that is a one-off event, in place only until a certain date - example 'closed for repairs until Sept 1st 2010'. (Formal 'Emergency TROs' are just a special case of a temporary closure.)
Width or Weight Restrictions etc.
TrailWise assumes all TROs are prohibitive for the given user classes. However, something like a width restriction will only affect some vehicles. The recommendation is to record such limitations as an 'Other Official Restriction' type, rather than a normal TRO. With some explanatory text of course! This will be treated as a warning to all affected users rather than outright prohibition.
Multiple Restrictions
It's perfectly possible to have more than one Restriction affecting the same track or groups of tracks. For example a track may have a permanent TRO for 4-wheel motors and a seasonal VR for motorbikes; just enter each restriction as appropriate.
Complex Restrictions
Some rare restrictions may be more complex than TrailWise provides for at first glance - for example, a TW Restriction can only provide for one 'season' of closure, yet there exist TROs with two seasons per year. In that case we can break the complex TRO down into simpler units, and enter as two Restrictions each of a single season. Comments can be added to explain the 'cheat'.
Expired Restrictions
A record is kept for reference of any kind of restriction that has passed its end date (if one is set). So any given track might have a succession of expired temporary TROs if repairs are carried out often. Such expired restrictions don't get taken into account by TrailWise when working out current status.
In the case of 'Voluntary Restraint' requests, please do ensure such requests are founded along LARA-style guidelines - based on agreement between authorities, user representatives, and perhaps landowners. TrailWise is not a means of promoting dictates - merely a means to advertise genuine agreements to the widest audience.

Home
FAQ
Contact
Register
Login
Tracks
Maps