Sorry guys but I am looking for one of the TT Staff who is prepared to follow up on a ticket that was raised (16xxxx-xxxxxx), went back and forth between myself and UK Support and was then closed so that I can no longer add anything to it despite the fact that the UK C.S. agent's last comment on 15.08.16 was a request to bear with the company whilst they investigated the issue further.
This is totally unacceptable and makes the camera data untrustworthy at least.
Mod edit : Please do not post any personal information on forum.
0
Comments
Sorry about the inconvenience and delayed reply..
I have sent a heads up to the customer service so someone will get in touch with you.
Regards
Vikram
Thankfully I have the well known PGPSW POI's on my android phone due to TT no longer allowing such files to be added and that in itself is a massive negative attitude for your company to adopt.
This situation is further complicated in that my SGS4 phone with Go mapping has a static camera at the start point and another at the end point, but it is not recognised as a Specs zone whereas the opposite track is.
It's a total nonsense that the programming is sending spurious data and is not getting resolved effectively.
As posted earlier, my phone has the PGPSW cameras on it and as a verifier for them, I know they are accurate, particularly accurate in the UK, so I am better off to run them if I feel the need.
It's just so frustrating trying to get someone to accept that the data is incorrect.
MapShare Reporter has the zone marked however the northbound start camera appears within the same icon as the southbound end camera, so could it be that the northbound start is actually on the wrong track and therefore won't be picked up in any event? On Saturday 12.05 I put an "Other" comment onto the MSR programme in the hope that this will be looked at.
It cannot be just my 6100 at fault as my Android SGS7 also fails to show the zone, so two updates on two different systems with the same problem - it has to be down to the programming surely?
Any suggestions would of course be appreciated or anyone else who uses this stretch of road and can confirm/negate the northbound Specs zone.
I have provided all the information and data that you would need in order to investigate this issue as it is across 3 platforms, but clearly this is not enough.
Unless there is a programmer who gets to read these issues, then I really don't see that you will ever put this right.
What a come-down from what TT used to be in the early years of the 700 series and similar.