jmcantera's profile - activity

you can get the data directly from Orion and then use Leaflet or any other Geo Visualization Library. I did some work in the past that might be outdated but can serve you as an starting point

https://github.com/jmcanterafonseca/l...

if you separate your different subscriptions by fiware-service it is possible, Wilma proxy can now associate user's organizations to fiware-service, so if you create a user under org A and another under org B, then you can create subscriptions belonging the different fiware services (with name equal to the organization) and afterwards they will only be accessed by each user

probably, try

you need to execute a command `show databases` and see how many orion-xxx are

as per the FIWARE Release, here there are the compatibility tables: https://github.com/FIWARE/catalogue/releases/tag/FIWARE_7.7.1

I would not recommend you to use the Fiware-Service-Path, as you may easily end up generating Entities with same Id in different Service-Paths without having a clue from which Service-Path are Entities coming when you query.

Wrt Service, please check, using the MongoDB client, that you have one mongoDB DB per fiware-service and that your entities are correctly stored.

Thanks!

Provided that you dump your data to the proper data store, in the proper format you can use whatever BI tool you want

Yes, what you are saying is correct. And the mapping can be done using the IoT Agents or your favourite integration tool

hello,

Here you will find some general information

https://www.fiware.org/contact-us/

The mailing list fiware-collaboration-req@lists.fiware... can be useful to make your contribution proposal.

On a project by project basis you would need to check the contribution policy of each project present at each Github Repo.

Thanks!

there are no license costs, you can build your own platform using FIWARE components, although you would need to respect the conditions of each GE OSS License, please check.

hi,

You can do both, you can create an adaptor to the IoT Agent or you can just create your own IoT Agent that talks to Meteobridge, using the IoT Agent library

https://github.com/telefonicaid/iotag...

thanks,

Do you know how many cities are currently using FIWARE?

Hi Rafael,

We have not set up yet a Slack channel but it is our intention to do it very soon. In the meantime you can use this channel, Stackoverflow or Github.

Thanks!

IoT Broker is not needed. Actually IoT Broker is just an alternative implementation of the OMA NGSI 9 interfaces.

could you please send us details about how Cepheus is subscribed to Orion?

For instance, the HTTP REST request and payload being used

thanks

A v2 subscription can also be used you just need to set attrsFormat to legacy. Example:

{ "description": "Notify me of all product price changes", "subject": { "entities": [{"idPattern": ".*", "type": "Product"}], "condition": { "attrs": [ "price" ] } }, "notification": { "http": { "url": "http://context-provider:3000/subscription/price-change" }, "attrsFormat" : "legacy" } }

other options are STH Comet (unfortunately it only supports a flavour of NGSIv1 ... ). See http://fiwaretourguide.readthedocs.io...

here a tutorial for Cygnus and MySQL

http://fiwaretourguide.readthedocs.io...

and another component Quantum Leap (more aligned with NGSIv2, using Crate as DB) is an alternative

https://github.com/smartsdk/ngsi-time...

maybe some of the companies of the FIWARE Consortium own a module like that but there is no open source project in the community dealing with such problems. There are some data models on waste management, please check https://schema.fiware.org

best

responded here

https://github.com/telefonicaid/iotag...

You can do asset management using the Orion Context Broker as a backend. All the assets can be entities and you can create, update, delete or query them. You can provide geospatial properties using GeoJSON.

As front-end you would need to implement your own application.

We are currently updating the fiware.org website. Sorry for any inconvenience. If you have any questions, or would like to report a bug, please contact us at fiware-website@lists.fiware.org.

as far as I know there are so specific components to deal with that. If you develop them as open source they can be welcome to ecosystem

thanks

hi,

Good question. You can certainly use a Device entity linked to a WasteContainer entity and use the Device entity to store battery level, configurations and the like.

For certain device conditions that should be alerted, why don't you use the Alert entity type?. The Alert entity type could be extended to cover new Alert categories and subcategories. If you opt for that approach a Pull Request that extends the current Alert data model (with categories and subcategories for alerts originated in devices) will be more than welcome.

