LarKC WP4+WP6 Teleconference, 14.00 -15:00, July 19, 2010
Participants
Stanley (Saltlux), Tony (Saltlux), Reto (STI), Zhisheng (VUA), Spyros(VUA), Irene (CEFRIEL), Michael (?CycEuro)
Agenda
- Dataset and schema for Road sign Usecase
- SPARQL endpoint, query examples for reasoning
- Available reasoning with regard to Scenario.
- Making workflows for Usecase
Dataset and schema for Road sign Usecase
- Seoul POI Data
POI RDB data from Saltlux internal project.
POI count : 67,724
It contains Spot type and Line type POI
Property : ID, Name, wgs84Lat, wgs84Lng
Not yet Triplified
- Road Sign Data
1) Road sign dataset
Triplifed with ID, wgs84Lat, wgs84Lng
Road sign count : 9,514
- 2) Road sign line type POI dataset
Triplified Found coordinate from Seoul POI : 89 of 255
Not found coordinate from Seoul POI : 166 of 255
- 3) Road sign spot type POI dataset
Triplified Found coordinate from Seoul POI :793 of 1,513
Not found coordinate from Seoul POI : 720 of 1,513
- 4) Road sign direction dataset
Road sign dataset contain POI dataset as road sign information.
ID, hasLongLeft, hasShortLeft, hasLongForward, hasShortForward, hasLongRight, hasShortRight
- Open Street Map
1) OSM Nodes dataset
Triplifed with nodeID, wgs84Lat, wgs84Lng
Node count : 99,212
- 2) OSM Nodes Info dataset
Triplifed with nodeID, name, category
Info count : 21,150
- 3) OSM Way dataset
Triplifed with wayID, wayNodes
Way count : 4,283
- 4) OSM Way Info dataset
Triplifed with wayID, wayName
Name is written Korean
Not all the info to way dataset
- Linked Geo Data
1) LGD Seoul nodes dataset from LGD complete
Extracted triples with nodeID, wgs84Lat, wgs84Lng
All the node in Seoul : 603
- 2) LGD Element
need to match LGD Seoul nodes to extract related elements
- Mediate Ontology
need to make a model to link datasets of RSD, OSM, LGD extracted.
SPARQL endpoint, query examples for reasoning
Road sign management Demo URL : http://larkc.saltlux.kr/rsm/
The demo only works in Internet Explorer, not in Chrome and not in Firefox.
- Michael Witbrock: Probably some very small Javascrip error to do with handling the "Show" button, from the behaviour.
Available reasoning with regard to Scenario
[Scenario 2] Recommending new road signs by changed road sign regulations Validation check through Road signs to destination POI.
Task 1. Retrieving all the Road signs containing selected destination POI. 1. Show POIs within map screen. 2. Click city hall with mouse right button. 3. Send query about retrieving all the road signs that contain cith hall name.
Task 2. Retrieving the way related to a road sign planque from Open street map. 1. find out a way containing a retrieved road sign with inference. 2. find out the forward direction of road sign with nodes of way. 3. if there is no way for the road sign, that road sign is invalid and checked.
Task 3. Checking validation of road sign information along the nodes of way 1 chasing the city hall along the nodes of way that meet next road sign. 2. If the road sign meet next road sign containing city hall, check valided and saved temporary. 3. If there is no city hall in next road sign, find POIs that has the name of city hall within 1Km. 4. If city hall is founded, all the road signs are valid
Task 4. Changing a invalid road sign information by another road sign. 1. If invalid road sign have previous road sign containing city hall and the next road sign containing city hall,
- the invalid road sign mark city hall instance on the direction of the next road sign.
Making workflows for Usecase
Spyros will support it.
Actions
* Stanley will send the data, the PPTs, and the documents
* Zhisheng and Spyros will check the data and see how to make validation checking for the scenario 2 (namely, Task 3)
* Irene will create a wiki for the task
* Michael: Luka will be in Korea, and may help with that?