DW Map Generation with TomTom - Unable to create geoid context

Software Version
NVIDIA DRIVE™ Software 10.0 (Linux)

SDK Manager Version
1.7.1.8928

Host Machine Version
native Ubuntu 18.04

Hello,

after my recent struggles to define the input XMLs manually, I’ve decided to work with the the map converters advertised by the documentation. Unfortunately those have been throwing interesting errors, even when using the exemplary commands from the readme; with a TomTom developer API key provided:

~$ maptool_tomtom_to_dw_maps --key=*REMOVED* --minLon=-122.3 --maxLon=-122.2 --minLat=37.4 --maxLat=37.5 --output_file=dwMapCache.xml
[13-04-2022 08:24:11] Platform: Detected Generic x86 Platform
[13-04-2022 08:24:11] TimeSource: monotonic epoch time offset is 1649826048395130
[13-04-2022 08:24:11] Platform: number of GPU devices detected 1
[13-04-2022 08:24:11] Platform: currently selected GPU device discrete ID 0
[13-04-2022 08:24:11] SDK: Resources mounted from /usr/local/driveworks-2.2/data/
[13-04-2022 08:24:11] TimeSource: monotonic epoch time offset is 1649826048395130
[13-04-2022 08:24:11] Initialize DriveWorks SDK v2.2.3136
[13-04-2022 08:24:11] Release build with GNU 7.4.0 from heads/buildbrain-branch-0-gca7b4b26e65
[Geoid] Unable to open geoid file
Maptool: [INFO]: Loading map...
MapToolTomTomToDWMaps: [ERROR]: Unexpected exception: 
DW_FAILURE: MapToolTomTomToDWMaps: Unable to create geoid context
[13-04-2022 08:24:11] Releasing Driveworks SDK Context

This error is raised under many different parameter permutations, even when no API key is provided at all, as long as there are sufficiently many other parameter configurations given.

Best Regards,
Fabian

Dear @fabian.hofmann1,
We are checking internally on this issue and update you.

Dear @fabian.hofmann1,
Could you confirm if you have data/tools/maps/geoids/WW15MGH.DAC on system? If so, please let us know the directory path from which you are running the tool.

Dear @SivaRamaKrishnaNV ,
the file exists in /usr/local/driveworks/data/tools/maps/geoids/. As described in the documentation for the converter, I included the folder with the binary files for the converters in the binary search path ( export PATH="/usr/local/driveworks/tools/maps:$PATH" ). I’m running the tools from my home directory.

Dear @fabian.hofmann1,
Does that mean, you copied the tool to $HOME directory and running?

Dear @SivaRamaKrishnaNV ,
I didn’t copy the tool to $HOME directory, but merely added the path to the binary file to my path. Meaning the file is still located in /usr/local/driveworks/tools/maps/.

Dear @fabian.hofmann1,
This issue seems to be related to relative paths of files in the executable. Could you please check running in the same directory instead of $HOME and let us know if it works? Note that the permission of directory should be set to R+W.

Dear @SivaRamaKrishnaNV,
thank you! I simply decided now to execute it directly within in the directory the binary was located in. After a few of permission errors, I decided to execute the converter as the superuser and the error/exception changed.

/usr/local/driveworks/tools/maps$ sudo ./maptool_tomtom_to_dw_maps --key=*REMOVED* --minLon=-122.3 --maxLon=-122.2 --minLat=37.4 --maxLat=37.5 --output_file=dwMapCache.xml
[14-04-2022 16:47:03] Platform: Detected Generic x86 Platform
[14-04-2022 16:47:03] TimeSource: monotonic epoch time offset is 1649947357483943
[14-04-2022 16:47:03] Platform: number of GPU devices detected 1
[14-04-2022 16:47:03] Platform: currently selected GPU device discrete ID 0
[14-04-2022 16:47:03] SDK: Resources mounted from /usr/local/driveworks-2.2/data/
[14-04-2022 16:47:03] TimeSource: monotonic epoch time offset is 1649947357483943
[14-04-2022 16:47:03] Initialize DriveWorks SDK v2.2.3136
[14-04-2022 16:47:03] Release build with GNU 7.4.0 from heads/buildbrain-branch-0-gca7b4b26e65
Maptool: [INFO]: Loading map...
Exception thrown
MapToolTomTomToDWMaps: [ERROR]: Unexpected exception: 
DW_FAILURE: MapToolTomTomToDWMaps: Unable to successfully fetch data from the server
[14-04-2022 16:47:04] Releasing Driveworks SDK Context

Dear @fabian.hofmann1,
Please confirm if you notice the same error when you run the tool in user mode and change the directory permission to have R/W permission. I do not have set up to verify on my end and hence seeking clarification from you for internal verification.

Dear @SivaRamaKrishnaNV ,
terrible sorry for the late reply; but yes the same error appears after changing the permissions for the entire driveworks folder to allow everyone to read/write/execute.

/usr/local/driveworks/tools/maps$ ./maptool_tomtom_to_dw_maps --key=*REMOVED* --minLon=-122.3 --maxLon=-122.2 --minLat=37.4 --maxLat=37.5 --output_file=dwMapCache.xml
[25-04-2022 06:52:14] Platform: Detected Generic x86 Platform
[25-04-2022 06:52:14] TimeSource: monotonic epoch time offset is 1650859278529218
[25-04-2022 06:52:14] Platform: number of GPU devices detected 1
[25-04-2022 06:52:14] Platform: currently selected GPU device discrete ID 0
[25-04-2022 06:52:14] SDK: Resources mounted from /usr/local/driveworks-2.2/data/
[25-04-2022 06:52:14] TimeSource: monotonic epoch time offset is 1650859278529218
[25-04-2022 06:52:14] Initialize DriveWorks SDK v2.2.3136
[25-04-2022 06:52:14] Release build with GNU 7.4.0 from heads/buildbrain-branch-0-gca7b4b26e65
Maptool: [INFO]: Loading map...
Exception thrown
MapToolTomTomToDWMaps: [ERROR]: Unexpected exception: 
DW_FAILURE: MapToolTomTomToDWMaps: Unable to successfully fetch data from the server
[25-04-2022 06:52:15] Releasing Driveworks SDK Context

Could it be an error with the API key or TomTom’s services?

Quick update: Now it is fully our fault it seems and not any config error or something else; I am speaking to TomTom right now to acquire the right kind of API key, because the one used is for the wrong API. Will update the issue once I have more info.

1 Like