Esri Scotland Conf 2016 - SEPA
•Descargar como PPT, PDF•
1 recomendación•4,069 vistas
Flood Event Data Capture
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Esri Scotland Conf 2016 - SEPA
Similar a Esri Scotland Conf 2016 - SEPA (20)
Más de Esri UK
Más de Esri UK (20)
Último
Último (20)
Esri Scotland Conf 2016 - SEPA
- 1. Flood Event Data Capture using out-of-the-box ESRI software Karen Pinkerton & Kirsty Jack karen.pinkerton@sepa.org.uk, kirsty.jack@sepa.org.uk
- 2. Why does SEPA need flood event data? Flood hazard and risk mapping (section 21) National Flood Risk Assessment (NFRA) reporting significant events to EEC and EU Floods directive (section 9) Flood warning activities (section 74) Planning advice (section 72) FRM Strategies (section 27)
- 3. Why does SEPA need flood event data? What is observed flood event data? What is observed flood event data?
- 4. Improving data capture, management & use
- 5. Data Capture: The Problem
- 6. The solution - FEDCAP FEDCAP – A tool for Flood Event Data CAPture utilising ArcGIS Online and the ESRI Collector App for the winter trial Free*Free* FlexibleFlexible SecureSecure Simple!Simple!
- 7. The solution - FEDCAP Methodology •Create two feature classes, add domains •Create a map and adjust symbology to suit •Publish to ArcGIS Online •Set up permissions and share •Choose a suitable basemap •Download offline map •Capture data •Sync data
- 8. FEDCAP Winter Trial Winter trial environment – record breaking! •Wettest December on record in Scotland •Over 200% of average rainfall fell in NE •50/400 river gauges in Scotland experienced record peak flows •Multiple flooding events, widespread over Scotland •Over 1000 properties flooded across Scotland http://www.metoffice.gov.uk/climate/uk/summaries/2016/winter http://www.ceh.ac.uk/news-and-media/news/warmest-wettest-november-january-record
- 10. FEDCAP Winter Trial Comparison with traditional methods Data quality • Georeferenced photographs • Could “georeference” videos • High resolution camera on iPad • Focused information captured for specific point • More information available in the field • Too many fields to fill in for all features • Recorded • 313 point features • 620 photographs/videos • 68 line features (trashlines/routes)
- 11. FEDCAP Winter Trial Comparison with traditional methods Time saved • Seconds to log in and load up • Takes a few minutes to capture • Slightly longer in the field than a camera • Reduces survey time by half compared with GPS • Reduces processing time by days • Easy to share data without hardware
- 12. FEDCAP Winter Trial Comparison with traditional methods Survey accuracy • <10cm difference after re-projection • Less detail as no elevation is captured
- 13. Winter trial achieved a strong correlation between surveyed data and data captured via the solution a reduction in the time spent processing data an increase in the quantity of data received in the immediate aftermath of a flood an improvement in the quality and consistency of data received in the aftermath of a flood event positive response from SEPA and Local Authority staff FEDCAP Winter Trial
- 14. What’s next? Future development •Continue trial period •Simpler form as many fields were not applicable to task •Add more information to FEDCAP e.g. specific SEPA basemaps •Improve processes for increased consistency when capturing data e.g. side of trash line •Improve post processing script to become fully automated
- 15. FEDCAP Winter Trial In summary the trial of the ESRI Collector App has •Improved data quantity and quality, providing great business benefit •Enabled the access of more information in the field •Saved time in capture and processing to attain useable information •Secure way to share with internal and external sources with quick interpretation •Simple to set up, use and modify •Lots of scope to improve further and adapt for other purposes
- 16. Thank you for listening! Some FEDCAP users. Testimonials Very good tool for capturing trash lines and also georeferenced photos - much more meaningful than previous methods of just taking photos and will be able to use to go back and get full survey easily. LW It is a great advantage to download data in GIS format very quickly. WC. The Collector app is easy to use to take photos and comments. Offline data capture worked well. DM. Good and what we should have had years ago (always been asking for a GPS camera)! RH. Great to have Collector app automatically adjust to the device and platform without additional coding required. KP. Will not replace full survey but great as a first look coarse data capture. EB. Any questions at this time? Email: karen.pinkerton@sepa.org.uk Email: kirsty.jack@sepa.org.uk
Notas del editor
- Enabling more informed decisions for flood risk management This year’s devastating floods in Scotland saw rivers reach record levels. Karen Pinkerton was on the front line, running a new pilot for SEPA, using ArcGIS Collector to capture vital survey data. SEPA’s ability to capture the extent and impact of flood events, in near real time, has greatly improved the range, quality and confidence of its data which is anticipated to help improve future, sustainable flood risk planning. Join Karen to find out how the use of mobile GIS will feed invaluable insight into the National Flood Risk Assessment and Flood Risk Management strategies.
- Immediately after flood events SEPA collects and gathers as much information as possible to improve the products & services we offer and to help fulfil our duties under the FRM Act Observed flood event data underpins much of the work we do in SEPA: Calibration of flood forecasting models & national flood hazard maps High flow/rating improvements which in turn improve flow estimates for modelling work Planning application reviews Flood impact assessments Flood warning developments Not only does this allow SEPA to complete its Annual Operating Plan/ Characteristics priorities: of caring for communities, acting to combat climate change etc. Producing information and evidence that people use to make evidence also means that SEPA can fulfil its statutory obligations under the Flood Risk Management Act. Flood hazard and risk mapping (section 21) NFRA (section 9) – reporting significant events to European Commission FRM Strategies (section 27) Planning advice (section 72) Flood warning activities (section 74)
- What is observed flood data? Can be in lots of various formats informal and external Survey carried out by SEPA staff as resource allows or by contractors on ad-hoc basis Hydrometric data used to infer return periods Photos/Videos newspapers, incident reports flooding reports/FRA’s GIS files Point for depth and specific location info, photos Line for trashline and routes Polygon for extents and flood risk areas
- In order to better support this work Undertaking project To improve data capture, management & onwards use New tools to speed up capture, streamlined storage to make data easier to find & improved data sharing mechanisms
- Current Situation Currently collecting data on ad hoc basis with paper form when out in the field, or annotating maps unless we have full GPS survey kit Leads to Inconsistent data submission Various detail captured e.g. return period, photos, depths – used for different tasks so different teams require diff levels of detail – must ensure we consistently capture it Various formats of data submission e.g. hand written notes, spreadsheet, photo, GIS Reduced link between information and spatial environment – if we want a manually annoted map in GIS it takes time! Possible duplication of data - especially when it’s all listed in a table & you’re not checking spatial data as you record new flood events – was there anything in that area already?! Time lag between data capture and useable data – takes time to post process & already struggle for resource This can lead to a piecemeal dataset with late or missing data for some time after event Overall problem possibly performing these tasks on data that is: incomplete inaccurate outdated Realised that this could not continue for much longer and needed to look into available technology to solve the problem
- FEDCAP – A tool for Flood Event Data CAPture Chose to utilise ArcGIS Online and the ESRI Collector App Record point information (with photos/videos attached) Collect rough trashlines and attribute info to them The collector app is downloaded to a device 6 iPads suitable for purpose (apart from move point when wiping off rain) 20+ SEPA staff with log ins (1 iPad per Flood Risk area) Data gets synced via the cloud to the internet ArcGIS online server manages the data and hosts the platform Data gets downloaded to SEPA server Why did we choose it? Technically “free” as already held an enterprise license agreement Flexible as it works on multiple platforms and devices Online and offline data capture is possible accessible from anywhere with internet but secure area Log-ins provide privacy and security Less resource required to develop Simple to create a solution (as a non-developer)
- Created two simple featureclasses point for info, depths, photo and impacts; line for trashline and info Set up Domains for drop downs Bring into ArcMap to set up symbology ArcMap 10.2 shares to service via wizard Publish to SEPA portal on ArcGIS Online Ensure feature access is all on for full functionality Shared to the SEPA portal in the cloud Adjust sharing and editing permissions Add to a map, choose a basemap Generic basemaps of ESRI topographic and imagery Scope to use SEPA basemaps in future e.g. watercourse names Made the map editable, shared with Mobile App group Adjusted the form to hide some fields and make sense Started collecting data in the field Multiple maps for multiple study areas at high resolution (limit on download offline) Regional map for areas in between study areas (flooding outside work area) switch between offline and online Collect data Symbology brought across GPS automatically zooms to location Capture location, Add information, Add photo if required Similarly trashline, start streaming and start walking Can tap on screen if too dangerous to walk trashline Tap submit, Saved to cloud, Saved to device if offline Icon informs how many features been updated and need to sync Sync back up to cloud Happy to demonstrate in more detail afterwards if any wishes…
- Launched (swiftly) during Storm Desmond, 5th December 2015. As you may or may not know it was a rather wet winter. Record breaking in fact! 3 Named Storms and 4 “officially” unnamed events which caused severe flood impacts. The UK was in a warm and moist tropical air mass for most of the month mild temperatures but wet and windy conditions due to frequent deep depressions and frontal systems. The UK temperature was 4.1°C above the 1981-2010 average warmest December on record by 1°C (record spans to 1910). Max temperature of 17.2°C recorded in Scotland on the 16th December. Wettest December on record in Scotland December rainfall was 215% of the average and the wettest by a mile Over 200% of average rainfall for NE fell in in these months 50/400 river gauges in Scotland experienced record peak flows By the 8th Jan, Glenmuick raingauge already had recorded 263% of the total ave rainfall for January River Dee at Park was 1.34m higher on the 30th Dec than the previous max. Exceptionally high flows recorded all over the country Multiple flooding events, widespread over Scotland Over 1000 properties flooded across Scotland Storm Desmond (5-6th Dec) Unnamed (15th Dec) Storm Eva (24th Dec) Unnamed Low (26th Dec) Storm Frank (29-30th Dec) “Frank Junior” (5th Jan) “Day of the Don” (7th Jan)
- The map in the centre displays the public reports in this period from Report-A-Flood Desmond Over 100mm rain in western Scotland in 24hrs 600 evacuations in Hawick, Newcastleton, Aviemore, Langholm, numerous road closures (&gt;21) and disruption to traffic extensive flooding to properties (150 flooded in Southern Scotland, including a school) 79 FWs issued at the peak Issued first 2 severe FW since launch of Floodline service in 2011 (Hawick & Newcastleton) Frank 5.88m level at Park gauge on river Dee was 1.3m higher than previous highest recorded Catchments saturated 110mm rain in river Cree in 12 hours Widespread flooding (again) and evacuations Highest flow ever gauged at Ballathie on river Tay 101 FWs issued and 2 severe (Peebles and Dumfries) NE By 8th January parts of Ne had already experienced 3 times the average rainfall Widespread flooding in NE. Evacuations along the river don (all communities cut off) Severe warnings issued for Inverurie and Kintore Perth flood gates protected the city from the largest flow since defences completed in 2004 (30cm off top of banks) 370 residential properties flooded in Ballater alone 500year old castle now on the brink of collapse as 50+metres of bank were washed away The Campbus of May Bridge near Ballater (Photo credits: Peter Jolly)
- Data quality Georeferenced photographs Could “georeference” videos useful for flow estimations collector compressed quality. Capture on Ipad and attach High resolution camera including video Focused information captured for specific point More information available in the field Can possibly add more detail with additional layers or purpose built basemaps Too many fields to fill in for all features Recorded* 313 point features 620 photographs/videos 68 line features (trashlines/routes)
- Time saved Seconds to log in and load up although need connection, an issue for the north Takes a few minutes to capture Slightly longer in field than just camera possibly more info recorded Reduces survey time by half compared with GPS; significantly more with dumpy level Reduces processing time by days Easy to share data internally/externally no need for hardware symbology means quick interpretation
- Survey comparison One example shown in this image. Trashline captured with FEDCAP, point captured with Leica GPS &lt;10cm difference after re-projection Could be due to left/right hand of iPad Less detail as no elevation Unable to calibrate with various heights of SEPA
- Winter trial achieved a strong correlation between surveyed data and data captured via the solution a reduction in the time spent processing data an increase in the quantity of data received in the immediate aftermath of a flood an improvement in the quality and consistency of data received in the aftermath of a flood event positive response from SEPA and Local Authority staff Testimonies of staff response at the end. In terms of a proof of concept this was ideal. However, there are still areas we would like to improve if SEPA is to continue with this technology in the future
- Future development SEPA corporate adoption Feeds into Business requirements to IS for FEDCAP Strong Business case for ArcGIS Online Public body but certain protocols to follow for procurement security of data in the cloud in UK (working with ESRI) Simpler form as many fields were not applicable to task Better idea of function so can adapt form to various purposes Add more information to FEDCAP read only layers Use specific SEPA basemaps Need processes in place to confirm consistency when capturing data hands to hold with the side of trash line, Content of photo and when to capture core fields Improve post processing script to become fully automated Download Field population Photo name
- In summary the trial of the ESRI Collector App has Improved data quantity and quality, providing great business benefit Spatial aspect improves accuracy Quicker to capture, means more data More accurate data means better understanding TIMELINE e.g. trash line creates an extent, which goes into flood modelling, improves knowledge of flooding, improves flood warning, SAVES LIVES Enabled the access of more information in the field and in the office Had people assessing data in the office whilst colleagues in the field almost instant useable data Could organise further survey, assess impacts from photos, compare with historic floods, relate depths to locations Secure way to share with internal and external sources with quick interpretation Shared symbology means everyone is looking at the same thing No hardware required to share data securely Simple For non-developer to set up as no additional code required Simple for staff to use with minimal training Simple to modify to improve further and adapt for other purposes
- So I think you can agree that it has been a great trial Some other points are view are given. Thank you for listening. Are there any questions at this time?