HOW TO: work on ServiceMap for developers

The ServiceMap is accessible for each Organization and the map is centred in the GPS center position of the Organization.

The Servicemap (alias Knowledge Base) can be used to:

• Recover the ServiceURI
• Request the serve API query to be used in the Dashboard Builder More Options of  the widgets, especially for the Selectors
• Pose queries and to request at the system a Query ID to be used in the Dashboard Builder More Options of  the widgets, especially for the Selectors
• Test eventual shapes loaded as WKT and created according to the WTK editor

Recover a ServiceURI for using on Node-RED, and Dashboard Builder

Please note that the PIN and the data accessible on Servicemap are Public. If you are locking for data which are private you have to use Data Inspector, or Dashboards.

The ServiceURI can be recovered from the pop up of any PIN on map which are present on the ServiceMap once performed a query. The ServiceURI has the following form.

http://www.disit.org/km4city/resource/ARPAT_QA_FI-BOBOLI

The  ServiceURI is a link that bring you the RDF definition of the City Entity.

Every time the user performs some query on ServiceMap, the panel on which the query is performed present a small disk and once clicked the system is sending you an email with example of Smart City API Calls

• REST CALL by category à JSON (Options in RED), they are REST ASCAPI calls
  • Requesting a category, so that to see all Services of the same category (subNature)
    • http://svealand.snap4city.org/ServiceMap/api/v1/?selection=59.581458578537955;16.71183586120606;59.62875017053684;16.875171661376957&categories=Street_light&maxResults=100&format=json
    • https://servicemap.disit.org/WebAppGrafo/api/v1/?selection=43.64471;11.005751;43.89471;11.505751&categories=Green_areas&maxResults=200&format=json
    • Custom PINS note: “selection” coordinates are used for collecting attributes in custom PINS. Other options such as “maxDists” cannot be used in custom PIN. All parameters can be used in other cases.
    • Different KB links are identified by their ASCAPI links: svealand.snap4city.org, servicemap.disit.org, ….
  • Requests to SuperServiceMap for the network of Federated KBs by using /api/………..
    Without prefixed KB to obtain merged results from more KBs. For example as:
    • /api/v1/?categories=Air_quality_monitoring_station&format=json
  • Requests from GIS servers by using WFS API and services
    • https://os.cittametropolitana.fi.it/imobi-ds/trafficsensors/1758EB9B47A3904E05673BFEEE61AB1776C4C0050E7BD7FB195EA33CC56767BE/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=TrafficSensors
• REST CALL by ServiceURI à JSON (ServiceURI in RED), they are ASCAPI calls
  • Requesting single Service
    • https://servicemap.disit.org/WebAppGrafo/api/v1/?serviceUri=http://www.disit.org/km4city/resource/ARPAT_QA_FI-BOBOLI&for...
    • https://servicemap.disit.org/WebAppGrafo/api/v1/?serviceUri=http://www.disit.org/km4city/resource/ARPAT_QA_FI-MOSSE_SV&format=json
    • Different KBs links are identified by their ASCAPI links: svealand.snap4city.org, servicemap.disit.org, ….
  • Referring to SuperServiceMap into the network of Federated KBs is possible by using /api/……….. Without prefixed KB, to obtain merged data from more KBs, for example as:
    • /api/v1/?categories=Air_quality_monitoring_station&format=json
• ServiceMap (specific KB) and Query service
  • The Query performed is saved and can be recalled with a QueryID, valid for that specific KB, and not accessible via SuperServiceMap / Federated KB
  • The QueryID is communicated via email
  • Specific REST Call with HTML is also provided to change the Query in server associated with the QueryID received
  • Query ID (only Read and Read/Write of the query)
  • https://servicemap.disit.org/WebAppGrafo/api/v1/?queryId=1c8111893d40a2bb07a2078ffe299ced&format=json
  • Cannot be used for Custom PINs.
  • Cannot be used to get data via ServiceMap since the Query ID is KB based
• Commands for Special Tool:
  • Traffic Flow tool: https://firenzetraffic.km4city.org/trafficRTDetails/roads/read.php
  • Scenario tool: /scenario/
  • Whatif tool: /whatif/
• Heatmaps, see Data Analytic part of the training for the several versions which can be used:
  • https://wmsserver.snap4city.org/geoserver/Snap4City/wms?service=WMS&layers=PM2_5Average24HourFlorence
  • https://wmsserver.snap4city.org/geoserver/Snap4City/wms?service=WMS&layers=denseNO2_Firenze_IDW
  • WMSServer that is a GeoServer may be different for different installations of Snap4City

Posing queries on Servicemap on the basis of Shapes

In the above image, the query on ServiceMap has been performed referring to a specific Area, and the  area has been that of Quartiere_Q1 for Florence. The Area has been loaded into the system as WKT shape created as follows. The query is requesting for entertainment POI in the whole specific are identified.

Loading a WKT

In the ServiceMap it is possible to load a polyline for further use. This is possible thanks to the tools:

• Manually created:  https://arthur-e.github.io/Wicket/sandbox-gmaps3.html
• loaded via: https://www.km4city.org/wkt/
• see for examples also http://antwerp.km4city.org/wkt/ http://helsinki.km4city.org/wkt/

Once the PolyLine (open or closed) is created with WICKET it can be loaded on the Servicemap using the above links.