diff --git a/.devcontainer/compose.yml b/.devcontainer/compose.yml
index 945490af..9e3d94b3 100644
--- a/.devcontainer/compose.yml
+++ b/.devcontainer/compose.yml
@@ -4,8 +4,5 @@ services:
context: ..
dockerfile: .devcontainer/Dockerfile
command: sleep infinity
- ports:
- - "4000"
- - "35729:35729"
volumes:
- ..:/usr/src/calitp
diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
index d5380219..7b73590d 100644
--- a/.devcontainer/devcontainer.json
+++ b/.devcontainer/devcontainer.json
@@ -4,20 +4,24 @@
"service": "site",
"workspaceFolder": "/usr/src/calitp",
"postAttachCommand": ["/bin/bash", ".devcontainer/postAttach.sh"],
- "settings": {
- "terminal.integrated.defaultProfile.linux": "bash",
- "terminal.integrated.profiles.linux": {
- "bash": {
- "path": "/bin/bash"
- }
+ "customizations": {
+ "vscode": {
+ "settings": {
+ "terminal.integrated.defaultProfile.linux": "bash",
+ "terminal.integrated.profiles.linux": {
+ "bash": {
+ "path": "/bin/bash"
+ }
+ }
+ },
+ "extensions": [
+ "bungcip.better-toml",
+ "eamodio.gitlens",
+ "esbenp.prettier-vscode",
+ "mhutchie.git-graph",
+ "redhat.vscode-xml",
+ "sissel.shopify-liquid"
+ ]
}
- },
- "extensions": [
- "bungcip.better-toml",
- "eamodio.gitlens",
- "esbenp.prettier-vscode",
- "mhutchie.git-graph",
- "redhat.vscode-xml",
- "sissel.shopify-liquid"
- ]
+ }
}
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
new file mode 100644
index 00000000..9b35196a
--- /dev/null
+++ b/.github/CODEOWNERS
@@ -0,0 +1,2 @@
+# default to web-admin team
+* @cal-itp/web-admin
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
new file mode 100644
index 00000000..c2e9e819
--- /dev/null
+++ b/.github/dependabot.yml
@@ -0,0 +1,27 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+ - package-ecosystem: "bundler" # See documentation for possible values
+ directory: "/" # Location of Gemfile
+ schedule:
+ interval: "daily"
+ commit-message:
+ prefix: "chore"
+ include: "scope"
+ labels:
+ - "dependencies"
+ - package-ecosystem: "github-actions"
+ # Workflow files stored in the
+ # default location of `.github/workflows`
+ directory: "/"
+ schedule:
+ interval: "daily"
+ commit-message:
+ prefix: "chore"
+ include: "scope"
+ labels:
+ - "dependencies"
diff --git a/.github/workflows/dependabot-differ.yaml b/.github/workflows/dependabot-differ.yaml
index 102ecedd..11bd821b 100644
--- a/.github/workflows/dependabot-differ.yaml
+++ b/.github/workflows/dependabot-differ.yaml
@@ -13,7 +13,7 @@ jobs:
if: contains(github.event.pull_request.labels.*.name, 'dependencies') # See https://git.io/JsVv1
steps:
- name: Checkout Pull Request Branch
- uses: actions/checkout@v2
+ uses: actions/checkout@v3
with:
ref: ${{ github.event.pull_request.head.sha }}
submodules: true
@@ -21,7 +21,7 @@ jobs:
- name: Setup Ruby
uses: ruby/setup-ruby@v1
with:
- ruby-version: 2.6
+ ruby-version: 3.1
bundler-cache: true
- name: Build Pull Request Version of Website
@@ -31,9 +31,9 @@ jobs:
mv _site _site-pr
- name: Checkout Default Branch
- uses: actions/checkout@v2
+ uses: actions/checkout@v3
with:
- ref: core
+ ref: staging
clean: false
submodules: true
@@ -70,7 +70,7 @@ jobs:
echo "::set-output name=pr-comment::$PR_COMMENT"
- name: Comment on the Pull Request
- uses: peter-evans/create-or-update-comment@v1
+ uses: peter-evans/create-or-update-comment@v3
with:
issue-number: ${{ github.event.pull_request.number }}
body: ${{ steps.site-diff.outputs.pr-comment }}
diff --git a/.gitignore b/.gitignore
index a064b2ce..bd16e28d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@
.bundle
.netlify
_site
+.DS_Store
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 7e333217..121fa7a0 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -15,7 +15,7 @@ default_stages:
repos:
- repo: https://github.com/compilerla/conventional-pre-commit
- rev: v2.2.0
+ rev: v2.3.0
hooks:
- id: conventional-pre-commit
stages: [commit-msg]
diff --git a/.vscode/settings.json b/.vscode/settings.json
index 49b32056..5fed93a2 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -6,13 +6,8 @@
"files.insertFinalNewline": true,
"files.trimFinalNewlines": true,
"files.trimTrailingWhitespace": true,
- "[javascript]": {
- "editor.tabSize": 2
- },
- "[json]": {
- "editor.tabSize": 2
- },
- "[markdown]": {
- "editor.defaultFormatter": "esbenp.prettier-vscode"
+ "editor.tabSize": 2,
+ "files.associations": {
+ "*.html": "liquid"
}
}
diff --git a/CONDUCT.md b/CONDUCT.md
deleted file mode 100644
index ed36699b..00000000
--- a/CONDUCT.md
+++ /dev/null
@@ -1,133 +0,0 @@
-
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
- and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
- overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
- advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
- address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-support@compiler.la.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
-at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations
diff --git a/Gemfile b/Gemfile
index 3149ca1b..5eb50c47 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,5 +1,4 @@
-source "https://rubygems.org"
-
-gem "jekyll", "~> 4.2.0"
-gem "rubyzip", "~> 2.3"
-gem "webrick", "~> 1.7"
+source "https://rubygems.org"
+
+gem "jekyll", "~> 4.3.2"
+gem "rubyzip", "~> 2.3"
diff --git a/Gemfile.lock b/Gemfile.lock
index 3fed0cc5..cd4a1df7 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,73 +1,78 @@
-GEM
- remote: https://rubygems.org/
- specs:
- addressable (2.8.0)
- public_suffix (>= 2.0.2, < 5.0)
- colorator (1.1.0)
- concurrent-ruby (1.1.7)
- em-websocket (0.5.2)
- eventmachine (>= 0.12.9)
- http_parser.rb (~> 0.6.0)
- eventmachine (1.2.7)
- ffi (1.14.2)
- forwardable-extended (2.6.0)
- http_parser.rb (0.6.0)
- i18n (1.8.6)
- concurrent-ruby (~> 1.0)
- jekyll (4.2.0)
- addressable (~> 2.4)
- colorator (~> 1.0)
- em-websocket (~> 0.5)
- i18n (~> 1.0)
- jekyll-sass-converter (~> 2.0)
- jekyll-watch (~> 2.0)
- kramdown (~> 2.3)
- kramdown-parser-gfm (~> 1.0)
- liquid (~> 4.0)
- mercenary (~> 0.4.0)
- pathutil (~> 0.9)
- rouge (~> 3.0)
- safe_yaml (~> 1.0)
- terminal-table (~> 2.0)
- jekyll-sass-converter (2.1.0)
- sassc (> 2.0.1, < 3.0)
- jekyll-watch (2.2.1)
- listen (~> 3.0)
- kramdown (2.3.1)
- rexml
- kramdown-parser-gfm (1.1.0)
- kramdown (~> 2.0)
- liquid (4.0.3)
- listen (3.4.0)
- rb-fsevent (~> 0.10, >= 0.10.3)
- rb-inotify (~> 0.9, >= 0.9.10)
- mercenary (0.4.0)
- pathutil (0.16.2)
- forwardable-extended (~> 2.6)
- public_suffix (4.0.6)
- rb-fsevent (0.10.4)
- rb-inotify (0.10.1)
- ffi (~> 1.0)
- rexml (3.2.5)
- rouge (3.26.0)
- rubyzip (2.3.0)
- safe_yaml (1.0.5)
- sassc (2.4.0)
- ffi (~> 1.9)
- terminal-table (2.0.0)
- unicode-display_width (~> 1.1, >= 1.1.1)
- unicode-display_width (1.7.0)
- webrick (1.7.0)
-
-PLATFORMS
- ruby
- x86_64-darwin-19
- x86_64-linux
-
-DEPENDENCIES
- jekyll (~> 4.2.0)
- rubyzip (~> 2.3)
- webrick (~> 1.7)
-
-BUNDLED WITH
- 2.2.4
+GEM
+ remote: https://rubygems.org/
+ specs:
+ addressable (2.8.4)
+ public_suffix (>= 2.0.2, < 6.0)
+ colorator (1.1.0)
+ concurrent-ruby (1.2.2)
+ em-websocket (0.5.3)
+ eventmachine (>= 0.12.9)
+ http_parser.rb (~> 0)
+ eventmachine (1.2.7)
+ ffi (1.15.5)
+ forwardable-extended (2.6.0)
+ google-protobuf (3.23.4)
+ google-protobuf (3.23.4-x86_64-darwin)
+ google-protobuf (3.23.4-x86_64-linux)
+ http_parser.rb (0.8.0)
+ i18n (1.14.1)
+ concurrent-ruby (~> 1.0)
+ jekyll (4.3.2)
+ addressable (~> 2.4)
+ colorator (~> 1.0)
+ em-websocket (~> 0.5)
+ i18n (~> 1.0)
+ jekyll-sass-converter (>= 2.0, < 4.0)
+ jekyll-watch (~> 2.0)
+ kramdown (~> 2.3, >= 2.3.1)
+ kramdown-parser-gfm (~> 1.0)
+ liquid (~> 4.0)
+ mercenary (>= 0.3.6, < 0.5)
+ pathutil (~> 0.9)
+ rouge (>= 3.0, < 5.0)
+ safe_yaml (~> 1.0)
+ terminal-table (>= 1.8, < 4.0)
+ webrick (~> 1.7)
+ jekyll-sass-converter (3.0.0)
+ sass-embedded (~> 1.54)
+ jekyll-watch (2.2.1)
+ listen (~> 3.0)
+ kramdown (2.4.0)
+ rexml
+ kramdown-parser-gfm (1.1.0)
+ kramdown (~> 2.0)
+ liquid (4.0.4)
+ listen (3.8.0)
+ rb-fsevent (~> 0.10, >= 0.10.3)
+ rb-inotify (~> 0.9, >= 0.9.10)
+ mercenary (0.4.0)
+ pathutil (0.16.2)
+ forwardable-extended (~> 2.6)
+ public_suffix (5.0.3)
+ rake (13.0.6)
+ rb-fsevent (0.11.2)
+ rb-inotify (0.10.1)
+ ffi (~> 1.0)
+ rexml (3.2.6)
+ rouge (4.1.3)
+ rubyzip (2.3.2)
+ safe_yaml (1.0.5)
+ sass-embedded (1.64.1)
+ google-protobuf (~> 3.23)
+ rake (>= 13.0.0)
+ terminal-table (3.0.2)
+ unicode-display_width (>= 1.1.1, < 3)
+ unicode-display_width (2.4.2)
+ webrick (1.8.1)
+
+PLATFORMS
+ ruby
+ x86_64-darwin-19
+ x86_64-linux
+
+DEPENDENCIES
+ jekyll (~> 4.3.2)
+ rubyzip (~> 2.3)
+
+BUNDLED WITH
+ 2.2.4
diff --git a/_config.yml b/_config.yml
index 66bc3757..709dc9ff 100644
--- a/_config.yml
+++ b/_config.yml
@@ -1,9 +1,20 @@
analytics: "G-VCVX2DGPPN"
-domain: "www.calitp.org"
-description: "A state government initiative, Cal-ITP is making riding by rail and bus simpler and more cost-effective—for California transit providers and riders."
-google_fonts: "https://fonts.googleapis.com/css2?family=Poppins:wght@500;700&family=Raleway:wght@900&display=swap"
+collections:
+ press:
+ output: true
+ permalink: /:collection/:name
+ resources:
+ output: false
+defaults:
+ - scope:
+ path: ""
+ type: press
+ values:
+ layout: press
+description: A state government initiative, Cal-ITP is making riding by rail and bus simpler and more cost-effective—for California transit providers and riders.
+domain: www.calitp.org
+google_fonts: "https://fonts.googleapis.com/css2?family=Poppins:wght@400;700&family=Raleway:wght@700&display=swap"
source: ./src
-theme_background_color: "#b82d28"
-theme_color: "#b82d28"
+timezone: America/Los_Angeles
title: "Cal-ITP: California Integrated Travel Project"
url: "https://www.calitp.org"
diff --git a/src/404.html b/src/404.html
index 9b8876b2..deffabbe 100644
--- a/src/404.html
+++ b/src/404.html
@@ -7,7 +7,8 @@
Sorry, but the page you were trying to view does not exist.
+ Go back Home.Page Not Found
+
+ {% if item.outlet %}
+ {{ item.outlet }} |{% endif %}
+ {{ item.tags | join: ", " }} |
+ {% include date.html date=item.date format = "%b %Y" %}
+
+ {{ paragraph }} +
+ {% endfor %} + +{{ page.lead }}
+ {% endif %} +For immediate release
+{{ date | append: location | append: "—" | append: page.intro }}
+ {{ page.content }} +
- Learn how the California Integrated Travel Project (Cal-ITP) is making riding by rail and bus simpler and more
- cost-effective—for providers and riders.
+
+ Learn how the California Integrated Travel Project (Cal-ITP) is making riding by bus and train simpler and more
+ cost-effective—for providers and customers.
- Adding a contactless payment reader to a bus or train means customers can quickly and easily tap to pay as they board
- with the bank card or smartphone that’s already in their pocket—just like they’d tap to buy a coffee.
-
- Starting with
- Monterey-Salinas Transit, Cal-ITP and partners like Visa are demonstrating how a transit provider that has traditionally used cash and
- agency-specific fare cards can accept contactless bank card payments like any other merchant.
-
- And to make it easier and more affordable for public transportation providers anywhere in the U.S. to acquire the
- building blocks of contactless payments, the California Department of General Services (DGS)—in collaboration with
- Cal-ITP—conducted a Request for Proposal that established Master Service Agreements (MSAs) allowing public
- transportation providers to purchase contactless payments hardware and software directly from vendors without further
- competitive bidding. Learn about the MSAs in our
- press release, and
- view the MSAs.
-
- Our Cal-ITP Benefits web application
- streamlines the process for transit riders to instantly qualify for and receive discounts, starting with
- Monterey-Salinas Transit
- (MST), which offers a half-price Senior Fare. Now older adults (65+) who are able to
- electronically verify their identity
- are able to access MST's reduced fares without the hassle of paperwork.
-
- We worked with state partners on this product launch, and next we're working to bring youth, lower-income riders,
- veterans, people with disabilities, and others the same instant access to free or reduced fares across all California
- transit providers, without having to prove eligibility to each agency.
-
- Cal-ITP is helping transit providers remove the guesswork for riders wondering when the next bus or train will arrive
- or if they’ll make their connection by using the General Transit Feed Specification (GTFS)—the global standard for
- publishing transit information. Cal-ITP developed
- California Minimum GTFS Guidelines
- and is working to ensure statewide GTFS static coverage by the end of 2020 and GTFS Realtime by the end of 2021. Along
- the way, the Cal-ITP team will support transit providers by assessing their systems and providing technical assistance
- so riders can easily access complete, accurate, consistent, and timely mobility data for their journey.
-
- There are hundreds of public transit providers in California—with no single system for collecting fares, verifying
- eligibility for fare discounts, or providing up-to-date vehicle arrival information to riders.
-
- This lack of uniformity creates barriers for new riders, complicates travel across different systems, and increases expenses
- for individual providers.
-
- Supported by the
- California State Transportation Agency
- (CalSTA) and the
- California Department of Transportation
- (Caltrans) through a grant from the
- California Transit and Intercity Rail Capital Program
- (TIRCP), the California Integrated Travel Project (Cal-ITP) is a statewide solution to make travel simpler and
- cost-effective for everyone.
- Since forming in 2018, some Cal-ITP milestones include:
- In August 2019, CalSTA and Caltrans organized a market sounding kickoff with companies and organizations in the payments,
- banking, and trip-planning industries. In that meeting, barriers to seamless trip planning and fare payment were identified,
- such as the lack of uniformity among California’s transit providers. Cal-ITP’s
- 1st Market Sounding
- in October 2019 dug into these barriers and identified specific opportunities for Cal-ITP to assist California’s transit
- providers by leveraging global standards for data and payment systems.
-
- Following the market sounding, Cal-ITP conducted a more thorough analysis to assess the financial and economic impacts of
- the recommended initiatives. The April 2020
- Cal-ITP Feasibility Study
- details the state of public transit in California and quantifies the economic benefits of Cal-ITP’s three primary
- initiatives under conservative to moderate assumptions of project costs and ridership effects based on estimated demand.
-
- To increase the quality and quantity of transit data published by California's transit providers, Cal-ITP and state and
- regional partners explored passenger-counting technologies in July 2020. Passenger occupancy data is crucial for
- transportation planning purposes, and physical distancing due to COVID-19 has highlighted the benefit for riders to know
- real-time passenger crowding in trip planning. Cal-ITP’s
- 2nd Market Sounding: Real-Time Transit Vehicle Occupancy Report
- was published in October 2020.
+ There are hundreds of public transit providers in California—with no consistent way to collect fares, verify eligibility for
+ fare discounts, or provide real-time vehicle information to customers on their phones.
- In 2020, Cal-ITP and partners gathered input from marketplace companies to gauge capabilities and interest in supporting
- payment issuance. The findings were documented in Cal-ITP’s
- 3rd Market Sounding Report: Payment Issuance for California Transit
- and led to Cal-ITP collaborating with the California Air Resources Board (CARB) in 2021 to understand the market for
- mobility accounts. Highlights from interviews with companies, transit agencies, and nonprofit and academic stakeholders can
- be found in the
- Market Sounding Report: Mobility Accounts.
+ The lack of a consistent experience creates barriers for new customers, complicates travel across different systems, and
+ increases expenses for individual providers.
- Throughout 2021, Cal-ITP forged new partnerships and live-tested solutions, advancing our vision across our three primary
- project areas. Check out our
+ Supported by the
2021 Accomplishments Report
- for complete details on our contactless payment demonstration projects and other ways in which our teams tackled mobility
- service data, payment acceptance, and eligibility for discounts and benefits.
-
- In March 2022, Cal-ITP announced its
+ class="red-link fw-bold"
+ href="https://calsta.ca.gov/">California State Transportation Agency
+ (CalSTA) and the
Market Consultation: Benefits Administrator, inviting companies to contribute answers to a set of five questions that could shape the way that California residents
- qualify for and receive benefits, starting with transit discounts.
-
- In June 2022, Cal-ITP announced a
+ class="green-link fw-bold"
+ href="https://dot.ca.gov/ ">California Department of Transportation
+ (Caltrans) through a grant from the
new open data standard
- to improve transit agency operations and promote an interoperable transit ecosystem by improving the flow of data and
- information sharing. The Operational Data Standard (ODS) leverages the existing GTFS standard used by transit agencies and
- riders all over the world for transit service information and extends it to include data about personnel, scheduled
- maintenance, and non-revenue service. The ODS specification is a product of the Operational Data Standard Working Group, a
- coalition of more than 40 transit agencies, transit technology vendors such as computer-aided dispatch/automatic vehicle
- location (CAD/AVL) companies, transit scheduling companies, and other contributors.
-
- Cal-ITP initiatives are grounded in real-world results. Here’s a sampling of what we plan to do, supported by success
- stories from transit providers around the world.
+ class="blue-link fw-bold"
+ href="https://calsta.ca.gov/subject-areas/transit-intercity-rail-capital-prog">California Transit and Intercity Rail Capital Program
+ (TIRCP), the California Integrated Travel Project (Cal-ITP) is a statewide solution to make travel simpler and
+ cost-effective for everyone.
- Real-time global data standards save time—and change perceptions of wait time. In Seattle, riders with
- access to GTFS Realtime information perceived their transit wait times as
- 30% shorter than those without GTFS Realtime. Actual wait times were reduced by 2 minutes.
-
- Contactless fare payments make transit easier for riders—especially tourists. Since beginning to accept
- contactless payments in 2019, New York City has seen
- taps from 130 countries
- and eliminated the trip delay for currency conversion or to buy a fare card.
-
- Contactless payments are popular with riders and boost satisfaction. In London,
- 2/3 of riders converted to contactless payments after just their first use. And in a recent survey of UK commuters,
- 45% of respondents said they would feel more positive toward public transit if they could use contactless payments.
-
- Contactless payments are an incentive for riders to return to transit after the COVID-19 pandemic.
- According to Visa,
- contactless transactions for transit increased by 187% from April to June 2020.
-
- Convenient, universal fare payments grow ridership. Riders are more likely to use transit when they
- don’t need to think about how they’ll pay their fare. In its first year accepting contactless payments,
- London saw a 4%–5% growth in Underground ridership.
-
- Real-time arrival information shows that transit is a reliable way to commute and travel. The
- introduction of
- real-time arrival information increased bus ridership by about 2% in New York and Chicago.
-
- Cash alternatives will cut costs for transit providers. Washington, D.C., spends 10¢ per dollar
- collecting cash fares but
- just 4¢ per dollar on credit/debit card fares.
-
- Digital payments are less expensive to accept. According to Visa, the average merchant spends about 7¢
- per dollar on processing cash and checks versus
- 5¢ per dollar for contactless payments.
-
- Machine maintenance and ticketing fees decrease. In New York City, the MTA expects to
- save millions of dollars by eliminating the costs required for upkeep of its MetroCard system.
-
- Contactless payments decrease bus dwell times.
- Buses make up 62% of California’s urban public transit trips. The Transportation Research Board found that
- bus boarding times are almost cut in half when tapping
- (2.75 seconds per passenger) compared to swiping (5.0 seconds per passenger) or paying cash (4.5 seconds per passenger).
-
- Making transit more attractive to riders will reduce driving demand.
- California’s transit mode share
- (5.2%) is comparable to the
- national average
- (5.0%). However, given our state’s density, diversity, congestion, and size, travel by bus and rail can and should be
- higher in California. Contactless fare payments and real-time arrival information lead to higher transit ridership,
- mitigating congestion and reducing greenhouse gas emissions.
-
- A statewide program to verify eligibility for reduced fares will alleviate cumbersome processes for both transit
- providers and riders.
- A simple, digitized, statewide verification program will enable any rider to have their eligibility for a reduced-fare
- program instantly verified for any transit provider in California. This way, older adults, students, veterans, and
- others can ride transit anywhere in the state with the confidence that they’ll be charged the right fare every time.
-
- Fare capping reduces transit costs for low-income riders. Unlimited-ride passes cost more upfront,
- forcing many riders to pay as they go at full fare. Contactless fare collection enables “fare capping,” which allows
- riders to pay the unlimited-ride price over time. This means that, after tapping enough times to reach the cost of a
- daily, weekly, or monthly pass, riders will no longer be charged for transit use for the remainder of that time period.
- By aligning transportation payment infrastructure with a 21st-century retail experience, Cal-ITP achieves four goals: This initiative is critical now more than ever.
- As COVID-19 hit the United States, many transit providers saw ridership decrease. But many who depend on transit do not have
- the privilege to work from home—including many essential workers. Reliable transit access and contactless payments are
- critical components to ensuring that transit forms a key part of the COVID-19 crisis response and recovery.
-
- Cal-ITP also supports the state’s longer-term equity, economic development, and climate goals as delineated in
- 2020 California Executive Order N-79-20. Increased transit ridership is a key component of California’s strategy to reduce greenhouse gas emissions and combat
- climate change. To reach its full potential, Cal-ITP will provide individual transit providers with the buying power to save
- on the equipment needed to ensure that transit remains a core tenet of the state’s mobility.
-
- As California faces these unprecedented challenges, there is a sense of urgency around creating a seamless, simpler, and
- more sustainable transit experience in California. Collaboration and collective problem-solving are needed at all levels of
- government, public and private transit providers, academia, and think tanks, as well as vendors of relevant technologies and
- business models. Join us.
+ Cal-ITP is working with transportation agencies across the country to launch a program that can immediately improve the
+ ridership experience. Contact us to learn more.
Drop us a line at hello@calitp.org to
- See our latest milestones, and subscribe to
- the
- Caltrans Mobility Newsletter, a free biweekly resource with frequent Cal-ITP project updates.
-
+ See our
+ latest milestones, and subscribe to the
+ Caltrans Mobility Newsletter, a free biweekly resource with frequent Cal-ITP project updates.
+ A modern and consistent transportation experience throughout California
+
+ alt="A trio of images, clockwise from top: a bus, a train platform with a sign that announces “Next train in 3 minutes,” and a transit rider paying their fare by tapping their smartphone’s mobile wallet on a payment reader when boarding" />
-
Enabling contactless payments
-
-
Automating customer discounts
-
-
Standardizing information for easy trip planning
- Bringing industry standards to California’s transit providers
- Identifying solutions
- Understanding feasibility
- Getting to work
+
+
+
Bringing industry standards to California’s transit providers
-
Helping California achieve critical goals through transportation
- Improve the customer experience
- Increase transit ridership
- Lower costs for transit providers and riders
- Reduce greenhouse gas emissions to reach environmental targets
- Promote equitable access to transportation across the state’s transit providers
-
-
The time is now—reach out to help and to learn more
+ Helping California achieve critical goals through transportation
+
+
+
+
+
+
+
The time is now—reach out to help and to learn more
Connect with Cal-ITP
-
-
- Stay up to date
- Connect with Cal-ITP
+ Drop us a line at
+ hello@calitp.org
+ to:
+
+
+ Stay up to date
+
Below you’ll find news about Cal-ITP and our initiatives, including press releases and media coverage about new launches and project milestones. Interested in getting in touch? Reach out to us at hello@calitp.org.
+ {% include pills.html tags=site.data.press_tags %} +Below you’ll find information about Cal-ITP and our initiatives, including fact sheets, case studies, and more. Don’t see what you’re looking for? Reach out to us at + hello@calitp.org.
+ {% include pills.html tags=site.data.resource_tags %} +