Metadata: Transit Route Timepoint Segments - Twin Cities Metropolitan Area

- View Sample -

Transit Route Timepoint Segments - Twin Cities Metropolitan Area

This page last updated: 12/12/2009
Metadata created using Minnesota Geographic Metadata Guidelines

Metadata Summary

Originator	Metropolitan Council and The Lawrence Group (TLG)
Abstract	The Transit Route Timepoint Segments layer contains fixed-route timepoint segments for routes in the Twin Cities metropolitan area. A transit segment is defined as a specific set of contiguous street centerlines with a defined Line-ID, Direction, From Node and To Node. Several segments make up a whole transit route (see the bus_routes_l shapefile). One shape and one corresponding record exists for each individual bus route segment. The line work for the dataset was derived from The Lawrence Group's and Metro Transit's street centerline dataset. Attributes include Segid, Line_id, Direction, From_node and To_node, Miles, Weekday/Saturday/Sunday Trips, and a decimal time for the first and last trip during Weekday/Saturday/Sunday service. Trip data, when known, is specific to the segment; when combined with bus stop information, it gives the most accurate picture of service frequency. For more generalized trip data, refer to the Transit Routes or Transit Route Street Service layers. For information regarding the Nodes (timepoints) and stops, see the Bus Stops layer. For information comparing the different transit GIS datasets distributed by the Met. Council, please see http://www.datafinder.org/metadata/transit_data_overview.pdf .
Browse Graphic	View a sample of the data.
Time Period of Content Date	12/12/2009
Currentness Reference	Route, segment, and stop information is accurate as of the above date. Includes linework from the TLG street centerline dataset released in June 2008.
Access Constraints	None
Use Constraints	None
Distributor Organization	Metropolitan Council
Ordering Instructions	This dataset is distributed on the internet by clicking below after 'Online Linkage'. Doing so will tell your browser to download a 'ZIP' file which will contain the following: - ArcView shape files - metadata for the dataset (.htm) - NOTICE.RTF, an important notice about this dataset that can be read by any word processing software. Additionally, this dataset is available for direct use via one or more map services. More information about what a web mapping service is can be found at http://www.datafinder.org/services/ The specific map service and layer name for this dataset can be found by clicking the blue or green boxes under the map service column of the DataFinder Catalog at http://www.datafinder.org/catalog/ .
Distribution Liability	NOTICE: The Geographic Information System (GIS) Data to which this notice is attached are made available pursuant to the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). THE GIS DATA ARE PROVIDED TO YOU AS IS AND WITHOUT ANY WARRANTY AS TO THEIR PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The GIS Data were developed by the Metropolitan Council for its own internal business purposes. The Metropolitan Council does not represent or warrant that the GIS Data or the data documentation are error-free, complete, current, or accurate. You are responsible for any consequences resulting from your use of the GIS Data or your reliance on the GIS Data. You should consult the data documentation for this particular GIS Data to determine the limitations of the GIS Data and the precision with which the GIS Data may depict distance, direction, location, or other geographic features. If you transmit or provide the GIS Data (or any portion of it) to another user, it is recommended that the GIS Data include a copy of this disclaimer and this metadata.
Online Linkage	I AGREE to the notice in "Distribution Liability" above. Clicking to agree will begin the download process (See Ordering Instructions above for details.)

Full Metadata

Transit Route Timepoint Segments - Twin Cities Metropolitan Area

Go to Section:
1. Identification Information
2. Data Quality Information
3. Spatial Data Organization Information
4. Spatial Reference Information
5. Entity and Attribute Information
6. Distribution Information
7. Metadata Reference Information


