SenseSmartRegion » SSiO

Me, karan and Andreas had a meeting last week discussing the basics: We presented the first use-case where our Hololens solution from CGI needs live sensor data - based on the units position aso...

We came to the conclusion that we should specify our way to access sensors by position on and utilize the Geolocation capabilities in the NGSIv2 protocol - a part of the Orion broker - already stated/recommended by Fiware. The geo capabilities are well suited for all our needs with both simple methods and more advanced.

And that we should make a public API available for external requests. This with the basics arguments needed for requesting data (login credentials, position X/Y, search radius aso) - eg in this case CGI and the hololens...

Sokigos suggestion is that we implement our basic layout/idea in a proof of concept - tested with the Hololens demo. We think Sokigo are suited to do this work?!

To do now:
Specify how the request should look like/parameters - and what kind of response it will produce in the version 1...

Me, karan and Andreas had a meeting last week discussing the basics: We presented the first use-case where our Hololens solution from CGI needs live sensor data - based on the units position aso...

We came to the conclusion that we should specify our way to access sensors by position on and utilize the Geolocation capabilities in the NGSIv2 protocol - a part of the Orion broker - already stated/recommended by Fiware. The geo capabilities are well suited for all our needs with both simple methods and more advanced.

And that we should make a public API available for external requests. This with the basics arguments needed for requesting data (login credentials, position X/Y, search radius aso) - eg in this case CGI and the hololens...

Sokigos suggestion is that we implement our basic layout/idea in a proof of concept - tested with the Hololens demo. We think Sokigo are suited to do this work?!

To do now:
Specify how the request should look like/parameters - and what kind of response it will produce in the version 1...

Me, karan and Andreas had a meeting last week discussing the basics: We presented the first use-case where our Hololens solution from CGI needs live sensor data - based on the units position aso...

We came to the conclusion that we should specify our way to access sensors by position on and utilize the Geolocation capabilities in the NGSIv2 protocol - a part of the Orion broker - already stated/recommended by Fiware. The geo capabilities are well suited for all our needs with both simple methods and more advanced.

And that we should make a public API available for external requests. This with the basics arguments needed for requesting data (login credentials, position X/Y, search radius aso) - eg in this case CGI and the hololens...

Sokigos suggestion is that we implement our basic layout/idea in a proof of concept - tested with the Hololens demo. We think Sokigo are suited to do this work?!

To do now:
Specify how the request should look like/parameters - and what kind of response it will produce in the version 1...

Me, karan and Andreas had a meeting last week discussing the basics: We presented the first use-case where our Hololens solution from CGI needs live sensor data - based on the units position aso...

We came to the conclusion that we should specify our way to access sensors by position on and utilize the Geolocation capabilities in the NGSIv2 protocol - a part of the Orion broker - already stated/recommended by Fiware. The geo capabilities are well suited for all our needs with both simple methods and more advanced.

And that we should make a public API available for external requests. This with the basics arguments needed for requesting data (login credentials, position X/Y, search radius aso) - eg in this case CGI and the hololens...

Sokigos suggestion is that we implement our basic layout/idea in a proof of concept - tested with the Hololens demo. We think Sokigo are suited to do this work?!

To do now:
Specify how the request should look like/parameters - and what kind of response it will produce in the version 1...