Author Topic: Redbridge, Code 11, parked on pay by phone in wrong location code - but could not correct  (Read 2345 times)

0 Members and 1771 Guests are viewing this topic.

Did you try and copy what you did?

I did but was after the contolled hours. Ill go again today before the controlled hours ends.
Ill update this chat afterwards

Hello,

So today I went on foot to the same spot within the controlled hours. See attached pictures in the drop box link below:

https://www.dropbox.com/t/99F1SDnpxG5VYVKt

Something weird happened. despite various people here and having read elsewhere that the free parking for an hour is only permissable once a day, this wasn't the case at all.

Today, upon standing on same spot, the geo code again suggested the incorrect location 6081228 at 1724 hours. To replicate the situation, I chose this option, with vehicle AK66HAN.

Then "upon realising" the error, at 1725 hours, with the same vehicle, I typed in the correct location code 6081226 and it allowed me to proceed with no issues and  allowed me to park for free. This was bizarre, as I had two concurrent parkin sessions active within minutes a part. I then tried a different car - a random car saved on my profile a van - it also allowed me to part free of charge. In fact I had four sessions active in the same location code, all free 6081226.

This is interesting, as its allowing me to do something that 1. very different when I tried last week when I received the PCN. But intrerestingly, it allowed me to four cars at the same spot for free. Which I understood was against Redbridge policy.

There are few screen shot grabs  of the booking  during active and a few after when the reciepts were genereated.

I hope this helps to strengthen our arguments that during their reorganisation of the codes, there were some technical glitches!

So you got the same multiple sessions as I did.

All you can do is say what you think you did and enclose the error screen.

You were also there for less than an hour.

Draft something and I'll tweak it.

+1.

IMO, do not lead with the error was their app's because it wasn't, it was yours.

Harsh it might sound, but if it prevents you thinking of adjudication along these lines then good. If a motorist chooses to rely upon an app for location details and doesn't comply with their obligation, which is to look for a traffic sign, then this is their choice.

You would say that on *** you tried to use the RingGo app to book a parking session at location ****6 but it would not accept this. Instead, you received an error message, see attached. Although a previous issue shouldn't have made any difference, you would add that when you first parked at the location you did manage to book a session, but at location number *****8. But when you noticed your error you couldn't amend this booking, not that it should have affected RingGo because for all the system knew you had parked at ***8 and then moved to ***6 very soon after.

Would be my take.

IMO, your focus on the app giving the wrong location is actually distracting and not material: as in my suggestion above, a driver should be allowed to park at A, book a session then move to B, book another and then to C. By putting your argument in a slightly different way you'll test their view of the 'free' parking facility. I have read their website again and read as a whole, I'm not certain what it means: https://www.redbridge.gov.uk/parking/more-parking/on-street-and-season-parking-charges/



Ok let me draft something tonight and I will send here for improvements and tweaks

I disagree on avoiding the geolocation especially as I think Redbridge has 'simplified' its location by having certain codes for bigger areas.

Their system geo-located a neighbouring code but this was checked and OP was then led to believe the correct one couldn't be used for a reason we can't replicate.

No charge was payable for the time there and no loss to the council.

I disagree.

IMO, a driver's obligations are clear as has been found in numerous adjudication decisions. You can weave this in to reps, but IMO do not lead or focus. The key issue is not whether the app located you incorrectly because this doesn't bear upon the facts as far as you know. You tried to book a session for ***6 but were prevented by the system. This is the issue IMO, not speculating about, let alone concluding, why.