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

[fiware-stackoverflow] Transport FIWARE Orion Data to FIWARE CKAN

    Details

    • Type: Monitor
    • Status: Closed
    • Priority: Major
    • Resolution: Dismissed
    • Affects Version/s: None
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:

      Description

      Created question in FIWARE Q/A platform on 28-05-2020 at 11:05
      Please, ANSWER this question AT https://stackoverflow.com/questions/62061838/transport-firware-orion-data-to-fiware-ckan

      Question:
      Transport Firware Orion Data to Fiware CKAN

      Description:
      We have some data from sensors which is published on Firware Orion. We'd like to visualize the data in the Fiware CKAN Open Data Portal using Fiware Draco. At this moment the Draco (Nifi with NGSI extension) creats a table in the PostGres public namespace with an encoded name. This is an issue because the CKAN portal requires a valid guid as table name.
      Does anyone has any suggestion?

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        32d 22h 25m 1 Andres Muñoz 30/Jun/20 10:31 AM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        andres.munoza Andres Muñoz made changes -
        Resolution Dismissed [ 10102 ]
        Status Open [ 1 ] Closed [ 6 ]
        fla Fernando Lopez made changes -
        HD-Enabler Draco [ 11536 ]
        Description
        Created question in FIWARE Q/A platform on 28-05-2020 at 11:05
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/62061838/transport-firware-orion-data-to-fiware-ckan


        +Question:+
        Transport Firware Orion Data to Fiware CKAN

        +Description:+
        We have some data from sensors which is published on Firware Orion. We'd like to visualize the data in the Fiware CKAN Open Data Portal using Fiware Draco. At this moment the Draco (Nifi with NGSI extension) creats a table in the PostGres public namespace with an encoded name. This is an issue because the CKAN portal requires a valid guid as table name.
        Does anyone has any suggestion?
        Created question in FIWARE Q/A platform on 28-05-2020 at 11:05
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/62061838/transport-firware-orion-data-to-fiware-ckan


        +Question:+
        Transport Firware Orion Data to Fiware CKAN

        +Description:+
        We have some data from sensors which is published on Firware Orion. We'd like to visualize the data in the Fiware CKAN Open Data Portal using Fiware Draco. At this moment the Draco (Nifi with NGSI extension) creats a table in the PostGres public namespace with an encoded name. This is an issue because the CKAN portal requires a valid guid as table name.
        Does anyone has any suggestion?
        fla Fernando Lopez made changes -
        Assignee Andres Muñoz [ andres.munoza ]
        fla Fernando Lopez made changes -
        Summary [fiware-stackoverflow] Transport Firware Orion Data to Fiware CKAN [fiware-stackoverflow] Transport FIWARE Orion Data to FIWARE CKAN
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2020-05-28 12:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2020-05-28 12:05|CREATED monitor | # answers= 0, accepted answer= False
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            andres.munoza Andres Muñoz
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: