Friday, February 27, 2009

A busy night for some...


Fire crews from around the region responded to a significant fire at Woodleigh Lodge just south of Sanson at around15:00 yesterday. All up, some 31 callsigns responded to the event with a further 6 machines moved to provide cover. PRFO Brent Fanning responded for the Council. At around 17:45 thoughts were turning to tea - a quick call to the Emergency Management Duty Officer resulted in the Red Cross being called in to assist.

For some it has been an overnight vigil with the last of them leaving around 07:30 this morning.

EMDO Ross Brannigan (Rosco's first week as EMDO and he gets a goodie) went to check things out and get a few photos later in the piece... I think we need lessons on how to take photos with your phone!

At the same time, I responded as alternative EMDO to a smoke complaint in Newbury Line. Turned out to be a stubble burn that was being well looked after. A lot of people in Palmerston North would have seen the pall of smoke though.

Tuesday, February 24, 2009

The Gospel according to Jeff


For about a year now Jeff Watson and his team have been posting river level forecasts to the Horizons Regional Council website. This is a project undertaken on behalf of the Emergency Management Office and I'm happy to say has received generally supportive feedback from the community. Recently however a few agencies have been complaining that our long-term forecasting is inaccurate and their decision-making has been affected by this. Well, that's where the discussions have become quite interesting in Council and have ranged from stopping posting the forecasts to the website to wrapping it in 10 pages of legal disclaimer and description. I'm pleased that we'll be taking a middle of the line approach in the next few weeks to provide a short disclaimer and brief description of the limitations of the forecasts. It's worth pointing out here that there are only a handful of organisations around the world prepared to put river level forecasts out into the public arena, and we are the only regional council in New Zealand to move it out of the back room.

So, brace yourself for what will probably be my lengthiest post since I created the blog…

Firstly, the forecasting models draw on a number of data inputs, the forecast rainfall, the actual rainfall and river levels, and then run these numbers through a virtual catchment to try and predict how high the river might get at a few critical spots (well that sounds fairly straight forward). Let's pick on the Whanganui model to try and explain some of the limitations of this forecasting.

Forecast rainfall… we automatically receive the forecast rainfall from the MetService every eight hours. We get this once global forecast models have run to provide input into their local climate models and it literally takes this long to happen. We have recently found out that MetService actually run seven different models and then pick the best to base their forecasts and warnings on (that makes sense). The river level forecast however draws on the same model every time, regardless of whether its being used by the MetService to develop their forecasts - we're seeing how we can pick up the best three forecasts that are chosen by the forecasters instead of the same model every time. Next (and this is where we get a bit 'Dr Who') there is the space-time-quantity continuum… does the rain that was forecast, up to 48 hours out, arrive where they said, when they said and in the intensities they said? You only need to be out by one degree of track to move the rain from one sub-catchment to the next and the model will be wrong. Equally, the forecast quantity presents a challenge - any more or any less than was forecast and the model will be wrong. In fact, the quantity might be right but it all arrives in two hours instead of 12 hours (you guessed it, the model will be wrong). Finally, if the front stalls or moves faster than expected the model will be wrong. So… you might as well poke a sticky wet finger in your ear and look at the sky (which is what some of the team did before we got the model).

Next, the actual rainfall… the Whanganui catchment is a large, hilly, sparcely populated and difficult to access part of the region. The number of sites we actually collect data from is very limited, to the point where it can be raining in a couple of sub-catchments and we won't even know. We are looking to improve the model by drawing on rain gauges outside of the catchment in Taranaki and Waikato and then interpolating the information across the catchments as well as adding an additional two rainfall sites into the catchment later this year. Of course if any of the equipment fails then this will make the model particularly vulnerable. The team keep on top of this as much as possible but sometimes our equipment gets stolen, hit by lightning, eaten by pests, filled with spiders or even used as target practice. Of course, of the rain that actually falls, some will evaporate, some will be absorbed and some will make it to the river and all three of these will be different for every event depending on what has happened before the rain arrived. The flood forecasting model attempts to deal with these effects.

So now we're interested in the water that actually makes it to the river… assuming it's arrived when, where and in the quantities forecast and wasn't evaporated or absorbed! The Whanganui catchment is made up of multiple sub-catchments, it may be raining in some but not others and each of these sub-catchments are feeding the river to varying degrees. Finally, the river height and flow will be recorded at a river level site (and possibly other parameters for other activities in Council). Now that we have a hard number on the river level it should be fairly straight forward to forecast how high the river will get in the town - right… we know the average travel time on the river and we know how much water is coming… but don't forget that more sub-catchments will be feeding the river before it gets to the town so we need to add these in too. Another little catch is this thing called a rating curve. To calculate the volume of water in the river, a cross-section of the river is taken and co-related to the river level site so… if the river is say 6m deep, the volume of water passing over the cross-section is say 1000 cubic metres/second (or cumecs). But what if the profile of the cross-section has changed (and Mother Nature does that to us), what if the river deepened at that spot and the volume was actually 2000 cumecs - the height could be the same on the gauge… this could have serious consequences down stream.

The Pipiriki site is a significant site for the Whanganui River. The site provides plenty of lead time for the town and is the basis for the Horizons and Wanganui District Council joint Flood Action Plan. There are two sites down river of this that enable us to confirm margins of error in the model. During possible events, staff in our emergency operations centre manually evaluate the data when it gets to this point so if the model is under-forecasting we should pick it up in plenty of time. If the model is over-forecasting… better safe than sorry.

When all said and done, forecasting how deep a complicated river system like the Whanganui will get in a few days time is a little more complicated than your average punter might think - but that won't stop us trying. No other agency is in a position to tell the local communities this level of information. Since the model has been running, we've had a couple of small events go through. Even though the model is designed to be more accurate in larger events, these small events have allowed us to re-calibrate the model (this should be in place soon). You can also see that improvements in forecasting data are being sought along with actual data from new and neighbouring sites. The main thing to remember is that the further out the forecast, the less accurate it will be (we can accurately tell you what actually happened though). While work continues to improve existing models, new models are being produced… we're expecting the Manawatu forecasting model to get plenty of hits when its up and running later this year.

Wednesday, February 18, 2009

Spill response in Wanganui


Earlier this week, a few of the Council's oil spill response staff responded to a reported diesel spill on the Whanganui River. Its believed the spill came from an unmanned Korean fishing vessel that has been tied up in the port for several years. Given that the 'rainbow sheen' has persisted for several days, we are also suspicious that the product was oil rather than diesel but sampling results have been inconclusive.

The picture attached shows Regional On-Scene Commander Ian Lowe assessing the effectiveness of 'agitation' on breaking up the residue. This was particularly effective and assisted natures natural processes of breaking down the oil. While use of some local boats was considered (including Coastguard) we opted to use the Council's boat. This did not delay the response in any way.

Staff are continuing to monitor the situation and anyone observing oil on the river is encouraged to contact the Council's pollution hotline on 0508-800-800.

Thursday, February 12, 2009

CDEM Compentency Framework

MCDEM have asked me to provide a link to some recent work... (brownie points for me!!).

You are able to access the MCDEM CDEM Competency Framework Online Survey from 2 February until 27 March 2009. Your full participation is encouraged, as it is essential if we are to obtain a complete picture of the CDEM sector in New Zealand and the roles and functions within it. As an added incentive, when you complete the survey you will go into the draw to win a prize package.

Access the survey here.

Read more about the CDEM Competency Framework here.

Tuesday, February 10, 2009

Flash flooding


Well, this afternoon has seen a bit of action in the old town... A heavy downpour early this afternoon followed by consistent heavy rain resulted in storm water systems overloading. While most parts of the city coped, some areas experienced a bit of surface flooding.

Most motorists coped with the unexpected obstacles but there were a few hoons 4WDing in the puddles.

Looking at the Fire Service jobs it looks like there was a bit of action in Wanganui too. The irony is... I picked up a bunch of fire restriction signs this afternoon and we go to a restricted fire season tomorrow night.

Tuesday, February 3, 2009

MCDEM information system

Well, it seems things are moving ahead with the MCDEM Emergency Management Information System (EMIS). Sean Hodges and I (along with a bunch of EM managers and REMAs) attended a MCDEM consultation meeting today to consider sector needs for an emergency information management system.

Although my initial impressions are that it's a fairly ambitious exercise, MCDEM seem to have engaged a more than capable team to see it through. One of the big things for me was that for this to be a successful national system, the CDEM Groups will need to 'buy-in' to make it work. I'm really pleased that MCDEM have had a change of heart about the importance of a system that can be used sector-wide.

Much of today's discussion was around process path and information needs. Being clear about what MCDEM needs to see to make strategic decisions informs what the Groups (and others) need to contribute to the EMIS. As we know, Groups address operational issues at a Local Controller level and strategic issues at the Group Controller level. So, the Group's operational information informs the Group's response strategy. Group strategies inform the National response strategy. We talked about rolling up the information so the next layer up is not overwhelmed by the amount of information potentially available.

The work that we've started with our Group's GIS web portal will continue as it will make any national system more robust. Once we've seen the MCDEM Request for Proposal, we will have a better idea on specifications that need to be considered in the Group project.

All in all, things are moving but don't expect immediate results. I'd estimate we're at least 16 months away from a product.