Section 1	Identification Information		Top of page
Originator	Metropolitan Council and The Lawrence Group (TLG)
Title	Transit Route Timepoint Segments - Twin Cities Metropolitan Area
Abstract	The Transit Route Timepoint Segments layer contains fixed-route timepoint segments for routes in the Twin Cities metropolitan area. A transit segment is defined as a specific set of contiguous street centerlines with a defined Line-ID, Direction, From Node and To Node. Several segments make up a whole transit route (see the bus_routes_l shapefile). One shape and one corresponding record exists for each individual bus route segment. The line work for the dataset was derived from The Lawrence Group's and Metro Transit's street centerline dataset. Attributes include Segid, Line_id, Direction, From_node and To_node, Miles, Weekday/Saturday/Sunday Trips, and a decimal time for the first and last trip during Weekday/Saturday/Sunday service. Trip data, when known, is specific to the segment; when combined with bus stop information, it gives the most accurate picture of service frequency. For more generalized trip data, refer to the Transit Routes or Transit Route Street Service layers. For information regarding the Nodes (timepoints) and stops, see the Bus Stops layer. For information comparing the different transit GIS datasets distributed by the Met. Council, please see http://www.datafinder.org/metadata/transit_data_overview.pdf .
Purpose	To identify all locations in the Twin Cities metropolitan area where fixed-route transit segments exist.
Time Period of Content Date	12/12/2009
Currentness Reference	Route, segment, and stop information is accurate as of the above date. Includes linework from the TLG street centerline dataset released in June 2008.
Progress	Complete
Maintenance and Update Frequency	Quarterly
Spatial Extent of Data	Twin Cities seven county metropolitan area. This includes the counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington in Minnesota.
Bounding Coordinates	-94.012 -92.732 45.415 44.471
Place Keywords	Twin Cities, Anoka County, Carver County, Dakota County, Hennepin County, Ramsey County, Scott County, Washington County
Theme Keywords	transit, buses, routes, segments, streets, roads, transportation
Theme Keyword Thesaurus	None
Access Constraints	None
Use Constraints	None
Contact Person Information	Jason Podany, Transit/GIS Planner Metropolitan Council - Metro Transit 560 6th Ave N Minneapolis, Minnesota 55411 Phone: 612-349-7714 FAX: 612-349-7675 E-mail: jason.podany@metc.state.mn.us
Browse Graphic	View a sample of the data.
Browse Graphic File Description	Example of TimepointSegments layer.
Associated Data Sets	- TLG Street Centerline and Address Range dataset. - bus service, routes and stops - For information comparing the different transit GIS datasets distributed by the Met. Council, please see http://www.datafinder.org/metadata/transit_data_overview.pdf .

Section 2	Data Quality Information	Top of full metadata	Top of page
Attribute Accuracy	A trip database produced by Transit Information was used to assign trips to the appropriate segments. First and last trip decimal times are averaged stop times for the from and to node of that segment. A trip timepoint database was used to determine average running times and miles per hour. Attributes are randomly checked by Metropolitan Council GIS staff.
Logical Consistency	The dataset is topologically 'clean'.
Completeness	The entire fixed-route transit network of the Twin Cities metropolitan area is included.
Horizontal Positional Accuracy	Positional accuracy varies throughout the dataset. Most line work in most counties falls within the road right of way, often near the center. Recent realignments by the TLG Street Centerline database have resulted in increased positional accuracy. Text below taken from TLG metadata: There are differing degrees of positional accuracy throughout the file. TLG adjusts the positional accuracy of the data to available sources known to have a greater degrees of accuracy then those used to generate the existing data. However, in all cases (including instances where COGO line work has been the reference) TLG generalizes the street segments to at least 4 feet in order to greatly reduce the number of vertices - thus reducing unnecessary file size and allowing for faster analysis. TLG's goal is to have 95% of roads located to within the approximate center of digital right-of-way data or pavement centerlines provided from counties, where such digital data is available. In other areas, 95% of roads are intended to be within ten meters of the road or right-of-way center.
Lineage	This dataset was created in Giro's Hastus scheduling software and referenced the TLG and Metro Transit street centerline dataset. See the metadata for the TLG Street Centerline layer for source information.
Source Scale Denominator

Section 3	Spatial Data Organization Information	Top of full metadata	Top of page
Native Data Set Environment	ArcView Version 3.x
Geographic Reference for Tabular Data	None
Spatial Object Type	Vector
Vendor Specific Object Types	arcs, nodes
Tiling Scheme	One layer for entire seven county region.

Section 4	Spatial Reference Information	Top of full metadata	Top of page
Horizontal Coordinate Scheme	UTM
Ellipsoid	GRS80
Horizontal Datum	NAD83
Horizontal Units	Meters
Distance Resolution
UTM Zone Number	15

Section 5	Entity and Attribute Information	Top of full metadata	Top of page

Entity and Attribute Overview

LINE ATTRIBUTES: 
  
SEGID:      A unique identifying number for each segment. 
  
LINE_ID:    A number identifying the route number associated with the bus and  
            its schedules.  Prefaced with an M for Metro Transit operated, and  
            P for Private Provider operated. 
  
