Unable to load OSM map
Status: Beta
Brought to you by:
apavlin
Menu
▾
▴
JDK info:
openjdk 25.0.1 2025-10-21
OpenJDK Runtime Environment (build 25.0.1+8-27)
OpenJDK 64-Bit Server VM (build 25.0.1+8-27, mixed mode, sharing)
What database server are you using? This error indicates that YAAC is not configured to successfully connect to the appropriate SQL database server you have chosen to use with the addressdb plugin. Note that YAAC is not a database; through the addressdb plugin, YAAC is a client of some database server you have chosen to use for which you have provided configuration data in the YAAC expert-mode Configuration dialog on the Postal DB tab.
If you don't have a database server, then you can't use the addressdb plugin. If you aren't planning to set up a database to hold the multiple gigabytes of postal address data, then you should delete the addressdb.jar file from your YAAC/plugins directory.
I will be fixing YAAC in the next build to properly handle the case of OSM importing when the addressdb plugin is installed but not configured.
Hi. Thanks for the quick response. I did add a few plugins thinking merely doing so might gain me access to callsign look up info, etc... I didn't realize plugins required additional set up. I especially didn't know not doing so would break simingly unrelated functionality. Without an obvious way to remove the plugins, I deleted the files and restarted. I was then able to load the OSM raw data. Glad to hear you will be fixing this. Shall I add another ticket for inability to remove plugins via the GUI?
Last edit: t fredrickson 2025-10-28
It shouldn't have broken functionality, and the addressdb plugin is specifically for the functionality of extracting postal address data from the OpenStreetMap dataset in a form that can be used later. Most plugins do require some configuration, just as base YAAC does. For example the ADS-B decoder plugin needs to know how to connect to your ADS-B receiver. The newest versions of YAAC now inform you if a plugin needs configuration; unfortunately, the addressdb plugin pre-dates that capability and didn't use it to report its configuration need, but it will now.
Unfortunately, Java makes it very difficult to disconnect from code in JAR files once you start using them; as long as one data object came from a class in the JAR file, you still need it, and some plugins take advantage of other plugins (for example, if you have the repeater finder plugin installed, the smallscreen plugin can display an alternate version of the repeater finder data). So, I will not be accepting a ticket for hot-unplugging a plugin; not all of them even work correctly when hot-plugging them in, and need YAAC restarted to get full functionality from the plugin.