MicroServices Directory for IOT Applications

• IOTMicroServicesforFinalUsers https://www.km4city.org/iot-micro-doc/user.html
• IOTMicroServicesforDevelopers https://www.km4city.org/iot-micro-doc/index.html

Please note that:

• Each IOT Application editor has a number of MicroService which are for default available on nodeRED as reported in the Annex XXXX
• There are a number of MicroServices specific for Rasberry PI: GPIO, AdaFruit, etc.
• There are a number of MicroServices specific for Android: reading status of the phone, accelerometer, tv camera, and other sensors.
• There is a large community working on NodeRED that produce every day new blocks that may be easily integrated in IOT applications in Snap4City.
  • They are listed on Google and/or on IBM library: https://flows.nodered.org/?num_pages=1
  • They are open source, typically. While some of them connect to services that need a fee to be used.
• interesting nodes that we have used more than others are 
  
  • Nodes for addressing other social media, chatbots
  • Nodes for additional analytics, sqlite, Arduino,
  • Nodes for machine learning, spark ML, mapreduce, etc

Snap4City support bidirectional flows in the end to end process passing from IOT devices to Dashboards, for content and resources, for dashboard and interactions at all level and for all user kinds:

• IOT devices with sensors and actuators
• Dashboards with widgets for
  
  • showing data coming from IOT Applications, Sensors, KPI, KB, and IOT Devices
  • acting on IOT devices, IOT Applications, IOT Brokers
• saving/loading/delegating MyPersonalData, from/to IOT Applications: ValueType, ValueName for example for GPS coordinates, trends, weights, glucose, etc.
• saving/loading/delegating MyAnnotation, from/to IOT Applications, for example for: comments, ranking.
• IOT Application getting data from IOT devices and sending data to actuators
• Notifications with Notificator and IOT Applications, sending notification via multiple channels
• DataGate for upload, download, share data sets
• ETL processes can collect data but also send data on external services and on DataGate
• Resource Manager for upload, download, share of resources such as: dashboards, IOT applications, ETL processes, data analytics processes, IOT Blocks/MicroServices, etc.

• Snap4City allows to present information to city users as described in the previous points, and provides support for collecting information from the city users back to the system, via several channels such as:

• Dashboard presents Actuators that are input widget for sending data, acting to IOT Applications and/or IOT devices/Actuators’;
• IOT devices: sensors can send real time data streams and events into the system, thus activating IOT applications, data analytics, and dashboards;
• IOT Applications can collect data from the users by using specific MicroServices, such as their position, their personal data, etc. This information may be also saved in the GDPR compliant profile;
• Snap4City Smart City API provides specific API for collecting on the back office anonymous images, ranks, comments, notes, etc.;
• Snap4City Portal: in which the users of the different profiles can access to documentation and document and can contribute on Blogs commenting tools and services and  creating a discussion;
• DataGate: in which the users can upload/propose their data set. The acceptance of the tools may depend on ToolAdmin approval. Once approved the data are going to appear on Knowledge Base and thus on MicroApplications, mobile Apps, dashboard, etc.
• Resource Manager: in which the users can upload/propose or download a number of resources such as: dashboards, IOT applications, IOT blocks/Microservice, Data Analytics, ETL Processes, external services, and external Rest Call as MicroService, etc.
• Social Media can also send data into the system since the solution is capable to get social media data by using: Twitter Vigilance, Twitter streams, etc.