Thames Tunnel: the Many Forms of Web GIS Reporting
Thames Tunnel: The manyforms of Web GIS ReportingBrad FisherGIS Technical LeadBrad.Fisher@tidewaytunnels.co.uk
Thames Tunnel Background 39 million cubic metres of sewage discharged to tidal River Thames in a typical year. As little as 2mm of rain can now trigger a discharge. Environmental - tides mean the sewage stays in the river for weeks, affecting dissolved oxygen levels and habitats Human – frequency of Combined Sewer Overflow (CSO) discharges is a potential hazard to all river users Legal – the UK fails to comply with the EU Urban Waste Water Treatment Directive.
Thames Tunnel challenges Meet requirements of Minister’s Direction in most cost efficient manner Intercept the flow from the 34 most polluting CSO’s (of 57) as identified by the Environment Agency Construction of one of the longest and deepest tunnels ever built beneath London Deal with variable ground conditions – London Clay, Lambeth Group, Thanet Sands and Chalk Minimise impact on surface and subsurface infrastructure Control odour and air release during tunnel filling
Preferred route and sites (phase one andinterim engagement)
Major Infrastructure Project A very complex & large engineering project for a GIS to support.
Primary role of GIS in ThamesTunnel is to support ‘informed’ decision making
Access to Information SS TPI Planning Enviro HS&E Design Prj Ctrls Geotech Property Doc Ctrl HS&E Modelling HR IT Survey Comms
GIS Deliverables in Thames Tunnel Analysis 6 GIS web apps Mobile apps Data Management 200+ contractors Data translation Trust in data Integrity Integrity Information 220+ data requests Deliverables Visualisation 750 data layers 33 000 maps Information Quality 200 Gb Data
Many sources of data / information Land useHistoric mapping Survey Data Piles of maps Property info Social As Built Drawings networks Photo’s
GIS Solutions Historic Mapping ViewerGeoPlan Twitter map Land Referencing Survey Data Original As Built Drawings
What is a Report? Wiki Definition: A report is a textual work (usually of writing, speech, television, or film) made with the specific intention of relaying information or recounting certain events in a widely presentable form. Reports are often wanted as some form of document (hardcopy (paper map) or softcopy (pdf)).
Reporting is not easy in a Web GIS Reporting is not easy – Few OOTB solutions – Bespoke Solutions not ideal – Its not necessarily hard (from dev perspective, moderate effort) BUT its tedious (to say least)
Challenges for web reporting Scale is everything – Even the scale bar tedious WYSIWG Resolution (dpi) / file size Page Size (support for large format printing (> A3) Interaction with selected sets of data Cached service issues Legends
Where are we at? – Historically a desktop solution – RIA have had a profound impact on our web based GIS applications functionally & user-expectations. – ArcGIS ADF could leverage off map templates (mxt) & with a bit you could come up with a decent solution. – REST releases to date still does not readily cater for printing to scale. – Geoprocessing (arcpy.mapping) offers opportunity – Third-party solutions/extensions
Moving forward Core reporting capabilities are slowing becoming mainstream (tomorrow will not be quick enough) – 10.1 proposing to offer printing exposed as a REST service – I think we may will see more third party & sample solutions that leverage off the 10.1 core capabilities
Reporting in GIS Web Apps Is Still a ChallengeBut its getting easier