🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: uk.rec.driving
Article #2010

Re: Parking again - paying by mobile

#2010
From: Ian Jackson
Date: Mon, 28 Nov 2011 13:51
46 lines
3562 bytes
In message <9jhbtaFjsoU2@mid.individual.net>, JNugent 
<jenningsltd@fastmail.fm> writes
>On 26/11/2011 21:47, Ian Jackson wrote:
>> In message <faqdnRkurYT9JE3TnZ2dnUVZ7oKdnZ2d@brightview.co.uk>, Nick Finnigan
>> <nix@genie.co.uk> writes
>>> On 25/11/2011 13:25, Zimmy wrote:
>>>>
>>>> Then I got to thinking; the Parking Warden must look up the car on his
>>>> portable computer as there is no ticket to stick on the windscreen when you
>>>> pay by mobile. Therefore, there's no real reason why said portable computer
>>>> can't also alert said Parking Warden to mobile-paid parking times about to
>>>> expire, to ensure timely ticketing before the felon returns.
>>>
>>> Anything pre-pay could contact a central location and then alert the PW
>>> when a ticket is about to expire - might have a partial reg in some cases.
>>> Or the PW could note times in his PC as he proceeds around the 
>>>parking areas.
>>>
>>>> Maybe paying by mobile is not quite so handy after all or am I just 
>>>>cynic?
>>>
>>> ... or not sufficiently paranoid.
>>
>> Of course, the system could work as follows:
>> 1. 'Phone in' at start of parking period.
>> 2. 'Phone in' again at end of parking period.
>> 3. Get charged for time spent parking.
>> Or is this just TOOOOO easy?
>
>Many people would forget the second call and cost themselves money. Not 
>bad from the rip-off merch...er... council's POV.

But this is essentially the same as the 'lost ticket' situation in a 
pay-on-foot carpark, where typically there is charge for a full day's 
stay (usually around �25).

There could be various simple procedures for damage limitation. For 
example, what if your clock-in included an estimated duration (so it 
would be exactly the same as at present). However, you wouldn't be 
penalised if you stayed after it expired. Instead, at the expiry time, 
you would be sent an automatic reminder that you hadn't clocked out, and 
you would be prompted to do so (if you wanted to). Repeated reminders 
could be sent every hour. Maybe still not 100% perfect, but not far from 
it.
-- 
Ian
Technical Details
Message-ID: <hiVheVBYH50OFwUF@g3ohx.demon.co.uk>
Path: arc1-ca.pugleaf.net!lh20ni30393pbb.0!nntp.google.com!news1.google.com!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
References: <jao4p0$6mr$1@dont-email.me> <jao518$92p$1@dont-email.me> <faqdnRkurYT9JE3TnZ2dnUVZ7oKdnZ2d@brightview.co.uk> <J$R7ZAEL6V0OFwwF@g3ohx.demon.co.uk> <9jhbtaFjsoU2@mid.individual.net>

Show Full Headers
Complete Article Headers
X-Google-Thread: 104960,9ac68a4393c6d469
X-Google-NewGroupId: yes
X-Google-Thread: 109765,bdc2d969d663682b
X-Google-NewGroupId: yes
X-Google-Attributes: gid73efed67cd,gida91e4e313e,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Received: by 10.68.15.105 with SMTP id w9mr25860244pbc.7.1322488355648;
        Mon, 28 Nov 2011 05:52:35 -0800 (PST)
Path: arc1-ca.pugleaf.net!lh20ni30393pbb.0!nntp.google.com!news1.google.com!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Ian Jackson <ianREMOVETHISjackson@g3ohx.demon.co.uk>
Newsgroups: uk.rec.driving,ed.general
Subject: Re: Parking again - paying by mobile
Date: Mon, 28 Nov 2011 13:51:20 +0000
Organization: A noiseless patient Spider
Lines: 46
Message-ID: <hiVheVBYH50OFwUF@g3ohx.demon.co.uk>
References: <jao4p0$6mr$1@dont-email.me> <jao518$92p$1@dont-email.me>
 <faqdnRkurYT9JE3TnZ2dnUVZ7oKdnZ2d@brightview.co.uk>
 <J$R7ZAEL6V0OFwwF@g3ohx.demon.co.uk> <9jhbtaFjsoU2@mid.individual.net>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org; posting-host="1Z/M1oM6JVqBnMi2uYI0kA";
 logging-data="5264"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+/qMq8PQLBPUCc6tbyOeMn7hMiYijqLLc="
User-Agent: Turnpike/6.07-S (<7UWqWe23KPzneMCj$tHoewDpOn>)
Cancel-Lock: sha1:vZaP40JRE0fkFsAg1H/V1UYdsKk=
Content-Type: text/plain;charset=iso-8859-1;format=flowed
Content-Transfer-Encoding: 8bit