Here are a few questions and answers to help you if you get stuck.

Application Developers

  • How do I see the data?
    See the the Developers’ API documentation.
  • I get 403 error?
    You can access the data if you subscribe to it - and you will need the API key you used for that subscription. That API key is then used as username.
    See the the Developers’ API documentation.
  • Where can I get an access key?
    If you haven't already done so, please register and create an account on the Data Hub.
    If you would like to consume the data, you need to subscribe/activate any of the public data sets available and you create an API access key in the process.
    If you would like to provide some data, you need to create a feed, and during the process create an API key that will be used for access to write to the end point.

Data Providers

  • How do I register a new datastream?
    See the Data Providers' API documentation.
  • How do I submit data via the API?
  • My data is in CSV format, can the datahub just take it?
    No. You will need to write your own adapter that will parse the CSV values and create EEML from it. You will then POST that EEML to the endpoint (the data feed you created). datahub features include automatic RESTful API wrap of the data received.
    See the Data Providers' API for more detail and code snippets.
  • Is there a standard schema for the content of event and sensor datastreams?
    Yes. On ingress EEML/SENML is the standard schema for sensor data and a modified form of OASIS CAP is the standard schema for events. On egress data is formatted in either XML or JSON. (The format can be requested as a parameter to the URL, with the default being XML).
  • Is access over HTTPS supported, or only HTTP?
    Yes, HTTPS can also be used to access the API via [/raw][codeAPI]/{feedID}[/codeAPI][raw] and is recommended to keep keys more secure.
  • Is there a way to subscribe to feeds or datastreams so that new values can be received asynchronously without needing to poll the service?
    This feature is planned but not yet implemented. It is technically feasible but there is a need to understand what the API should look like to make it attractive/accessible to developers.
  • Is a JavaScript library provided to enable requests to be sent from web applications?
    JavaScript's security model ensures that pages can only access URLs from the same server using AJAX. This means that JavaScript in a web page cannot be used to read or write data directly. Fortunately, it's simple to work around this restriction with a little server-side code.
  • Is there a way to configure trigger conditions e.g. when a datastream exceeds a certain value?
    This is not supported directly yet, but is being considered for a future release. However, in the meantime, an application can easily monitor a data feed and create its own trigger.
  • Is there a way to enumerate via the API all the devices created by a specific account?
    Via the portal (but not via the API) it is possible for feed creators to see all their feeds. In many cases a feed will be created per sensor (device), however other approaches are possible. In future this could be added to the catalogue search, and MIS about the feeds (e.g. usage statistics) could be added. Access control/security policy must also be addressed.
  • I have a sensor network, how do I put it on the datahub?
    A sensor network could range from using your own smartphone as a sensor, to sensor-enabling your home, your business premises, your car-park, … almost anything! We've done a few so some worked examplesmight be available soon, but meanwhile, drop us a line and we’ll help you get started.
  • What if my data doesn't fit into your model?
    You can send your own data to the datahub in two ways:
    1. If your data is a sensor or an event feed then you can use the Data Providers' API
    2. For other data there is a data pipelining service available on request. Please get in touch.
    The Data Provider’s API uses data standards such as EEML and SENML to simplify inter-working. Simply create the data feed using our online form, this returns a URL to which you can post your data using a private key. To find out more about self-service data on-boarding, see browse our Getting Started section.
  • Who is the Data Owner?
    datahub is treating Data Provider as the owner of the data. You will be responsible for the metadata, availability and/or update of the data. For datahub detailed terms and conditions, please look at this page
  • Does the Data Hub need to keep a copy of my data?
    No, we could proxy requests to your API and this is available on request. Please get in touch.
  • Can I store personal data on the datahub?
    datahub is not intended to be used to store and process personally identifiable information. Please contact the administrators if you have a need to process data of this type.