this post was submitted on 22 Dec 2023
12 points (100.0% liked)

Te Upoko o te Ika a Māui / Wellington

407 readers
1 users here now

Kia ora and welcome to !wellington, a place to share and discuss anything about Te Upoko o te Ika a Māui / Wellington in general.

Rules:

Banner image by Rob Suisted

founded 1 year ago
MODERATORS
Dave
d3Xt3r
12
Chance of acute water shortage in Wellington increases (www.rnz.co.nz)
submitted 11 months ago by happy_piwakawaka to c/wellington
15 comments fedilink hide all child comments
 

The chance of Wellington experiencing an acute water shortage this summer has increased, while emergency water tanks sell out around the region.

New modelling from Wellington Water shows there is now a 33 percent chance of the region seeing an acute water shortage rather than a 24 percent chance that had been previously recorded.

Under that type of shortage, level 4 water restrictions would be brought into place which would ban all outdoor water use and reduce indoor water use by up to 50 percent.

you are viewing a single comment's thread
view the rest of the comments
[–] happy_piwakawaka 2 points 11 months ago (1 children)

Yeah I've actually been impressed with the response to my 2 FIXiT reports - I need to remember to use it more often.

We had an ever worsening leak round my way and I just had assumed it'd been reported. After maybe a month I ended up reporting it through the app and it was fixed the next week.

Would be nice if there was a way to view existing reports / jobs. I did a quick search and found this for water jobs: https://www.wellingtonwater.co.nz/resources/maps/job-status-map/ but it doesn't show anything for me (might be a mobile / Firefox thing)

[–] Dave 1 points 11 months ago (1 children)

The map loads for me on Firefox for Android, just with coloured areas.

[–] happy_piwakawaka 2 points 11 months ago (1 children)

Yeah on Chrome you can actually see individual jobs at specific addresses

[–] Dave 3 points 11 months ago

I tried it on PC Firefox and it still doesn't work. Looks like it's blocking the cross-domain requests as they haven't set their CORS headers right.