You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: open_data/hqta.py
+5-10
Original file line number
Diff line number
Diff line change
@@ -8,17 +8,11 @@
8
8
]
9
9
10
10
PURPOSE= ('''
11
-
Estimated High Quality Transit Areas as described in
12
-
Public Resources Code 21155, 21064.3, 21060.2.
11
+
Estimated High Quality Transit Areas as described in Public Resources Code 21155, 21064.3, 21060.2.
13
12
'''
14
13
)
15
14
16
-
METHODOLOGY= ('''
17
-
This data was estimated using a spatial process derived from General Transit Feed Specification (GTFS) schedule data. To find high-quality bus corridors, we split each corridor into 1,500 meter segments and counted frequencies at the stop within that segment with the highest number of transit trips. If that stop saw at least 4 trips per hour for at least one hour in the morning, and again for at least one hour in the afternoon, we consider that segment a high-quality bus corridor. Segments without a stop are not considered high-quality corridors. Major transit stops were identified as either the intersection of two high-quality corridors from the previous step, a rail or bus rapid transit station, or a ferry terminal with bus service. Note that the definition of “bus rapid transit” in Public Resources Code 21060.2 includes features not captured by available data sources, these features were captured manually using information from transit agency sources and imagery. We believe this data to be broadly accurate, and fit for purposes including overall dashboards, locating facilities in relation to high quality transit areas, and assessing community transit coverage. However, the spatial determination of high-quality transit areas from GTFS data necessarily involves some assumptions as described above. Any critical determinations of whether a specific parcel is located within a high-quality transit area should be made in conjunction with local sources, such as transit agency timetables.
18
-
19
-
Notes: Null values may be present. The "hqta_details" columns defines which part of the Public Resources Code definition the HQTA classification was based on. If "hqta_details" references a single operator, then "itp_id_secondary" and "agency_secondary" are null. If "hqta_details" references the same operator, then "itp_id_secondary" and "agency_secondary" are the same as "itp_id_primary" and "agency_primary".
20
-
'''
21
-
)
15
+
METHODOLOGY="This data was estimated using a spatial process derived from General Transit Feed Specification (GTFS) schedule data. To find high-quality bus corridors, we split each corridor into 1,500 meter segments and counted frequencies at the stop within that segment with the highest number of transit trips. If that stop saw at least 4 trips per hour for at least one hour in the morning, and again for at least one hour in the afternoon, we consider that segment a high-quality bus corridor. Segments without a stop are not considered high-quality corridors. Major transit stops were identified as either the intersection of two high-quality corridors from the previous step, a rail or bus rapid transit station, or a ferry terminal with bus service. Note that the definition of `bus rapid transit` in Public Resources Code 21060.2 includes features not captured by available data sources, these features were captured manually using information from transit agency sources and imagery. We believe this data to be broadly accurate, and fit for purposes including overall dashboards, locating facilities in relation to high quality transit areas, and assessing community transit coverage. However, the spatial determination of high-quality transit areas from GTFS data necessarily involves some assumptions as described above. Any critical determinations of whether a specific parcel is located within a high-quality transit area should be made in conjunction with local sources, such as transit agency timetables. Notes: Null values may be present. The `hqta_details` columns defines which part of the Public Resources Code definition the HQTA classification was based on. If `hqta_details` references a single operator, then `itp_id_secondary` and `agency_secondary` are null. If `hqta_details` references the same operator, then `itp_id_secondary` and `agency_secondary` are the same as `itp_id_primary` and `agency_primary`."
Document links, justification, for why datasets need to be made public. Submit this information every time a ticket is open to update the existing layers.
4
+
5
+
## Intranet Links
6
+
1.[Geospatial open data request](https://sv03tmcpo.ct.dot.ca.gov/portal/apps/sites/#/geep/pages/open-data-request)
7
+
1.[Open support ticket for GIS](https://sv03tmcpo.ct.dot.ca.gov/portal/apps/sites/#/geep/pages/support-request)
8
+
9
+
### High Quality Transit Areas
10
+
11
+
High Quality Transit Areas, as described in Public Resources Code 21155, 21064.3, 21060.2, relies on the intersection of frequent transit service. These are subject to the transit schedules available in the General Transit Feed Specification (GTFS). The California Integrated Travel Project within Caltrans ingests GTFS data daily for all operators in the state, standardizes, and processes this data for storage in its data warehouse.
12
+
13
+
Capturing where these HQTAs are is one expected spatial product from GTFS data. Given that GTFS data is always being updated by operators, whether it is to increase or reduce service,
14
+
this HQTA dataset also reflects the most recent boundaries given operator's latest scheduled trips.
15
+
16
+
### Transit Routes / Stops
17
+
18
+
The General Transit Feed Specification (GTFS) provides transit schedules, including transit route and stop information, in text files. The California Integrated Travel Project within Caltrans ingests GTFS data daily for all operators in the state, standardizes, and processes this data for storage in its data warehouse.
19
+
20
+
This dataset compiles all the route and stop information for all CA transit operators and provides it in a geospatial format. Transit routes are shown with their line geometry, and transit stops are shown with their point geometry. Given that GTFS data is always being updated by operators, whether it is to increase or reduce service, CA transit routes / transit stops datasets provide monthly snapshots for operators' latest schedules.
This data was estimated using a spatial process derived from General Transit Feed Specification (GTFS) schedule data. To find high-quality bus corridors, we split each corridor into 1,500 meter segments and counted frequencies at the stop within that segment with the highest number of transit trips. If that stop saw at least 4 trips per hour for at least one hour in the morning, and again for at least one hour in the afternoon, we consider that segment a high-quality bus corridor. Segments without a stop are not considered high-quality corridors. Major transit stops were identified as either the intersection of two high-quality corridors from the previous step, a rail or bus rapid transit station, or a ferry terminal with bus service. Note that the definition of “bus rapid transit” in Public Resources Code 21060.2 includes features not captured by available data sources, these features were captured manually using information from transit agency sources and imagery. We believe this data to be broadly accurate, and fit for purposes including overall dashboards, locating facilities in relation to high quality transit areas, and assessing community transit coverage. However, the spatial determination of high-quality transit areas from GTFS data necessarily involves some assumptions as described above. Any critical determinations of whether a specific parcel is located within a high-quality transit area should be made in conjunction with local sources, such as transit agency timetables.
64
-
65
-
Notes: Null values may be present. The "hqta_details" columns defines which part of the Public Resources Code definition the HQTA classification was based on. If "hqta_details" references a single operator, then "itp_id_secondary" and "agency_secondary" are null. If "hqta_details" references the same operator, then "itp_id_secondary" and "agency_secondary" are the same as "itp_id_primary" and "agency_primary".
66
-
</procdesc>
66
+
<procdesc>This data was estimated using a spatial process derived from General Transit Feed Specification (GTFS) schedule data. To find high-quality bus corridors, we split each corridor into 1,500 meter segments and counted frequencies at the stop within that segment with the highest number of transit trips. If that stop saw at least 4 trips per hour for at least one hour in the morning, and again for at least one hour in the afternoon, we consider that segment a high-quality bus corridor. Segments without a stop are not considered high-quality corridors. Major transit stops were identified as either the intersection of two high-quality corridors from the previous step, a rail or bus rapid transit station, or a ferry terminal with bus service. Note that the definition of `bus rapid transit` in Public Resources Code 21060.2 includes features not captured by available data sources, these features were captured manually using information from transit agency sources and imagery. We believe this data to be broadly accurate, and fit for purposes including overall dashboards, locating facilities in relation to high quality transit areas, and assessing community transit coverage. However, the spatial determination of high-quality transit areas from GTFS data necessarily involves some assumptions as described above. Any critical determinations of whether a specific parcel is located within a high-quality transit area should be made in conjunction with local sources, such as transit agency timetables. Notes: Null values may be present. The `hqta_details` columns defines which part of the Public Resources Code definition the HQTA classification was based on. If `hqta_details` references a single operator, then `itp_id_secondary` and `agency_secondary` are null. If `hqta_details` references the same operator, then `itp_id_secondary` and `agency_secondary` are the same as `itp_id_primary` and `agency_primary`.</procdesc>
0 commit comments