DIRECTION:  0, or 1.  0 is for northbound or eastbound, 1 for southbound or  
            westbound. 
  
FROM_NODE:  Timepoint, aka Node, where segment begins. 
  
TO_NODE:    Timepoint, aka Node, where segment ends. 
 
MILES:      Length of the segment in miles. 
 
WKDY_TRIPS: The total number of trips made by this segment during a weekday. 
 
WKDY_FTRIP: The time of the first trip that segment makes on a weekday, in  
            decimal form. This time is the average between the stop times of  
            the two timepoints on either end of the segment. 
  
WKDY_LTRIP: The time of the last trip that segment makes on a weekday, in  
            decimal form. This time is the average between the stop times of  
            the two timepoints on either end of the segment. 
 
SAT_TRIPS:  The total number of trips made by this segment during a Saturday.   
 
SAT_FTRIP:  The time of the first trip that segment makes on a Saturday, in  
            decimal form. 
  
SAT_LTRIP:  The time of the last trip that segment makes on a Saturday, in  
            decimal form. 
  
SUN_TRIPS:  The total number of trips made by this segment during a Sunday.   
   
SUN_FTRIP:  The time of the first trip that segment makes on a Sunday, in  
            decimal form. 
  
SUN_LTRIP:  The time of the last trip that segment makes on a Sunday, in  
            decimal form. 
 
LINE_ID_N:  A numeric field identifying the route number associated with  
            the route and its schedules.

Entity and Attribute Detailed Citation

Section 6	Distribution Information	Top of full metadata	Top of page
Publisher	Metropolitan Council
Publication Date	Periodically revised
Contact Person Information	Mark Kotz GIS Database Administrator Metropolitan Council 390 Robert Street North St. Paul, Minnesota 55101-1805 Phone: 651-602-1644 FAX: 651-602-1674 E-mail: mark.kotz@metc.state.mn.us
Distributor's Data Set Identifier	TimepointSegments
Transfer Format Name	ArcView Shape File
Transfer Format Version Number	ArcView: 3x
Transfer Size	1.4 Meg. for self extracting ZIP file.
Ordering Instructions	This dataset is distributed on the internet by clicking below after 'Online Linkage'. Doing so will tell your browser to download a 'ZIP' file which will contain the following: - ArcView shape files - metadata for the dataset (.htm) - NOTICE.RTF, an important notice about this dataset that can be read by any word processing software. Additionally, this dataset is available for direct use via one or more map services. More information about what a web mapping service is can be found at http://www.datafinder.org/services/ The specific map service and layer name for this dataset can be found by clicking the blue or green boxes under the map service column of the DataFinder Catalog at http://www.datafinder.org/catalog/ .
Distribution Liability	NOTICE: The Geographic Information System (GIS) Data to which this notice is attached are made available pursuant to the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). THE GIS DATA ARE PROVIDED TO YOU AS IS AND WITHOUT ANY WARRANTY AS TO THEIR PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The GIS Data were developed by the Metropolitan Council for its own internal business purposes. The Metropolitan Council does not represent or warrant that the GIS Data or the data documentation are error-free, complete, current, or accurate. You are responsible for any consequences resulting from your use of the GIS Data or your reliance on the GIS Data. You should consult the data documentation for this particular GIS Data to determine the limitations of the GIS Data and the precision with which the GIS Data may depict distance, direction, location, or other geographic features. If you transmit or provide the GIS Data (or any portion of it) to another user, it is recommended that the GIS Data include a copy of this disclaimer and this metadata.
Online Linkage	I AGREE to the notice in "Distribution Liability" above. Clicking to agree will begin the download process (See Ordering Instructions above for details.)

Section 7	Metadata Reference Information	Top of full metadata	Top of page
Metadata Date	12/12/2009
Contact Person Information	Jason Podany, Transit/GIS Planner Metropolitan Council - Metro Transit 560 6th Ave N Minneapolis, Minnesota 55411 Phone: 612-349-7714 FAX: 612-349-7675 E-mail: jason.podany@metc.state.mn.us
Metadata Standard Name	Minnesota Geographic Metadata Guidelines
Metadata Standard Version	1.2
Metadata Standard Online Linkage	http://www.gis.state.mn.us/stds/metadata.htm

This page last updated: 12/12/2009