# L5 closure A303 Hampshire

**URL:** https://www.waze.com/discuss/t/l5-closure-a303-hampshire/118859
**Category:** UK Editor Requests
**Created:** [November 5, 2017, 8:09am UTC](https://www.waze.com/discuss/t/l5-closure-a303-hampshire/118859 "2017-11-05T08:09:35Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![DG567](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@DG567](https://www.waze.com/discuss/u/DG567)
#### Post date: [November 5, 2017, 8:09am UTC](https://www.waze.com/discuss/t/l5-closure-a303-hampshire/118859/1 "2017-11-05T08:09:35Z")

</div>

If you get to this in time…

The A303 e/bound is closed at Andover for bridge maintenance all weekend until 6am Monday morning. I think the Highways England feed has closed the wrong section. At the moment [these segments](https://www.waze.com/en-GB/editor/?env=row&lon=-1.48929&lat=51.20228&s=102602071&zoom=2&segments=121887872,180880548,121886463,261546936,299218583,121886314,121886317,121886318) are all closed.

I _think_ the (incorrectly) closed segments to the west are actually open - they were due to be closed on a different weekend - but I haven’t seen it with my own eyes so I’m loathed to say it’s wrong but I can see URs saying it’s open.

Thanks  
David

---

<div class="post-metadata">

### Author: ![woodvale](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/w/FF5252/32.png) [@woodvale](https://www.waze.com/discuss/u/woodvale)
#### Post date: [November 5, 2017, 10:00am UTC](https://www.waze.com/discuss/t/l5-closure-a303-hampshire/118859/2 "2017-11-05T10:00:40Z")

</div>

Hi David

I’ve removed the closures that I helped Closure Monitor add last night and closed the segments you’ve linked to. I saw one UR that clearly had a track through the CM-closed section, so I’m content that it was closed in error.

Thanks for shouting!

---

<div class="post-metadata">

### Author: ![DG567](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/0099FF/32.png) [@DG567](https://www.waze.com/discuss/u/DG567)
#### Post date: [November 5, 2017, 10:24am UTC](https://www.waze.com/discuss/t/l5-closure-a303-hampshire/118859/3 "2017-11-05T10:24:11Z")

</div>

Thanks John.  
Just looked at the app - there’s a tiny segment that’s still closed to the west, at a small triangular junction. Can’t send a link sorry, not at PC.

---

<div class="post-metadata">

### Author: ![iainhouse](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/0099FF/32.png) [@iainhouse](https://www.waze.com/discuss/u/iainhouse)
#### Post date: [November 5, 2017, 1:16pm UTC](https://www.waze.com/discuss/t/l5-closure-a303-hampshire/118859/4 "2017-11-05T13:16:17Z")

</div>

> [@DG567](#):
>
> Thanks John.  
> Just looked at the app - there’s a tiny segment that’s still closed to the west, at a small triangular junction. Can’t send a link sorry, not at PC.

Closure removed :mrgreen:

---

<div class="post-metadata">

### Author: ![woodvale](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/w/FF5252/32.png) [@woodvale](https://www.waze.com/discuss/u/woodvale)
#### Post date: [November 5, 2017, 2:48pm UTC](https://www.waze.com/discuss/t/l5-closure-a303-hampshire/118859/5 "2017-11-05T14:48:09Z")

</div>

Sorry about that. As I’d helped Closure Monitor add the closure, I used a spare minute before going out to add the correct and remove the wrong, thinking I’d have enough time. Thought I’d got all the segments involved, but clearly not.

Sent from my Galaxy S7 using Tapatalk
