15-03-2012 12:50 PM
I have created this new Topic to discuss, specifically please, the ageing of GPSr (or perhaps in other terms Why & How do Legacy Units arise and What Now?) I have quoted the chat elsewhere into this new topic. Just give me a moment to do this and then this topic is "Go" .
15-03-2012 02:28 PM
15-03-2012 02:32 PM
Wow - I thought I had done that; I'll have to find where I did create the comments since it took me a while to copy & paste them across and identify in separate colours to distinguish thyem. - hang in there for an hour or so if you don't mind. Have an urgent matter on hand and difficult to assign priority right at this moment.
15-03-2012 02:54 PM - edited 15-03-2012 09:58 PM
In a prior Topic discussion on Legacy Units arose. A suggestion from that chat has been added to the MSR suggestion list.
Here we go with the OT items over there:
Giangi opened with:
In my opinion the best improvement ever will be incorporating the web application into TomTom Home!
Tomtom HOME is going to be irrelevant, as soon as all the NAV2 devices will be legacy. Different units use different maps. As soon as you don't have the latest map on your unit, but like a 3 years old, it would be pointless to report an error that was fixed already...maybe
And why would NAV2 devices be legacy? Is there a new GPS technology that requires new hardware?
The new one is NAV3. More and more of the old units (One) are becoming legacy. The x30 models are mid-term. But it is a hijack again Sorry Shorty [Shorty - no offence taken; this is the situation experienced]
As long as there's no other positioning system I believe none of these should be legacy. If they suit their purpose, where's the problem?
+1 right here. I can't see any problem at all.
Let say that if the map on the device is newer it can then be used with user's agreement!
I was talking about TTH just because that's the pgm I use owning a 750. The same can be applied to MyTomTom too!
Btw: as soon as there will not be any more map updates for the "legacy" devices I will abandon TomTom because I do not want any of the current devices...
me too. The good thing about the "legacy" devices is that the user can access the file system. This sometimes helps a lot, and when Tomtom decides to "close" the system, this will be the moment I'll move to a competitor
NOW let's hope I've pressed the right buttons
Edit: fixed a spelling :: Shorty
15-03-2012 05:54 PM
15-03-2012 09:59 PM
I like that "link" idea and think I should include that in our MSR suggestions list
19-03-2012 03:14 AM
I've had a re-think, not on the subject and the chat on Unit ageing, but this topic should be more correctly placed in Discussions. Ditte will move for us later today.
22-03-2012 03:33 PM
Also it is better to create one complete database, instead of thousands (or more) individual. For that purpose we have MSR already to share the data with TomTom only at this point (users of older unitsd with each other also).
Why do you want thousands dbs? MSR is a web application, TTH (not sure about MyTomTom) is a web abblication; you "just" have to implement the client-side in TTH while keeping the server-side on TomTom's servers as it is now!
You will have only one repository on TomTom side but you will gain access to local data as entered directly on your own device!
Not being able to edit/look inside your local map corrections done on the device is the major "problem" of correcting map on device!
You do not have any feedback, for example, if a change has been incorported into the map!
If a change has not been incorporated you still see it on the device (tested by myself on my Go 750) just because on map upgrade the local repository (which is not saved inside the map folder!) is preserved! But if a correction is still not "accepted" is far better to re-do it so to force the central repository to receive it again!
Wouldn't it better to have an interface easy to use and WYSIWYG on MSR as you have on your own device?
On the device you have an immediate feedback of the correction while on MSR you have nothing!