{"id":275,"date":"2019-02-16T19:14:47","date_gmt":"2019-02-16T19:14:47","guid":{"rendered":"https:\/\/www.codemotion.com\/magazine\/the-snap4city-api-a-tool-for-smart-city-developers\/"},"modified":"2019-11-14T12:40:52","modified_gmt":"2019-11-14T12:40:52","slug":"the-snap4city-api-a-tool-for-smart-city-developers","status":"publish","type":"post","link":"https:\/\/www.codemotion.com\/magazine\/ai-ml\/big-data\/the-snap4city-api-a-tool-for-smart-city-developers\/","title":{"rendered":"The Snap4City API: a tool for smart city developers"},"content":{"rendered":"

I<\/span>ntegrated platforms and frameworks are the standard solution to the development, test and deployment of applications within complex environments: for example, no one today would program from scratch a neural network while there are plenty of libraries, APIs and frameworks to do that according to different needs, programming paradigms, etc.<\/p>\n

Smart city is one of the biggest arena for development and, as such, requires the mastering of too many assets (both services and infrastructures) to be done \u201cfrom scratch\u201d, or even to be done via a general purpose development framework. On the contrary, it is crucial for the success of smart city projects that suitable tools and very general and comprehensive frameworks are available to let the developers focus on the real target of their application.<\/p>\n

As we know from previous articles (for example the in-depth article on sentient cities<\/a>), Snap4City, an open, standardised, data-driven, service-oriented and user-centric platform aimed at developing IOT\/IOE applications, allows for the creation of general applications via wizards and dashboards, in particular applications may be written or drawn in a graphical language where programming structures are connected both to devices and to dashboards, to be able to perform data analytics, to invoke external services, to execute machine learning algorithms, etc.
\nBut for more specific and sophisticated purposes, Snap4City provides also a powerful set of APIs which can be profitably used to build applications and services of different kinds: the Smart City API.<\/p>\n

\"\"<\/p>\n

Img 1: Smart city API Web documentation page<\/em><\/p>\n

The API is actually structured in several APIs, logically grouped according to the kind of services they offer: thereafter we will deal with some of those APIs which are of paramount interest when developing smart city applications.<\/p>\n

The IOT Device Registration API, which can be used to register IOT devices to the IOT directory, a preliminary step before using them to collect data and interact with devices located in various part of the city.<\/p>\n

 <\/p>\n

\"\"
\nImg 2: Devices directory page<\/em><\/p>\n

The Notificator API, which lets the application which uses it be informed about notifications, as they are defined inside the City Dashboard, a basic tool when using Snap4City.<\/p>\n

\"\"
\nImg 3: Events in the notificator dashboard<\/em><\/p>\n

The DISCES Scheduler API, aimed at monitoring and controlling back office processes of data ingestion and data analytics: DISCES (Distributed Smart City\/Cloud Engine Scheduler), is a scheduler supporting Elastic Management, which allows us to collect the scheduling plans for various processes (e.g. ETL, Data Analytics), to create a plan for the execution of processes over time, to monitor the resources of the cloud (hosts, virtual machines, containers), to turn on\/off hosts and to deploy and shutdown virtual machines and containers.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

Img 4: Back office scheduler DISCES<\/em><\/p>\n

All the previous APIs are also available as IOT microservices block for IOT applications [link to my first document \u201carticle 3\u201d if possible] to be arranged via the wizard GUI within the dashboard.<\/p>\n

Moreover, Smart City APIs provide the Km4City Web App API, which provides services accessible as API REST and which may be viewed as actual \u201cmicro-applications\u201d ready to be used, also directly from the dashboard or from other IOT applications.<\/p>\n

The Resource Manager API can be used to save and search resources managed by the Resource Manager: they can be IOT Applications, ETL processes, Data Analytics Processes, Dashboard, etc. They can also be saved and retrieved from the API so that the other tools can use the Resource Manager API to showcase their instances, to share and promote their work.<\/p>\n

\"\"
\nImg 5: Resource Manager: an actual process loader<\/em><\/p>\n

Also there is a Sensor API, which is designed to let mobile phone and other mobile devices communicate to the back office to signal their status, position and other relevant information. This API is also involved in collecting suggestions, hints, assistance, etc.<\/p>\n

As a part of the Smart City API, Snap4City also provides a mobile development app kit, which is an open source example for developing mobile and web apps using Cordoba Apache.<\/p>\n

Last but not least, it is worth mentioning the Advanced Smart City API, a useful container of APIs exporting various services among which we may list:<\/p>\n