overview

1
overview
peerDS?
Discovery?
ServerStuff
Not so soon
Tablet
GPS
soon
Already got
G
CO
COProbe
localDS
globalDS
I
3D
H
J
Grid bypass
GridProxy (EQUIP)
PolnLayers
GridDB
EQUIP connector?
K
??
M
QueryGadget
lifejacket
MapGadget
GridProxy (lifejacket)
sensor
E
CO
PDA??
(subsumed)
CO
D
F
Experiments on with children
GridProxy (file)
3D model
B
fatclient
Sensor Website(s)
L
image
datasouvenir
C
UCLDB
GPS
3Dvis
PDA
DBproxy
logger
upload
webquestsite
Inventor Model files 100MB
Model viewer
A
CO
log
alarmphone
browser
OS map stuff
2
Plenary Agenda

• Development agenda
• write code
• Get data
• Do demo

• Status update
• (Talk to ben croxford (tomorrow))
• Choice of pollution sensing devices
• Talk about schools activity (not too late)
• Future activities, money, plans, public
  underst?
• Design/specify interfaces between sub-activities,
  esp. RCA data souvenirs, phonealarm, Sussex web
  quest
• Design City integration (GSq)
• GSq 3D issues?
• Talk about/design next steps on 3D visn
• (Plan activities for next 6 months)

3
Sensor/data requirements

• UCL/Vis dense pollution trails, one area,
  GPS-referenced (1?!-10)
• Ben Croxford (meteorology??) ?
• Schools 1/a few(5)/30(class) (per school)
• Click to probe? Read in place? Download? Log in
  one place? GPS-registered?
• Public understanding (device?)
• Simple, integrated, comprehensible
• Linked to schools collection??
• Personal exposure/clinical (?) (as many as pos.)
• Personal, worn?, position/reference data
  referenced
• GSq/field scientist GPS-referenced (1/site)

4
A phonealarm (later)

• Map or table or pollution data that can be
  cross-referenced to phone cells
• Preferably derived from the UCL-based pollution
  trail database (or later schools activities)
• Issues
• Time of day? Average?
• Geographical coverage?
• Updates/changes?
• Extension/integration with miniGPS/equivalent?
• By whom? (not RCA)
• Requires pollution trail -gt map service
• Presentation, maps or tables (if keys readily
  mappable)
• Mapping to cell averages
• (UCL, RCA to progress)

5
B datasouvenir

• A web page (e.g. from antarctic sensor (and/or
  national archive)) published live, with
  identifiable field for data
• Timeliness/frequency? Issue for exploration
• Say every 5 minutes? Every 2 hours?
• Time delays/chunking of data?
• (a) true/faithful (most recent)
• (b) finer-grained/delayed
• All sensors in labelled page or individual
  pages
• (persistent, publicly accessible service)

6
C webquest

• Antarctic
• Site usable by kids to query, e.g. by sensor,
  time period (season, time of day)
• Output CSV files, HTML tables, generated graphs
  (images)
• (requires persistent publicly available service)
• Urban
• As per A
• Or direct view of individual trails from DB

7
D/E database access/integration

• UCL
• dev-id (int ?) x Time -gt OSGB (lat/long), CO,
  (CO-base), temp
• Postgres (spatial data extension) (else Oracle)
• Will support query by lat/long when installed
• (see also Marek Bells Wireless maps by position)
• (cygwin issues?)
• GridDB (XSIL)
• Dev -gt sensors sensor -gt configuration, time,
  data format, sensor type sensor type sensor x
  sequence x value(s) (incl. Time)
• Default use Postgres with Grid database
• use spatial extensions for GIS stuff
• Manuel ?Chris/?????Don/

8
F log file grid polution sensor proxy

• Low priority can get the data into the database
  easier through versions of existing device log
  uploaders (to new unified DB)

9
G/H local GSq pollution probe and map layer

• Local CO device as Probe publishes to EQUIP yes
• Map
• 1. Map layer dots for samples in dataspace
• 2. On demand map viewing layer, w. CGI-BIN
  interface to generate 2D (or 3D) models on demand
• Image with alpha layer of interpolated polution
• Issues
• Specifying the query via second gizmo?
  Enable/disable layers?

10
I/J EQUIP sensor meets grid sensor

• Direct global equip DS lt-gt DBMS gateway
• Lower priority for EQUIP data item to Grid
  device/sensor proxy (more work doesnt force
  EQUIP issues as clearly)

11
K/L 3D visualisation refactoring/GSq 3D
integration

• CGI-BIN service to generate 2D/3D models with
  interpolated pollution visualisation on demand
  (DEFAULT)
• 3D visualiser to fetch models from URLs
• Streaming order??
• OR Renderer with internal SQL query/visualisation
  capability
• (e.g. to dynamically recolour the city geometry)
• Issues
• Coordination layers, content, queries

12
M lifejacket pollution sensor

• Yes please
• Waiting on the device discussion and involvement
  from Nott.EEE/Bristol

13
Soon

• DataItem types DataBase implications
• CO Probe for GSq Belt (Paul, Stef? Jan?)
• Map Layer for GSq displaying probe reports
  (SteveN)
• Maps which show this area for the belt
• Map layer for GSq gets and displays pollution map
  images from (new) server (SteveN?)
• Server which serves pollution map (Anthony?)
• Interface
• Images
• 3D models (Ying?)
• ? Gizmo for layer control and/or query specn

• 3D renderer extension to get show models
  including pollution info (Anthony? Chris?)
  (Ying?) EQUIP service for fetching stuff
• EQUIP lt-gt sensor database connector (Chris?)
• Servlet(s) for
• Latest sensor data (Jan, Stef?)
• Sensor data from a certain time ago
• Blocks of sensor data queried by sensor, time
  spans
• Available devices/sensors

14
Not as soon

• Server queries DB rather than files
• Build some sensors? (Manuel)

• 3D renderer extension to dynamically modify model
  
• Whatever Servlet(s) havent been done yet
• Latest sensor data
• Sensor data from a certain time ago
• Blocks of sensor data queried by sensor, time
  spans
• Available devices/sensors
• Migrate Grid DB to Postgres incorporate/assimila
  te UCL polution schema and data??
• Convert existing UCL DB-using apps to use Grid DB
  schema

15
Visualisation query

• Input
• Time period
• Area/region OSGB lat/long (square or centre
  size)
• With paths boolean
• Coverage one of road/pavement only, complete
• Output
• 3D model, coloured, with paths
• 2D map, alpha?, colour