All roads in Grey County. Intersection-to-intersection segments are continuously updated monthly to maintain accurate addressing. Captured at various scales from 1:5000 - 1:20,000 depending on location and jurisdiction. Original source data derived from Ontario Ministry of Natural Resources and Forestry Ontario Road Network (ORN).
Field
Name
Alias
Data Type
Description
OBJECTID OBJECTID Object ID GIS Unique identifier
ROAD_NAME ROAD NAME Text Full official road name composed of individual street name components where present, including street name body, street type suffix and directional suffix.
ROAD_NAME_ABBR ROAD NAME ABBREVIATED Text Abbreviated version of road name (E.g. 10th Ave E instead of 10th Avenue East)
ALT_NAME ALTERNATE NAME Text Full alternate road name. This is typically county or provincial highways when a local municipality street name is provided as the official road name. Should be null if no alternate name exists
STREET_NAM STREET_NAM Text Street name body only, the identifying named component of a street name
STREET_TYP STREET_TYP Text Street type (non-abbreviated)
STREET_TYP_SHORT STREET TYPE SHORT Text Street type (abbreviated)
STREET_DIR STREET_DIR Text Street direction (non-abbreviated)
STREET_DIR_SHORT STREET DIRECTION SHORT Text Street direction (abbreviated)
STREET_CLA STREET_CLA Short Street class used to facilitate mapping. Values can be Highways (1), County roads (2), Municipal roads (3), Unmaintained roads (4) and Roads under construction (5)
L_F_ADD L_F_ADD Long Left - From address range
L_T_ADD L_T_ADD Long Left - To address range
R_F_ADD R_F_ADD Long Right - From address range
R_T_ADD R_T_ADD Long Right - To address range
VERIFY VERIFY Short Unchanged (0), or Changed/updated (1). Values of 1 have underwent a modification since data inception, and should have a change log description in the VERIFY_COM field
VERIFY_COM VERIFY_COM Text Logged comments to describe changes to road data during verification
DATE_ADD DATE_ADD Date Date road created in geodatabase. Initialize date was 1/1/2004
HWY_NUM HWY_NUM Text MTO Highway Number
GREYRD_NUM GREYRD_NUM Text Grey Road Number
EDITOR EDITOR Text Last user who edited data
CLOSE_DETR CLOSURE DETOURS Text Roads that are suitable or not suitable for public traffic detours, completed in NOV2013, only those not suitable for detours have been captured. One record marked partial - not Minto-Normanby townline is not passable from Sideroad 25 to Ski Road (Wellington Co.)
EDIT_DATE EDIT_DATE Date Last time data was edited
JURIS_L LEFT JURISDICTION Text Road owner and authority having jurisdiction, who issues permits for the road left segment. May be governed by MTO connecting link or boundary agreement
JURIS_R RIGHT JURISDICTION Text Road owner and authority having jurisdiction, who issues permits for the road right segment. May be governed by MTO connecting link or boundary agreement
MUNICIPAL_L LEFT MUNICIPALITY Text Lower Tier Municipality, determined by the traversal from the "L_F_ADD" to the "L_T_ADD"
MUNICIPAL_R RIGHT MUNICIPALITY Text Lower Tier Municipality, determined by the traversal from the "R_F_ADD" to the "R_T_ADD"
MUN911_L LEFT 911 MUN SHORT Text 3 character municipal name used for 911 CAD, abbreviated version of MUNICIPAL_L.
MUN911_R RIGHT 911 MUN SHORT Text 3 character municipal name used for 911 CAD, abbreviated version of MUNICIPAL_R.
PARITY_L LEFT PARITY Text The even or odd property of the address number range on the Left side of the road segment relative to the FROM address: O=Odd; E=Even; B=Both
PARITY_R RIGHT PARITY Text The even or odd property of the address number range on the Right side of the road segment relative to the FROM address: O=Odd; E=Even; B=Both
ORN_ROAD_CLASS ORN ROAD CLASS Short Road classification per ORN
PAVED_STATUS PAVED STATUS Short Paved (1), Unpaved (2)
DIR_OF_TRAFFIC_FLOW DIR OF TRAFFIC FLOW Short The direction(s) of vehicular or motor traffic flow. Both (1), Positive (2), Negative (3)
MAINT_SUMMER MAINTENANCE SUMMER Text Jurisdiction responsible for summer maintenance
MAINT_WINTER MAINTENANCE WINTER Text Jurisdiction responsible for winter maintenance
MAINT_AGREEMENT MAINTENANCE AGREEMENT Text The agreement record that outlines seasonal maintenance responsibilities (Alfresco/sharepoint url)
BOUNDARY_ROAD BOUNDARY ROAD Text Indicates if a road segment runs along a municipal or county boundary (Yes/No)
ROAD_LENGT ROAD LENGTH (m) Double Length of Road Segment in meters. Geometry of line segment calculated in GIS with UTM NAD83 Zone 17N coordinate system
LANE_COUNT LANE COUNT Short Number of Lanes
SPEED_LIMI SPEED LIMIT Short Speed limit in km/h
Shape Shape Geometry Auto generated line geometry in GIS
Shape.STLength() Shape.STLength() Double Auto generated pseudo length in GIS. Due to the web coordinate system used, this is not the true length.
Karst areas found in Grey County from 2018 Official Plan, Appendix A.
Bruce County polygon layer showing the boundary of each municipality.
This map reflects the road cycling routes in Grey County.
Bruce County Assessment Parcels are maintained by the County of Bruce on an ongoing basis. The Date Updated value shown here is meaningless because the layer is in fact updated many times each month.Note: Your download will include data from whatever portion of the county is visible in the map above. If you zoom in, open the Download menu, and choose an option under Filtered Dataset, what you receive will cover just that area.
The Digital Geologic-GIS Map of parts of the Zapata Ranch and Mosca Pass Quadrangles, Colorado is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (zara_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (zara_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (grsa_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (grsa_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (zara_geology_metadata_faq.pdf). Please read the grsa_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (zara_geology_metadata.txt or zara_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
Recreational trails mapped throughout Bruce County. Included are trails in County Forests, Rail Trails, and municipal trails as already published in Bruce County Map Book and elsewhere.
Aggregate Resource Areas in Grey County from 2018 Official Plan, Schedule B are defined as lands with high quality sand and gravel resources (often referred to as aggregate resources), which may be needed for future resource extraction.
https://maps.grey.ca/pages/termshttps://maps.grey.ca/pages/terms
Verified alcohol vendors in Grey and Bruce County
This data is part of the series of maps that covers the whole of Australia at a scale of 1:250 000 (1cm on a map represents 2.5km on the ground) and comprises 513 maps. This is the largest scale at which published topographic maps cover the entire continent. Data is downloadable in various distribution formats.
The Unpublished Digital Geologic-GIS Map of Parts of Great Sand Dunes National Park and Preserve (Sangre de Cristo Mountains and part of the Dunes), Colorado is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (gsam_geology.gdb), a 10.1 ArcMap (.mxd) map document (gsam_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (grsa_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (grsa_geology_gis_readme.pdf). Please read the grsa_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. Google Earth software is available for free at: http://www.google.com/earth/index.html. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (gsam_geology_metadata.txt or gsam_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in Google Earth, ArcGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 13N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Great Sand Dunes National Park and Preserve.
The Unpublished Digital Geologic-GIS Map of parts of the Twin Peaks and Blanco Peak Quadrangles, Colorado is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (tpbp_geology.gdb), a 10.1 ArcMap (.mxd) map document (tpbp_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (grsa_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (grsa_geology_gis_readme.pdf). Please read the grsa_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). Presently, a GRI Google Earth KMZ/KML product doesn't exist for this map. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (tpbp_geology_metadata.txt or tpbp_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 13N. The data is within the area of interest of Great Sand Dunes National Park and Preserve.
The Digital Geologic-GIS Map of the Medano Pass Quadrangle, and parts of the Liberty Quadrangle, Colorado is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (mepa_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (mepa_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (grsa_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (grsa_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (mepa_geology_metadata_faq.pdf). Please read the grsa_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (mepa_geology_metadata.txt or mepa_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
Bedrock Drift Thickness areas in Grey County from 2018 Official Plan, Appendix E:Selected Bedrock Resource Area - Drift ThicknessPaleozoic bedrock outcrop; areas of exposed bedrock partially covered by a thin veneer of drift. Drift thickness is generally less than 1 m.Paleozoic bedrock outcrop covered by drift. Drift thickness is generally 1 to 8 m. Bedrock outcrops may occur.
The Significant Woodlands layer was refined in 2017 by using data collected as part of the Natural Heritage Systems Study – Green in Grey, data from the MNRF and through airphoto analysis. In order to be considered significant, a woodland shall be either greater than or equal to forty (40) hectares in size outside of settlement areas, or greater than or equal to four (4) hectares in size within settlement area boundaries. If a woodland fails to meet the size criteria outside a settlement area, a woodland can also be significant if it meets any two of the following three criteria:Proximity to other woodlands i.e. if a woodland was within 30 meters of another significant woodland, orOverlap with the boundaries of a Provincially Significant Wetland and Significant Coastal Wetlands, Core Area, Significant Valleylands, or a Significant Areas of Natural and Scientific Interest , orInterior habitat of greater than or equal to eight (8) hectares, with a 100 meter interior buffer on all sides.
The Digital Geologic-GIS Map of the Beck Mountain and Crestone Peak Quadrangles, and parts of the Crestone Quadrangle, Colorado is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (bemo_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (bemo_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (grsa_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (grsa_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (bemo_geology_metadata_faq.pdf). Please read the grsa_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (bemo_geology_metadata.txt or bemo_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
https://www.ontario.ca/page/open-government-licence-ontariohttps://www.ontario.ca/page/open-government-licence-ontario
The soil complex database contains other descriptive information including slope class, Canada Land Inventory (CLI) ranking, stoniness, drainage class, texture etc. The CLI components of the data layer is generally intended to be used as a tool for broad land use planning decision making, and not necessarily for field-level management. The soil complex information can also be applied to source water protection, nutrient management and soil erosion modeling. Note: The soil complex data layer is subject to a continuous improvement strategy - data was last download August 2023.Ontario Ministry of Agriculture, Food, and Rural Affairs and Agriculture and Agri-Food Canada, in cooperation with the Ministry of Natural Resources, have compiled a geo-spatial soils database for Southern Ontario. The database consolidated the existing digital soil data mapped on a county basis into a digitally stitched and standardized product.The soil survey data was mapped by a number of soil surveyors from the 1920s to the 1990s. The Soil Ontario product incorporates soil information from a variety of map scales. The project has brought the individual county or regional municipality surveys together in a digitally stitched database which reveals inconsistencies in soil data across county boundaries. Using GIS and NRVIS (Natural Resource Values Information System) a GIS Specialist matched the soil polygons that crossed boundaries using the best available resources.
Visit https://www.grey.ca/resident-services/grey-transit-route for bus stop timetables.
Land boundary lines of Bruce County municipalities
All roads in Grey County. Intersection-to-intersection segments are continuously updated monthly to maintain accurate addressing. Captured at various scales from 1:5000 - 1:20,000 depending on location and jurisdiction. Original source data derived from Ontario Ministry of Natural Resources and Forestry Ontario Road Network (ORN).
Field
Name
Alias
Data Type
Description
OBJECTID OBJECTID Object ID GIS Unique identifier
ROAD_NAME ROAD NAME Text Full official road name composed of individual street name components where present, including street name body, street type suffix and directional suffix.
ROAD_NAME_ABBR ROAD NAME ABBREVIATED Text Abbreviated version of road name (E.g. 10th Ave E instead of 10th Avenue East)
ALT_NAME ALTERNATE NAME Text Full alternate road name. This is typically county or provincial highways when a local municipality street name is provided as the official road name. Should be null if no alternate name exists
STREET_NAM STREET_NAM Text Street name body only, the identifying named component of a street name
STREET_TYP STREET_TYP Text Street type (non-abbreviated)
STREET_TYP_SHORT STREET TYPE SHORT Text Street type (abbreviated)
STREET_DIR STREET_DIR Text Street direction (non-abbreviated)
STREET_DIR_SHORT STREET DIRECTION SHORT Text Street direction (abbreviated)
STREET_CLA STREET_CLA Short Street class used to facilitate mapping. Values can be Highways (1), County roads (2), Municipal roads (3), Unmaintained roads (4) and Roads under construction (5)
L_F_ADD L_F_ADD Long Left - From address range
L_T_ADD L_T_ADD Long Left - To address range
R_F_ADD R_F_ADD Long Right - From address range
R_T_ADD R_T_ADD Long Right - To address range
VERIFY VERIFY Short Unchanged (0), or Changed/updated (1). Values of 1 have underwent a modification since data inception, and should have a change log description in the VERIFY_COM field
VERIFY_COM VERIFY_COM Text Logged comments to describe changes to road data during verification
DATE_ADD DATE_ADD Date Date road created in geodatabase. Initialize date was 1/1/2004
HWY_NUM HWY_NUM Text MTO Highway Number
GREYRD_NUM GREYRD_NUM Text Grey Road Number
EDITOR EDITOR Text Last user who edited data
CLOSE_DETR CLOSURE DETOURS Text Roads that are suitable or not suitable for public traffic detours, completed in NOV2013, only those not suitable for detours have been captured. One record marked partial - not Minto-Normanby townline is not passable from Sideroad 25 to Ski Road (Wellington Co.)
EDIT_DATE EDIT_DATE Date Last time data was edited
JURIS_L LEFT JURISDICTION Text Road owner and authority having jurisdiction, who issues permits for the road left segment. May be governed by MTO connecting link or boundary agreement
JURIS_R RIGHT JURISDICTION Text Road owner and authority having jurisdiction, who issues permits for the road right segment. May be governed by MTO connecting link or boundary agreement
MUNICIPAL_L LEFT MUNICIPALITY Text Lower Tier Municipality, determined by the traversal from the "L_F_ADD" to the "L_T_ADD"
MUNICIPAL_R RIGHT MUNICIPALITY Text Lower Tier Municipality, determined by the traversal from the "R_F_ADD" to the "R_T_ADD"
MUN911_L LEFT 911 MUN SHORT Text 3 character municipal name used for 911 CAD, abbreviated version of MUNICIPAL_L.
MUN911_R RIGHT 911 MUN SHORT Text 3 character municipal name used for 911 CAD, abbreviated version of MUNICIPAL_R.
PARITY_L LEFT PARITY Text The even or odd property of the address number range on the Left side of the road segment relative to the FROM address: O=Odd; E=Even; B=Both
PARITY_R RIGHT PARITY Text The even or odd property of the address number range on the Right side of the road segment relative to the FROM address: O=Odd; E=Even; B=Both
ORN_ROAD_CLASS ORN ROAD CLASS Short Road classification per ORN
PAVED_STATUS PAVED STATUS Short Paved (1), Unpaved (2)
DIR_OF_TRAFFIC_FLOW DIR OF TRAFFIC FLOW Short The direction(s) of vehicular or motor traffic flow. Both (1), Positive (2), Negative (3)
MAINT_SUMMER MAINTENANCE SUMMER Text Jurisdiction responsible for summer maintenance
MAINT_WINTER MAINTENANCE WINTER Text Jurisdiction responsible for winter maintenance
MAINT_AGREEMENT MAINTENANCE AGREEMENT Text The agreement record that outlines seasonal maintenance responsibilities (Alfresco/sharepoint url)
BOUNDARY_ROAD BOUNDARY ROAD Text Indicates if a road segment runs along a municipal or county boundary (Yes/No)
ROAD_LENGT ROAD LENGTH (m) Double Length of Road Segment in meters. Geometry of line segment calculated in GIS with UTM NAD83 Zone 17N coordinate system
LANE_COUNT LANE COUNT Short Number of Lanes
SPEED_LIMI SPEED LIMIT Short Speed limit in km/h
Shape Shape Geometry Auto generated line geometry in GIS
Shape.STLength() Shape.STLength() Double Auto generated pseudo length in GIS. Due to the web coordinate system used, this is not the true length.