How to show an object from a Wirecloud MapViewer widget

Question

Well, I'm trying to show the following entity:

{ "contextResponses" : [ { "contextElement" : { "type" : "City", "isPattern" : "false", "id" : "Miraflores", "attributes" : [ { "name" : "position", "type" : "coords", "value" : "-12.119816, -77.028916", "metadatas" : [ { "name" : "location", "type" : "string", "value" : "WSG84" } ] } ] }, "statusCode" : { "code" : "200", "reasonPhrase" : "OK" } } ] } 

Connecting an NGSI and NGSI Entity source to a Poi operator using the MapViewer widget (Insert / Update PoI) with the following settings:

NGSI Source

• NGS server url: mydirection: 1026
• NGSI Proxy URL: http://mashup.lab.fi-ware.org//000/
• NGSI Objects: City
• NGSI Attributes:.

NGSI Object for Poi

• Attribute Coordinates: Position

But nothing is displayed on the map! Can someone help me figure out what the problem is?

Answer 1

It seems that your configuration is correct (I assume mydirection: 1026 is the full URL, that is, it includes the protocol), but your network is probably filtering port 3000. Try using http://ngsiproxy.lab.fi-ware.org as NGSI proxy server instead of http://mashup.lab.fi-ware.org:3000/ {000/.

In fact, I recommend that you enable https notifications in your instance of the context instance and use https ://ngsiproxy.lab.fi-ware.org , especially if you create your WireCloud toolbar on an https network (for example, https: //mashup.lab.fi-ware.org ), since using this NGS proxy server will solve some problems with mixed content:

• Chrome: https://support.google.com/chrome/answer/1342714?hl=en
• Firefox: https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/

Update : FIWARE will move from fiskware to fiware.org. The recommended NGSI proxy is now ngsiproxy.lab.fiware.org ( ngsiproxy.lab.fi-ware.org is still working).

Answer 2

Three easy steps to run MapViewer on Fiware:

• Update ConionBroker Orion on your system

• You must verify that the daemon and rdis are installed and running on your system.

• You must create the correct boot sequence in init.d: ​​redis, rush and contextBroker

After these steps, you can create your own view interface in Wirecloud using MapViewer, an NGSI source, and an NGSI object for POI.

You must correctly use structured JSON messages, as in the following example:

 { "contextElements": [ { "type": "iotdevice","isPattern": "false","id": "edison1", "attributes": [ { "name": "temperature", "type": "string", "value": "10" }, { "name" : "position", "type" : "coords", "value" : "-20, 35", "metadatas" : [ { "name" : "location", "type" : "string", "value" : "WSG84" } ] } ] } ], "updateAction": "APPEND" }