Description: The data contained within this shp outlines the parking locations noted within the Bruce Trail Reference at the time of this data export. Terms Of Use: This data is for internal use only and is not to be shared with the public or any other agencies without the permission of the BTC. By accepting the receipt of this data, you are accepting the terms of use. Limit of Liability and Disclaimer: The information provided herein is presented "as is". The BTC, staff, volunteers or other organizations cannot be held liable for any inaccuracies that may occur within data as a whole. The BTC shall in no event be liable for any loss of profit or any other commercial damage, including but not limited to special, incidental, consequential, or other damages. It is important to note that parking locations are sometime closed whereas sometimes new parking locations are made available. All changes are displayed on our website http://brucetrail.org/pages/trail-changes NOTE: There are two point features for every parking area. One point feature is known as the "True Location" while the second point feature is known as the "Representation". The reason for displaying parking areas at their "True Location" is obvious. This data was created based on 2002 GTA & 2005 Swoop ortho imagery (slangley). The parking locations within the "Representation" dataset have been slightly repositioned from their true geographic location to a "best fit" location based on adjacent symbology in order to accomodate the size of the cartographic parking symbol and adjacent line work found within the 1:50K Bruce Trail Reference Maps. Attribute Description is as follows: NOTE: some attribute tables often need work! True Local = For large scale mapping 1:10K etc. Distinguishes between the following 4 parking classifications. To display only the "true location" of each parking area, use the following definition query to hide the "representation" features. NOT [True_Local] = 'Representation' Represent = For 1:50K mapping. Distinguishes between the following 4 parking classifications. To display only the "representation" of each parking area, use the following definition query to hide the "true location" parking features. NOT [Represent] = 'True Local' Parking Lot = A formal parking lot. Off Road = A parking area that of which is seemingly an informal yet obvious space for a few cars. Roadside = Parking on the shoulder of a road. This is deemed as "use at your own risk" parking for the reason that the BTC cannot always keep up to date in real time with changes to Municipal parking regulations on various roads. Description: A rough description/directions to the recommended parking. Cars: An approximate number cars that the area can accomidate. Date: The general date to which the recommended parking had been updated and/or verified as being legit. verified: = (y) means that this parking area has been verified by the local Bruce Trail club as being legit and suitable for publishing with in the BT Reference Guide.
STREET_ONEWAY
(
type: esriFieldTypeString, alias: ONE-WAY_STATUS, length: 1
, Coded Values:
[0: Two way street]
, [1: One way, same direction as digitized feature]
, [2: One way, against direction of digitized feature]
)
Description: Summary Updated: Apr 2013 - s.langley This dataset is internally updated by Scott Langley (BTC) on an ongoing basis as necessary. Contact Info: Scott Langley GIS Cartographer slangley@brucetrail.org 1 800 665 4453 ext.25 The data contained within this shp outlines the segments of the Bruce Trail (Main Trail & Side Trails). Limit of Liability and Disclaimer: The information provided herein is presented "as is". The BTC, staff, volunteers or other organizations cannot be held liable for any inaccuracies that may occur within data as a whole. The BTC shall in no event be liable for any loss of profit or any other commercial damage, including but not limited to special, incidental, consequential, or other damages. It is important to note that the Trail does change and gets rerouted from time to time. All reroutes are displayed on our website http://brucetrail.org/trail_changes Attribute Description is as follows: TRAIL_TYPE: Distinguishes between Main Trail & Side Trail (or Other Trail) TRAIL_NAME: All Side Trails have individual names. CLUB_SEC: The Bruce Trail is broken up into nine Club Sections along the Trail. Niagara Iroquoia Toronto Caledon Hills Dufferin Hi-Land Blue Mountains Beaver Valley Sydenham Peninsula SITE: Trail segments are broken into three simple categories. 1. Blazed (Trail that is not located on a traveled road or road allowance) 2. Road (Trail that is located on traveled road. Driveways and bush type roads are exempt) 3. Rd Allow (Trail located on a road allowance) CONT_OR: "Cont OR" defines active segments that are considered to be Optimum Route. DISCLAIMER: The BTC, staff, volunteers or other organizations cannot be held liable for any inaccuracies that may occur within this data.
Service Item Id: 74977518d75d4dc99bbd77a4c7106590
Copyright Text: Scott Langley
(Received from BTC 29 June 2015)
STREET_ONEWAY
(
type: esriFieldTypeString, alias: ONE-WAY_STATUS, length: 1
, Coded Values:
[0: Two way street]
, [1: One way, same direction as digitized feature]
, [2: One way, against direction of digitized feature]
)
STREET_ONEWAY
(
type: esriFieldTypeString, alias: ONE-WAY_STATUS, length: 1
, Coded Values:
[0: Two way street]
, [1: One way, same direction as digitized feature]
, [2: One way, against direction of digitized feature]
)
STREET_ONEWAY
(
type: esriFieldTypeString, alias: ONE-WAY_STATUS, length: 1
, Coded Values:
[0: Two way street]
, [1: One way, same direction as digitized feature]
, [2: One way, against direction of digitized feature]
)
STREET_ONEWAY
(
type: esriFieldTypeString, alias: ONE-WAY_STATUS, length: 1
, Coded Values:
[0: Two way street]
, [1: One way, same direction as digitized feature]
, [2: One way, against direction of digitized feature]
)
STREET_ONEWAY
(
type: esriFieldTypeString, alias: ONE-WAY_STATUS, length: 1
, Coded Values:
[0: Two way street]
, [1: One way, same direction as digitized feature]
, [2: One way, against direction of digitized feature]
)
STREET_ONEWAY
(
type: esriFieldTypeString, alias: ONE-WAY_STATUS, length: 1
, Coded Values:
[0: Two way street]
, [1: One way, same direction as digitized feature]
, [2: One way, against direction of digitized feature]
)