Monitor the current traffic load with minute-by-minute response data.

Client needs

The motivation for the production of this project was the display of fleet data in a map view and technological, graphical and UI/UX obsolescence.

The previous solution was divided into two parts - Portal, which is the part with general information, news feed, camera previews, etc. - And the map part, where the main functionality of the application is, which is a map screen showing various phenomena on the road network in the Czech Republic - accidents, closures, excessive costs and information from telematics systems (information boards on motorways, weather stations, etc.).

Our new application is (in addition to static phenomena such as accidents, etc.) able to display FCD data (data from the fleet of vehicles) provided by another supplier and we put it into context for the user - we display the so-called earthworms or linear phenomena that represent the flow of traffic on all roads where fleet vehicles drive. FCD data was the grist of this project.

Part of the work with FCD data was also the so-called segmentation of the road network of the Czech Republic - the whole Czech Republic is divided into segments (=parts) from a geographical/logical point of view and we are able to show them in great detail - e.g. segment Kralovehradecky region, District Pardubice, D1, D11, Agglomeration of Prague. In addition to being able to show FDC data (traffic flow and density) on individual roads, we can also provide statistical data on the whole segment - in the case of D1, for example, we can show data on the number of fleet vehicle passes, expected delays between end points, average speed and length of queues. We can also display data 24 hours in advance.

Of course there are options to search for a route and a specific address point in the Czech Republic.

Our solution

The project included an implementation study, graphic design and development of the application itself.

The map can be filtered using the square icon buttons. It is therefore possible to choose what you want to see.



For a project of this importance, it was essential that everything was well prepared before the implementation phase and therefore many consultations with the client and data provider took place in the preparation phase.

A separate and complex issue was the incorporation of our solution into the client's technological infrastructure so that nothing impeded the data flow and at the same time the application security requirements were met.


Traffic info always at hand.

We launched the first beta version of the application after a year of development and the application ran in this mode for another year with constant addition of functionalities. The next step in this project will be the release of a new mobile app that is written using React Native technology and will be much more agile and modern than the existing app.

Final result

The application on our side has two layers - Frontend and backend connected by API. Which is a pretty standard structure, but for which we have technologically made a step forward compared to the replaced solution.


Static pages of informational nature are then served by the second part of the backend written in PHP, where we created a simple CMS for content management. The big challenge was to combine the existing data sources from the data supplier, our backend and for example the user infrastructure, which was separate, with close communication along the client-us-data supplier axis to create a data source tailored to the new application.


For the frontend we use the React framework, which is a javascript platform developed by Facebook that allows us to create highly responsive applications. For the API we use GraphQL technology, which allows to specify in queries only what is needed on the client side and nothing more, which gives a lot of freedom to developers in working with data and it saves data flow.

Final implementation

The server logic and data handling were handled in NodeJS, which is a javascript framework for backend use. The static informational pages are then served by a second part of the backend written in PHP, where we provided a simple CMS for content management.

Project in numbers

Number of visits per day
Point phenomena in the map
Data update period