From pablofernandezmoniz at gmail.com Fri Sep 9 12:41:20 2016 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Fri, 9 Sep 2016 11:41:20 +0100 Subject: [Fiware-developer-experience] Documentation tasks. Message-ID: Hi, Following We enumerate the different tasks established on the skype meeting on 9th September of 2016 ULPGC must check and align: - cookbook - NGSIv2 - Tour Guide And the main documentation task to be resolved in MarkDown format: 1) Install docker on Windows, Mac and Linux. Bitergia 2) Clone the repository. Bitergia 3) Steps to instantiate Orion and some queries examples. ULPGC 4) Starting with IoT, simulate sensors, generate sensor data and link with Ckan and Cosmos. Bitergia 5) Starting with IdM, rules. Bitergia 6) Initialize the front-end. ULPGC Deadline on 20th September to have, at least a draft, of most of the sections. Documentation will be developed at https://github.com/Fiware/docs.TourGuide Regards ULPGC team, -------------- next part -------------- An HTML attachment was scrubbed... URL: From pablofernandezmoniz at gmail.com Fri Sep 23 16:13:52 2016 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Fri, 23 Sep 2016 15:13:52 +0100 Subject: [Fiware-developer-experience] Create a geolocated restaurant with "options=keyValues" Message-ID: Hi, We were requested to add an example of how to add a restaurant in the Tourguide Application using the *options=keyValues* parameter. So, we are performing a request like: POST :/v2/entities?options=keyValues HEADERS: { "Fiware-Service: "tourguide", "Fiware-ServicePath": "/Franchise1", "Content-Type": "application/json" } PAYLOAD: { "id": "sample-id1", "type": "Restaurant", "address": { "streetAddress": "Cuesta de las Cabras Aldapa 2", "addressRegion": "Araba", "addressLocality": "Alegr?a-Dulantzi", "postalCode": "01240" }, "aggregateRating": { "ratingValue": 3, "reviewCount": 98 }, "capacity": 100, "department": "Franchise4", "description": "Sample description", *"location": "42.8404625, -2.5123277",* "name":"Sample-restaurant", "priceRange": 0, "telephone": "945 400 868" } The problem is that the location field is not interpreted as "geo:point", it is interpreted as text. We checked it by retrieving the created entity: GET :/v2/entities/sample-id1 HEADERS: { "Fiware-Service: "tourguide", "Fiware-ServicePath": "/Franchise1" } RESPONSE PAYLOAD: { "id": "sample-id1", "type": "Restaurant", "address": { "type": "StructuredValue", "value": { "streetAddress": "Cuesta de las Cabras Aldapa 2", "addressRegion": "Araba", "addressLocality": "Alegr?a-Dulantzi", "postalCode": "01240" }, "metadata": {} }, "aggregateRating": { "type": "StructuredValue", "value": { "ratingValue": 3, "reviewCount": 98 }, "metadata": {} }, "capacity": { "type": "Number", "value": 100, "metadata": {} }, "department": { "type": "Text", "value": "Franchise4", "metadata": {} }, "description": { "type": "Text", "value": "Sample description", "metadata": {} }, *"location": { "type": "Text", "value": "42.8404625, -2.5123277", "metadata": {} },* "name": { "type": "Text", "value": "Sample-restaurant", "metadata": {} }, "priceRange": { "type": "Number", "value": 0, "metadata": {} }, "telephone": { "type": "Text", "value": "945 400 868", "metadata": {} } } We also tried to perform a geoquery and the restaurant is not shown as we expected: GET :/v2/entities?georel=near; maxDistance:10&geometry=point&coords=42.8404625,-2.5123277&attrs=name HEADERS: { "Fiware-Service: "tourguide", "Fiware-ServicePath": "/Franchise1" } RESPONSE PAYLOAD: [{ "id": "0115206c51f60b48b77e4c937835795c33bb953f", "type": "Restaurant", "name": { "type": "Text", "value": "Elizalde", "metadata": {} } }] Is this the expected behaviour? Are we creating the entity wrongly? Should we add a ticket for Orion in SoF? Thanks, ULPGC team -------------- next part -------------- An HTML attachment was scrubbed... URL: From josemanuel.canterafonseca at telefonica.com Wed Sep 28 10:11:45 2016 From: josemanuel.canterafonseca at telefonica.com (JOSE MANUEL CANTERA FONSECA) Date: Wed, 28 Sep 2016 08:11:45 +0000 Subject: [Fiware-developer-experience] Create a geolocated restaurant with "options=keyValues" In-Reply-To: References: Message-ID: <6A2ABC3A-8D57-4EFA-B154-CB4638EEAA67@telefonica.com> As we said over chat you need to specify attribute type explicitly , as Orion cannot distinguish between string and geo:point with only providing a string best From: on behalf of Pablo Fern?ndez Moniz Date: Friday 23 September 2016 at 16:13 To: "fiware-developer-experience at lists.fiware.org" Subject: [Fiware-developer-experience] Create a geolocated restaurant with "options=keyValues" Hi, We were requested to add an example of how to add a restaurant in the Tourguide Application using the options=keyValues parameter. So, we are performing a request like: POST :/v2/entities?options=keyValues HEADERS: { "Fiware-Service: "tourguide", "Fiware-ServicePath": "/Franchise1", "Content-Type": "application/json" } PAYLOAD: { "id": "sample-id1", "type": "Restaurant", "address": { "streetAddress": "Cuesta de las Cabras Aldapa 2", "addressRegion": "Araba", "addressLocality": "Alegr?a-Dulantzi", "postalCode": "01240" }, "aggregateRating": { "ratingValue": 3, "reviewCount": 98 }, "capacity": 100, "department": "Franchise4", "description": "Sample description", "location": "42.8404625, -2.5123277", "name":"Sample-restaurant", "priceRange": 0, "telephone": "945 400 868" } The problem is that the location field is not interpreted as "geo:point", it is interpreted as text. We checked it by retrieving the created entity: GET :/v2/entities/sample-id1 HEADERS: { "Fiware-Service: "tourguide", "Fiware-ServicePath": "/Franchise1" } RESPONSE PAYLOAD: { "id": "sample-id1", "type": "Restaurant", "address": { "type": "StructuredValue", "value": { "streetAddress": "Cuesta de las Cabras Aldapa 2", "addressRegion": "Araba", "addressLocality": "Alegr?a-Dulantzi", "postalCode": "01240" }, "metadata": {} }, "aggregateRating": { "type": "StructuredValue", "value": { "ratingValue": 3, "reviewCount": 98 }, "metadata": {} }, "capacity": { "type": "Number", "value": 100, "metadata": {} }, "department": { "type": "Text", "value": "Franchise4", "metadata": {} }, "description": { "type": "Text", "value": "Sample description", "metadata": {} }, "location": { "type": "Text", "value": "42.8404625, -2.5123277", "metadata": {} }, "name": { "type": "Text", "value": "Sample-restaurant", "metadata": {} }, "priceRange": { "type": "Number", "value": 0, "metadata": {} }, "telephone": { "type": "Text", "value": "945 400 868", "metadata": {} } } We also tried to perform a geoquery and the restaurant is not shown as we expected: GET :/v2/entities?georel=near;maxDistance:10&geometry=point&coords=42.8404625,-2.5123277&attrs=name HEADERS: { "Fiware-Service: "tourguide", "Fiware-ServicePath": "/Franchise1" } RESPONSE PAYLOAD: [{ "id": "0115206c51f60b48b77e4c937835795c33bb953f", "type": "Restaurant", "name": { "type": "Text", "value": "Elizalde", "metadata": {} } }] Is this the expected behaviour? Are we creating the entity wrongly? Should we add a ticket for Orion in SoF? Thanks, ULPGC team -------------- next part -------------- An HTML attachment was scrubbed... URL: