As cities deploy more transportation technologies, the ability to bring data from different systems together becomes increasingly important.

The City of Dublin, Ohio explored that challenge through its Transportation Data Dashboard project. Dublin's Accenture/Anser consulting team evaluated how data and dashboards from multiple transportation technology providers could be incorporated into a unified City data environment.

Fybr was the only third-party commercial technology provider documented in the final report as successfully supporting both dashboard embedding and API data integration.

Fybr's existing analytics dashboards were successfully embedded within Dublin's Transportation Data Portal. The project also integrated Fybr's underlying parking data through its API, giving the City the flexibility to use that information in its own dashboards and applications.

As part of the project, the Fybr data pipeline was independently validated by comparing data obtained through the API with information displayed in Fybr's dashboards.

For Dublin, that integrated data begins at the individual parking space. Fybr provides real-time occupancy and parking-session information that can help the City understand short-term parking activity, identify potential parking violations and make parking information available across its broader transportation-data environment.

View the independent report → Dublin, OH Transportation Data Dashboard Report

Dublin at a Glance

Customer: City of Dublin, Ohio

Location: Historic Dublin

Fybr technology: Individual parking space, loading zone, and no parking area occupancy sensors, live availability mobile application (FybrPark), directed enforcement mobile application (FybrEnforce), analytics (FybrInsights) and API data integration

Deployment: On-street parking, loading zone, and no parking areas (including center-left turn lanes) along North High Street and North Street

Data collected: Real-time occupancy and parking-session information

Applications: Parking utilization, session-duration analysis, real-time availability and navigation, violation identification, analytics, and transportation-data integration

Integration: Embedded Fybr dashboards and API data integration

Independent evaluation: City of Dublin Transportation Data Dashboard project / Accenture-Anser consulting team

Vehicle identification required for occupancy: No

From Parking Activity to Actionable Data

Fybr sensors give Dublin a real-time view of how individual parking spaces, loading areas and no parking areas (including center-left turn lanes) are being used.

The system records when a space becomes occupied, when it becomes available and how long an occupancy session lasts. That allows Dublin to understand utilization and turnover while also identifying timed-parking violations and activity in monitored areas.

The City's Transportation Data Dashboard Report describes Fybr data as providing real-time occupancy and parking-session information that can be analyzed by individual space and over time.

But Dublin's project went a step further: the City wanted that information to work within a larger transportation-data environment.

Two Paths to Integration

As part of Dublin's Transportation Data Dashboard project, the Accenture/Anser consulting team evaluated two ways of bringing information from transportation technology providers into the City's broader platform.

Embedded Applications

Could an existing vendor dashboard be incorporated directly into Dublin's Transportation Data Portal?

Fybr's existing analytics dashboards were successfully embedded, giving Dublin access to parking sessions, duration and violation information within its broader transportation environment.

API Data Integration

Could the underlying data be accessed through an API and incorporated into City-developed dashboards and applications?

Fybr's parking data was also successfully integrated through its API.

Among the third-party commercial technology providers documented in the final report, Fybr was the only provider that successfully supported both approaches.

An API That Was Integrated and Validated

The Dublin project did more than confirm that an API was available.

Accenture/Anser used Fybr's API to bring parking data into Dublin's environment and then validated the resulting data pipeline by comparing API-derived information with the data displayed in Fybr's own dashboards.

That gives Dublin flexibility in how it uses its parking information. The City can use Fybr's existing applications where appropriate or incorporate the underlying data into its own dashboards, analytics and future transportation applications.

For cities investing in multiple transportation technologies, that flexibility matters. Parking data does not have to remain isolated within the parking platform that collected it.

Independent Evidence

Dublin's Transportation Data Dashboard Report documents Fybr's individual-space occupancy and parking-session data, violation information, successful dashboard embedding, API integration and validation of the resulting data pipeline.

View the independent report → Dublin, OH Transportation Data Dashboard Report

Frequently Asked Questions

Can Fybr parking data integrate with other municipal systems?

Yes. Dublin's project demonstrated two approaches: embedding Fybr's existing applications within another platform and accessing the underlying parking data through Fybr's API.

Was Fybr's API actually tested?

Yes. Fybr data was integrated through its API, and Accenture/Anser validated the resulting data pipeline by comparing API-derived information with data displayed in Fybr's dashboards.

Does Dublin have to use Fybr's dashboard to use Fybr data?

No. Dublin demonstrated that Fybr's existing dashboards can be embedded within another platform while the underlying parking data can also be accessed through APIs for use in other applications.

What parking information does Fybr provide in Dublin?

Fybr provides real-time occupancy and parking-session information at the individual-space and curb-zone level, including no parking areas and center-left turn lanes. That information can be used to understand utilization and duration and identify potential parking violations.

Open Parking Data Creates More Possibilities

Dublin demonstrates the value of parking data that can move beyond the system that collects it. Fybr gives the City real-time insight into individual parking spaces, loading areas, no parking areas, and potential violations, while open integration allows that information to become part of a broader transportation-data environment. The result is parking technology that can solve today's operational needs without limiting how a city may want to use its data tomorrow.