survey_title
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: Alberta Parks Wayfinding Program Survey, type: esriFieldTypeString
)
purpose
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: This survey is to be completed by Alberta Parks Division staff working with the Wayfinding Sign Program with the purpose of collecting program feedback for future updates. Thank you for taking the time to answer this survey., type: esriFieldTypeString
)
instructions
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: We respect your privacy. Any personal information you provide in the survey is protected by the privacy provisions of the Freedom of Information and Protection of Privacy Act. If you have any questions about the privacy of this information, please contact Alberta Parks by e-mail at AlbertaParksSurvey@gov.ab.ca, type: esriFieldTypeString
)
expectations
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: 1. Does the wayfinding program meet your expectations and park/facility/visitor needs with regards to…, type: esriFieldTypeString
)
exp_specify
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: Please provide details of how these components of the Wayfinding Program are not meeting your expectations., type: esriFieldTypeString
)
signs
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: 2.Question: Should Alberta Parks continue to use Alberta Parks’ Traffic Regulation signs inside of our Parks OR should Alberta Parks begin to transition all Traffic Regulation signs (when being replaced) to Alberta Transportation's Traffic Regulation signs?
Background: Currently Alberta Parks primarily uses its own design standard for Traffic Regulation signs (stop, yield, speed, do not enter, etc.), but uses Alberta Transportation's Traffic Regulation signs at major intersections bisecting non-park roads and along non-park roadways. Some parks have experienced problems in court with tickets citing the traffic safety act.
Alberta Transportation Traffic Regulation signs are larger than Parks standards and have an increased cost. For example:
Parks Speed Limit sign: 600x600mm costs $44.95
Alberta Transportation Speed Limit sign: 600x750mm costs $59.99, type: esriFieldTypeString
)
sign_regulations
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: Please select your preference:, type: esriFieldTypeString
, Coded Values:
[0: Continue to use Alberta Parks Traffic Regulation signs in combination with Alberta Transportation Traffic Regulation signs]
, [1: Transition to ONLY using Alberta Transportation's Traffic Regulation signs for all instances]
, [2: Other (please specify below)]
)
trail_signs
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: Please select from the following options:, type: esriFieldTypeString
, Coded Values:
[1: 1 - Not at all]
, [2: 2]
, [3: 3 - Somewhat]
, ...2 more...
)
trail_signs_spec
(
nullable: true, editable: true, defaultValue: null, length: 2000, alias: Do you have any suggestions to improve the current directional trail sign options?, type: esriFieldTypeString
)
refl_signs_note
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: 4. Should the wayfinding program move away from all trail signs being reflective to:, type: esriFieldTypeString
)
refl_signs
(
nullable: true, editable: true, defaultValue: null, length: 255, alias: Please select from the following options:, type: esriFieldTypeString
, Coded Values:
[1: All reflective]
, [2: All non-reflective]
, [3: Based on location]
)
refl_signs_spec
(
nullable: true, editable: true, defaultValue: null, length: 2000, alias: Please add any additional comments about sign reflectivity here (optional), type: esriFieldTypeString
)
improvement
(
nullable: true, editable: true, defaultValue: null, length: 2000, alias: 5. Do you have any additional comments on future enhancements and updates to the Wayfinding Program?, type: esriFieldTypeString
)