Matanuska Greenbelt Special Event Permit Application
January 15, 2015 (page rev Feb 13, 2015)
(For those looking for emergency and safety planning maps and documents, please see files 4 and 7 in Files needed. They have 5 ***** in red next to them)
To have more consistent race permitting procedures,
the agencies in the Matanuska Greenbelt began implementing an Interagency Race
Permit Application procedure in 2014. Race fees will contribute toward trail
maintenance throughout the system. The agencies and contacts include
Matanuska Lakes State Recreation Area – Alaska State Parks, Wayne Biessel, 745-8935, email@example.com
Matanuska Experiment Farm -- University of Alaska Fairbanks, Norm Harris, 746-9475, firstname.lastname@example.org
Mat-Su College – University of Alaska Anchorage, Patrick Kelly, 786-7795, email@example.com
Note: This information is current as of May 18, 2016, but could be modified again. Contact the above people for whichever trailhead your event uses for the most current information. The intent is to improve safety for these events as well as help maintain the resource.
Do you need
this interagency permit application? (see above note)
If your event does not cross property boundaries, check with the administrator or designee for the trailhead where you will be starting and finishing as to which permit to use. They may have their own or have you use a modified procedure with the interagency application. While this was originally a race permit (competitive event), we're learning that some non-race events are much larger and should probably be providing much of the same information.
Differences in maps:
Print vs Interactive
.pdf / print versions are at a fixed scale and fixed features. These maps use the 2011 MSB imagery.
Online / interactive maps can be zoomed in/out, layers can be turned on/off, and some revisions can be made. Selecting a feature (such as trail, post, gate) pops up a window with more details, like lat/long. You do not have to sign up for access. The interactive maps use backgrounds provided by ESRI – terrain as well as image backgrounds are available.
If you use the interactive versions, you can add your race course (easy to add .gpx file from your gps), volunteer locations, and other features, then save it in your account on ArcGIS online. (These are free with some limitations on usage.) Make the map public. You can also just print out what you need and draw race features on it.
Regular vs Emergency Planning maps
Regular user maps were developed to help people find their way back to cars and provide some idea of types of trails, but have since evolved with the signs to have more detail. (These are maps on http://www.matanuska-greenbelt.org/trail-maps)
Purpose of emergency planning maps: To provide information for
(1) Event planners / race directors to plan for reaching injured participants somewhere near their race course. (Self rescue vs calling 911, where possible)
(2) First responders to retrieve missing or injured people. Palmer Fire and Rescue is the first response for lost/injured people in this area, but we are working with MSB units also.
(3) Other people working on emergency responses
How do emergency planning maps differ from regular maps. These were developed with suggestions from emergency responders or trail users needing a map for emergency planning.
Numbers work their way outbound from each trailhead - starting with the westernmost trails for CMT and MLSRA and working east; starting with northernmost trails and working south for the College and Farm. This assumed system expansion was heading east.
The colors and icons may differ between the .pdf / print and interactive version
Most of these procedures are intended to help manage the resources and enhance experiences for users - both racers and non-racers.
If you have questions about general procedures, please contact Wayne Biessel <firstname.lastname@example.org>
Contacts for individual units are listed at top of page.
If you have problems with downloads, entering data in application, or other technical issues, contact email@example.com. Describe issue including software (program and version - this is probably the most important), make/model of computer, operating system.