Bug in Calculate Radar Plot from Pcap file

[AlessiaDS]

When trying to plot using data from a pcap file of a CAT048 it doesn't execute it due to an error in the data source, it doesn't calculate the latitude and the longitude even if in the management of data sources they are inserted. I attach the link for the file used.
https://drive.google.com/file/d/15y8Hn5GcWrU6SccNVlBbQJ8HXdvC-EYZ/view?usp=sharing

here, range and azimuth are available

here, the radar has been configured with the correct anchor coordinates

[hpuhr]

Got it, thank you for the write-up. Will take a look and get back to you shortly.

[AlessiaDS]

Thank you for your time.

[hpuhr]

OK, so I figured out a few things - there is (as you correctly identified) a bug in this COMPASS version. But there is a workaround that should help you:

• Use your current database, open the "Configure Data Sources" dialog
• Select the "Unknown (35/1)" data source
• Click in the Altitude text field, enter "0" again
• Click "Done", close the application (which saves the configuration)
• Open the application again, create a new database, import the PCAP file again
• This should result in the latitude/longitude being calculated correctly (always for this data source)

Please let me know if this works for you (in the mean time, before we do a bugfix-release in a few weeks).

Behind the scenes, there are 2 actual issues:

1. The Radar data source being ignored for lat/lon calculations if the altitude is "never set" (which is still displayed as 0 in the dialog even if never set, but not saved in the background configuration data if no value entered at all)
2. If no data was imported before, the "Process" -> "Calculate Radar Plot Positions" task fails with the following assert:
   • "COMPASS-v0.7.5_hf2_newos.AppImage: /app/workspace/compass/src/projection/projectionmanager.cpp:199: unsigned int ProjectionManager::calculateRadarPlotPositions(std::__cxx11::string, std::shared_ptr, NullableVector&, NullableVector&): Assertion `projection.radarCoordinateSystemsAdded()' failed."

Both will be fixed in the next bug-fix release.

Please let us know if there are any other issues - in a new report or using [email protected]