This workflow implements an alarm system for bicycle restocking at Washington bike stations. Capital Bikeshare offers a download of their bike usage data dating as far back as 2010. They also offer a live REST-API. In this workflow, we use data from 2018 and 2019 as training data and evaluate the learned model on the data of the first three months of 2020.
The task is to predict one of three classes, that is whether a bike station needs: to remove bikes, to add bikes, or no action. Predicting 3 classes is easier than predicting a precise number and classification methods can be used. We only use the data that was provided by capital bikeshare (with some assumptions on the initial status of the stations at the end of 2017). The primary purpose of this workflow is to show how KNIME and Cumulocity can be used in concert. We therefore do not put much effort in the optimization of the machine learning model and also to not use any external data. A natural extension of this workflow would be for example to join weather data to the device data in order to improve the prediction quality.
Get this workflow from the following link: Download
2018-2020_Bike_Restocking_c8y_v4.1 consists of the following 105 nodes(s):
2018-2020_Bike_Restocking_c8y_v4.1 contains nodes provided by the following 8 plugin(s):
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to firstname.lastname@example.org, follow @NodePit on Twitter, or chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.