Python package for:
fetching raw historical traffic data from Finnish Transport Infrastructure Agency,
aggregating said data,
building directional graph between provinces/ervas and mapping the edges to the appropriate sections of the aggregated traffic data, and
visualizing the aggregated data.
Installation
pip3 install fin-traffic-data
Fetching raw traffic data
The console script fin-traffic-fetch-raw-data allows you to fetch the raw traffic data of all traffic measuring stations between two dates. Usage:
fin-traffic-fetch-raw-data --begin-date 2020-01-01 --end-date 2020-02-01
The dates are formatted as YYYY-MM-DD. The script spits out HDF5 files storing pandas dataframes with the filenaming convention fin_traffic_raw_<begin-date>_<end_date>.h5.
The output file contains the raw traffic data for each TMS in a dataset called tms_<tms id>.
Aggregating raw data
The console script fin-traffic-aggregate-raw-data allows you the aggregate pre-fetched traffic data. Usage:
fin-traffic-aggregate-raw-data --dir raw_data/ --time-resolution 1h
Here the options are
- –dir
Directory from which to load the datafiles for raw traffic data
- –time-resolution
Time-resolution of the aggregation. Use the literals w for weeks, d for days, and h for hours.
The script spits out a file named fin_traffic_aggregated_<begin-date>_<end-date>_<time-resolution>.h5.
Computing traffic between provinces and university hospital catchment areas
The console script fin-traffic-compute-traffic-between-areas can be used to compute traffic between different regions. For computing traffic between provinces, use the command:
fin-traffic-compute-traffic-between-areas --area province --input aggregated_data/fi_traffic_aggregated-2020-01-01 00:00:00-2020-09-16 00:00:00-1:00:00.h5
For traffic between university hospital catchment areas, use the flag –area erva. This tool spits out a file named tms_between_ervas.h5 or tms_between_provinces.h5.
Converting province/ERVA level traffic to CSV format
For converting province/ERVA level traffic to a compressed archive of CSV-files, use the command:
fin-traffic-export-traffic-between-areas-to-csv --area erva
This requires the file tms_between_ervas.h5 and outputs the archive tms_between_ervas.tar.bz2.
Metadata
Release files for fin-traffic-data 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fin_traffic_data-0.0.5.tar.gz | 13.1 kB | Without provenance | Details for fin_traffic_data-0.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fin_traffic_data-0.0.5-py3-none-any.whl | Python 3 | none | any | Details for fin_traffic_data-0.0.5-py3-none-any.whl |
Total release size: 42.1 kB
Release files / fin_traffic_data-0.0.5.tar.gz
| Download URL | fin_traffic_data-0.0.5.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
513aebb69c172cc2ab3bb5dba5742d00221a59374875dc9ae2d140306fbd6cc9
|
|
BLAKE2b-256 checksum How to use checksums |
e9604ab7b1bbaa3a372667f145534e12c57f306b602fd710596848a888dad6f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.8.6
|
Release files / fin_traffic_data-0.0.5-py3-none-any.whl
| Download URL | fin_traffic_data-0.0.5-py3-none-any.whl |
|---|---|
| Size | 28.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4612ee7509b078ac18b872fbfc4343117c4fc778d22cb96a30de780ea124e5c0
|
|
BLAKE2b-256 checksum How to use checksums |
1b214be06730819c6144b65810e4fef0bb97ee0544424d681a213ace04bf2176
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.8.6
|
Security for fin-traffic-data 0.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.