Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-7141

FIWARE.Question.Tech.Apps.ApplicationMashup.can't display the POI from ContextBroker to MapViewer

    Details

      Description

      Created question in FIWARE Q/A platform on 23-08-2016 at 10:08
      Please, ANSWER this question AT https://ask.fiware.org/question/597/cant-display-the-poi-from-contextbroker-to-mapviewer/

      Question:
      can't display the POI from ContextBroker to MapViewer

      Description:
      I'm trying to connect the OrionContextBroker and Wirecloud MapViewer widget in the local environment without the FIWARE Lab.
      I want to display the POI from ContextBroker to MapViewer, but nothing appears in the map.

      The following Entity is entered in the OrionContextBroker:

      curl localhost:1026/v1/contextEntities/City1 -s -S --header 'Accept: application/json' | python -mjson.tool
      {
      "contextElement": {
      "attributes": [

      { "name": "Latitud", "type": "float", "value": "139.692101" }

      ,

      { "name": "Longitud", "type": "float", "value": "35.689634" }

      ],
      "id": "City1",
      "isPattern": "false",
      "type": "City"
      },
      "statusCode": {
      "code": "200",
      "reasonPhrase": "OK"
      }

      }

      The configuration of the NGSISource operator is:

      NGSI server URL : http://localhost:1026/

      NGSI proxy URL : http://localhost:3000

      Use the FIWARE credentials of the user : true

      NGSI scope : /

      NGSI entity types : City

      Monitored NGSI Attributes : Latitud, Longitud

      The configuration of the NGSI Entity To PoI operator is:

      Coordinates attribute : Latitud, Longitud

      NGSI source operator outputs the following error:

      “Error creating subscription in the context broker server: Unexpected response from WireCloud's proxy”

      And Browser Console outputs the followingerror:

      http://localhost/cdp/http/localhost:1... Failed to load resource: the server responded with a status of 422 (Unknown Status Code)

      I'm guessing that there is a cause to NGSIProxy.
      Do you know something cause?
      Please help me.

        Activity

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        backlogmanager Backlog Manager made changes -
        Summary [fiware-askbot] can't display the POI from ContextBroker to MapViewer FIWARE.Question.Tech.Apps.ApplicationMashup.can't display the POI from ContextBroker to MapViewer
        aarranz Álvaro Arranz made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        aarranz Álvaro Arranz made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        aarranz Álvaro Arranz made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        backlogmanager Backlog Manager made changes -
        Assignee Álvaro Arranz [ aarranz ]
        backlogmanager Backlog Manager made changes -
        HD-Chapter Apps [ 10836 ]
        mev Manuel Escriche made changes -
        HD-Enabler Wirecloud [ 10857 ]
        Description
        Created question in FIWARE Q/A platform on 23-08-2016 at 10:08
        {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/597/cant-display-the-poi-from-contextbroker-to-mapviewer/


        +Question:+
        can't display the POI from ContextBroker to MapViewer

        +Description:+
        I'm trying to connect the OrionContextBroker and Wirecloud MapViewer widget in the local environment without the FIWARE Lab.
        I want to display the POI from ContextBroker to MapViewer, but nothing appears in the map.

        The following Entity is entered in the OrionContextBroker:

        curl localhost:1026/v1/contextEntities/City1 -s -S --header 'Accept: application/json' | python -mjson.tool
        {
           "contextElement": {
                "attributes": [

                {
                    "name": "Latitud",
                    "type": "float",
                    "value": "139.692101"
                },
                {
                    "name": "Longitud",
                    "type": "float",
                    "value": "35.689634"
                }
            ],
            "id": "City1",
            "isPattern": "false",
            "type": "City"
        },
        "statusCode": {
            "code": "200",
            "reasonPhrase": "OK"
        }


        }

        The configuration of the NGSISource operator is:

        NGSI server URL : http://localhost:1026/

        NGSI proxy URL : http://localhost:3000

        Use the FIWARE credentials of the user : true

        NGSI scope : /

        NGSI entity types : City

        Monitored NGSI Attributes : Latitud, Longitud

        The configuration of the NGSI Entity To PoI operator is:

        Coordinates attribute : Latitud, Longitud

        NGSI source operator outputs the following error:


          “Error creating subscription in the context broker server: Unexpected response from WireCloud's proxy”


        And Browser Console outputs the followingerror:


          http://localhost/cdp/http/localhost:1... Failed to load resource: the server responded with a status of 422 (Unknown Status Code)


        I'm guessing that there is a cause to NGSIProxy.
        Do you know something cause?
        Please help me.
        Created question in FIWARE Q/A platform on 23-08-2016 at 10:08
        {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/597/cant-display-the-poi-from-contextbroker-to-mapviewer/


        +Question:+
        can't display the POI from ContextBroker to MapViewer

        +Description:+
        I'm trying to connect the OrionContextBroker and Wirecloud MapViewer widget in the local environment without the FIWARE Lab.
        I want to display the POI from ContextBroker to MapViewer, but nothing appears in the map.

        The following Entity is entered in the OrionContextBroker:

        curl localhost:1026/v1/contextEntities/City1 -s -S --header 'Accept: application/json' | python -mjson.tool
        {
           "contextElement": {
                "attributes": [

                {
                    "name": "Latitud",
                    "type": "float",
                    "value": "139.692101"
                },
                {
                    "name": "Longitud",
                    "type": "float",
                    "value": "35.689634"
                }
            ],
            "id": "City1",
            "isPattern": "false",
            "type": "City"
        },
        "statusCode": {
            "code": "200",
            "reasonPhrase": "OK"
        }


        }

        The configuration of the NGSISource operator is:

        NGSI server URL : http://localhost:1026/

        NGSI proxy URL : http://localhost:3000

        Use the FIWARE credentials of the user : true

        NGSI scope : /

        NGSI entity types : City

        Monitored NGSI Attributes : Latitud, Longitud

        The configuration of the NGSI Entity To PoI operator is:

        Coordinates attribute : Latitud, Longitud

        NGSI source operator outputs the following error:


          “Error creating subscription in the context broker server: Unexpected response from WireCloud's proxy”


        And Browser Console outputs the followingerror:


          http://localhost/cdp/http/localhost:1... Failed to load resource: the server responded with a status of 422 (Unknown Status Code)


        I'm guessing that there is a cause to NGSIProxy.
        Do you know something cause?
        Please help me.
        mev Manuel Escriche made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            aarranz Álvaro Arranz
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: