PPP Forum

I have bought new SDK 'TTNCF6' and I have changed it in the application... but I continue having he himself problem: it does not work with negative values (South/ West coordinates)

Example code:

Resp = TTN.SowCoordinatesOnMap(dLon, dLat).ToString()
Resp = TTN.NavigateToCoordinates(dLon, dLat).ToString()

If 'dLon' or 'dLat' < 0 then ... Resp = -4 (Error)

Which is the solution?

Hi JoseRamon,

we gave it a try and can confirm your problems.

Errorcode abouve -100 are produced directly by the SDK.
So we gave the thing a try with a native SDK C++ Application (to ensure our wrapper is not involved).

The result is the same as you told.
Further we did a "double test" which means - geodcode of an address - and than use this result to ensure that we use valid data.

We sent an email to TomTom about this bug!!
###########

Manfred, I have sent him a mail.

Thanks.

And you should have got a repyl with the attached SDK test application.

Manfred

Hi,

we got a confirmation of this bug from TomTom.
Since the only way to come over this problem is to produce (and handle) communication files "by hand" we have no solution at the moment and have to wait for a TomTom solution.

Here the TomTom statement about this bug:

This is a known issue and we are planning to fix this. There is a workaround possible, only this workaround doesn’t work with the SDK library, you will have to create the communication files yourself. The only thing you need to do is to add 4294967295 to your negative coordinate. This will make it a positive value, but when NAVIGATOR processes this value it will store it in a signed integer and this will convert it into a negative value again.

Regards

Manfred

I have proven the solution to add the value proposed by TomTom to the negative coordinates... and it does not work !

1) It only works when the coordinate is 0º W, that is to say, the problem is not in the format of shipment of the SDK, it is within the TomTom6.

Test code:
If dLat < 0 Then
  dLat = 42949.67295 + dLat
EndIf

If dLon < 0 Then
  dLon = 42949.67295 + dLon
EndIf
Resp = TTN.SowCoordinatesOnMap(dLon, dLat).ToString()

If 'dLon' = West ... Resp = -4 (Error)
If 'dLat' = South ... Resp = -4 (Error)

2) Adding the value to all the coordinates (positive and negative) it works with positive (North/East), but not with the negative coordinates (South/West).

Test code:
dLat = 42949.67295 + dLat
dLon = 42949.67295 + dLon
Resp = TTN.SowCoordinatesOnMap(dLon, dLat).ToString()

If 'dLon' = West ... Resp = -4 (Error)
If 'dLat' = South ... Resp = -4 (Error)

Thanks

Hi Jose Ramon,

you may have overseen one thing in the statement of TomTom!!

There is a workaround possible, only this workaround doesn’t work with the SDK library, you will have to create the communication files yourself

This means that the SDK does not allow such value - or tries to correct it.
Otherwise it would have been easy for us to build a version of TTNCF wich checks for negative values and does the correction if needed.

The suggested workaround would mean NOT TO THE SDK (for coordinate related functions)-
instead you must write your own file communication layer which produces and handles the
communication with the navigator by itself.

And yes you are right - the files produced by the SDK are correct - the problem is within the navigator,
Or in other words - the bug is within the Navigator.

So what would it mean to build a workaround?
First a lot of work to handle the files.
Second - a solution which will (maybe) no longer work after TomTom fixes the bug in the Navigator.exe.
---either they change the SDK to produce those "workaround values"
---or they ship a corrected Navigator.exe (then the workaround will fail with such a version).

So or the moment people livinig / running their apps - in areas with negative values in Lat / Lon have either the possibility to build a temporary workaround - or they have to wait for a solution from TomTom.

I would invite anyone to contact TomTom via the known partners email or via http://www.tomtom.com/pro

As the past showed  the more customers argue the faster TomTom builds a solution.

Regards

Manfred

Hi All,

This seems to be related (or perhaps I'm doing something wrong):

TTN 6 / TTNCF 6
When getting the current position from the SDK/wrapper, it will only return positive values. So even it you're west of the meridian, you'll get a positive longitude. No need adding that subsequent geodecoding will return odd results.

If anyone has other results, please let me know, maybe I'm doing something wrong. I used this to test it:

int res = TTN.GetCurrentPosition(ref tE, ref tPos);
...
MessageBox.Show(tPos.dLongitude.ToString());
...

Leon

 

---

http://www.autokosten.info - PDA Trip Recorder

Hi Leon,

although we do not really knwo the problem in the TTN interface we think about something like TTN6 uses an "unsigned" datatype.

This would explain your Results also.

I beg you to forward your information to TomTom - maybe this helps to prevent us from a "partial Bug fix"

Regards

Manfred

Hi Manfred,

Thanks for your reply. I sent TomTom pro a mail about this this morning,
I'll keep you posted about it!

Best regards,
Leon

 

---

http://www.autokosten.info - PDA Trip Recorder

Manfred, FYI I got this response:

We are aware of a bug in all functions where coordinates are passed as a parameter. Negative coordinates are not accepted here. The other way around isn't a known issue thus far and unfortunately we have no immediate way to test this. I'll investigate and let you know.

----

It's logical I guess that he can't test this very well without actually going to a position with a negative longitude. Perhaps someone here on this forum who reads this can check this out:

If you live in an area with a negative longitude (or latitude for that matter), please test the GetCurrentPosition function, and see if it actually returns negative values where it should.

At least it isn't a TTNCF bug ;)

Best regards,
Leon

---

http://www.autokosten.info - PDA Trip Recorder

Hi Leon,

great response - so this means that TomTom did not know about this problem!!
And (thanks to your note) they know it by now - and hopefully fix it with the other bug.

Anyhow - I'm astonished that a company like TomTom has no "GPS Simulator" to test their apps and devices (the build hardware also).
I think they have such devices- but have no time to use them

Regards

Manfred

Hi Leon,

In order to test of the SDK with negative coordinates, the GPS is not necessary:

1) Plans a route advanced = Go: A to B
2) To activate way “DEMO”

Best regards,
José Ramón

@José Ramón: many thanks! I didn't think it would actually simulate GPS input as well... it does :)

@Manfred: apparently they even have their own built in simulator, but they just don't know it :)

---

http://www.autokosten.info - PDA Trip Recorder

We have tested the GetCurrentPosition function from Alabama (United States) and received a positive latitude and a negative longitude.

The ShowCoordinatesOnMap function does not work properly here. If we put in a negative longitude, it produces an error. If we change the number to a positive, it puts us about one state over from where we are. The longitude it puts us at does not change when we pass different longitude values into the function.

Any help would be appreciated,

Dubfault