
This dataset contains traffic data collected on 17, 24, and 31 January 2026 in the Fuorigrotta area of Naples, Italy. The data were gathered using HERE Technologies' Traffic API v7 using the Python tool found in the linked repository and focus on two main anomalous scenarios: Soccer match on 17 and 31 January, both starting at 18:00 Yellow weather warning on 24 January The database used is PostgreSQL 17.5 with the PostGIS extension, needed to support the geospatial data types included in the dataset. The dump was generated using PostgreSQL's pg_dump utility. It is possible to restore this dump into a new PostgreSQL + PostGIS database using psql: psql -U -d -f The database structure is as follows: data: Acts as the primary entry point for a data update. Contains metadata like source_updated (timestamp in UTC) and tag (a string with a common piece of text for related data). Links to both the physical locations and the traffic flow metrics via entry_id. locations & links: locations: Defines a specific area or stretch of road with a description and total length. links: Provides the spatial geometry for a location. It uses a geography(linestring, 4326) type to store the actual GPS coordinates and paths of the road segments. current_flows: This is the central hub for traffic status. It tracks real-time variables such as speed, free_flow speed, jam_factor (congestion level), and confidence (data reliability). It also includes qualitative data like traversability and junction_traversability. lanes & sub_segments: Both tables link back to a specific current_flow entry to provide deeper detail. lanes: Breaks down flow data by specific lane numbers and types. sub_segments: Allows for even more precise tracking by dividing a main link into smaller pieces, each with its own speed and jam factor metrics. The lanes and sub_segments tables are empty since those information are not available in HERE Technologies' free plan.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
