This module and command line tool provides access to the CityIQ API, with particular focus on getting metadata and parking events. The interface includes a basic access object for getting metadata and events, a scraper object for mass downloading events, and a command line tool for downloading and processing events.
Quickstart
Install the module with pip:
pip install cityiq
Then generate a configuration file with:
ciq_config -w
Edit the file with your credentials and other information for your system. The default file is configured for the San Diego system, but you may have to update the client id and password.
You can list the nodes, assets and locations in the system with the ciq_nodes program:
ciq_nodes --locations # display locations a JSON lines
ciq_nodes --cameras # display camera assets as JSON lines
# etc
You can also dump all assets or all locations to CSV files.
ciq_nodes -A assets.csv
ciq_nodes -L locations.csv
Getting events is a two step process, and can be done with either the CLI programs or the Python API. To get events with the CLI, fors download them to the cache. The cache location is defined in the configuration file, and should have at least 100GB of free space.
First, download and cache the events. The download will run for all of the assets that have the given event, over the whole time range. On the San Diego system, time ranges longer than a few months can take days to download.
ciq_events -e BICYCLE -s 2020-01-01 -f 2020-02-01
The downloaded data is stored in the cache as CSV files, which you can load directly in which pandas or dask, or convert to one CSV file per asset:
ciq_events -e BICYCLE -s 2020-01-01 -f 2020-02-01
Devlopment
Committing
The project scaffold gets the version number for the module from git. To get the version number:
$ python setup.py --version
Set the version with a tag. The version numbers are specified with PEP440
$ git tag 0.0.1
Remember to push tags to the remote with git push --tags
Publishing
Publish the project to to PyPI with twine:
pip install twine twine upload dist/*
Scaffolding
This project has been set up using PyScaffold 3.1. For details and usage information on PyScaffold see https://pyscaffold.org/.
Metadata
Release files for cityiq 0.1.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 |
|---|---|---|---|---|
| cityiq-0.1.5.tar.gz | 1.9 MB | Without provenance | Details for cityiq-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cityiq-0.1.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for cityiq-0.1.5-py2.py3-none-any.whl |
Total release size: 1.9 MB
Release files / cityiq-0.1.5.tar.gz
| Download URL | cityiq-0.1.5.tar.gz |
|---|---|
| Size | 1.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3014801bb5e118f91adc485712d8f576ca68621dc6a296505b0414d4adca998b
|
|
BLAKE2b-256 checksum How to use checksums |
05bea1d3147bb96b72a157f7be9d9c6fab914f36452fa18723c9fa81b0eac3c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0.post20191030 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.6.9
|
Release files / cityiq-0.1.5-py2.py3-none-any.whl
| Download URL | cityiq-0.1.5-py2.py3-none-any.whl |
|---|---|
| Size | 30.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7e6aac5beb8c7ebbc02cdf1b0c4cbcdcc780f44b3263b22a056b9dce4dd96671
|
|
BLAKE2b-256 checksum How to use checksums |
488209dec52e8f3d23dde164a239402fb32a4657bcaa5f9ba7deeb69b29ce3aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0.post20191030 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.6.9
|
Security for cityiq 0.1.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.