Thanks, best

Hi,

I think you would need to have a look at Perseo, a Complex Event Processing implementation that integrates with the Orion Broker

see https://github.com/telefonicaid/perse...

and

https://drive.google.com/open?id=0B_p...

thanks

Currently we don't have specific APIs for Mobility as a Service. You can always create new APIs on top of the NGSI APIs.

You can check API Umbrella

https://apiumbrella.io/

soon it will be integrated with OAuth token management

The FIWARE Marketplace is playing the promotion role, please check

http://marketplace.fiware.org

please can you refine this question a bit more, particularly the specific issues you may have with Fiware technologies?

Thanks, best

Hi,

You cannot do that and should not do that. Even though there is a workaround, using data URIs, I would not recommend it if images are going to be bigger.

For storing images my recommendation is to use an object storage service such as S3 or Swift. The latter can be used from the Fiware Lab. Then, Orion entities can have an attribute (a URL) that will point to the object storage and in particular to the referenced image, such as

{ "id": "MyBuilding", "type": "Building", "photo": { "type": "URL", "value": "http://object.storage.org/objId" } }

hi,

Easy way, publish your CKAN data as Orion Broker entities.

Some existing data models are at http://schema.fiware.org

and the Orion Broker APIs Summary are at

http://fiware-orion.readthedocs.io/en...

josemanuel.cantera at fiware dot org

have you read this resource?

http://fiwaretourguide.readthedocs.io...

hi,

Sounds like a nice project. I think you should be using Kurento and Orion, but nonetheless I would like to have a conversation with you

best

please check the public IP of your instance under https://cloud.lab.fiware.org

you need to connect to the Cloud portal (http://cloud.lab.fiware.org) in order to know what is the public IP address of the virtual machine on which Orion is running (under the instances section). Then, probably you need to check your security groups so that the 1026 port is open. I think you don't need to manage it directly through the firewall command, it can be done through the portal.

I cannot find now a tutorial of the FIWARE Lab, please someone from the community can complement this response?

thanks

this seems to be a network connectivity problem. please check that you get access to any other external service or address

thanks

see

https://github.com/Fiware/showcase.sm...

Please have a look at

developer.fiware.org

thanks

hi,

As the Raspberry Pi is a device that can speak FIWARE NGSI directly, the easiest way would be to use a Python script to obtain the data coming from the Raspberry Pi Sensors and then use the NGSIv2 API to publish the data offered by the sensors connected to the Raspberry on a Orion Context Broker.

You can deploy your own Orion Context Broker instance, on your laptop, for instance using Docker

docker run fiware/orion

You can pre-create the entity you are going to use to store the sensor data, for instance:

POST /v2/entities

{ "id": "MyObservation-RaspberryPi-890", "type": "Observation" }

Then every time a new sensor measurement is obtained from the Raspberry Pi you can

POST /v2/entities/MyObservation-RaspberryPi-890/attrs

{ "temperature": { "value": 23.5 } }

You can get the temperature value by getting your entity data as follows:

GET /v2/entities/MyObservation-RaspberryPi-890?options=keyValues and you will get something like

{ "id": "MyObservation-RaspberryPi-890", "type": "Observation", "temperature": 23.5 }

Of course, your laptop and the Raspberry Pi have to be on the same network.

Other architectures more complicated could make use of IoT Agents but in this case it is not even needed.

I hope this helps

best

we have got in touch with you through email

thanks

yes, indeed

FIWARE based architectures are open, modular and scalable. This means that integrating existing systems can be quite easy thanks to this characteristic inherent to FIWARE. As a result FIWARE can coexist with legacy architectures, Furthermore FIWARE does not preclude operating systems or programming environments.

Having said that, and with regards to Context Data managed by the city, the NGSI9 context providers are a nice mechanism to integrate existing data sources and expose them as NGSI entities. For more information, please check

http://fiware-orion.readthedocs.io/en...