Contour regions are easy. Right above the menu choice to draw contour lines is the choice to fill contour regions. So uncheck contour lines and check contour regions instead. You might also want to edit the contour ranges (third choice on the submenu where you check and uncheck drawing topo contours) to get more contrast in the color changes between different elevation levels.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of David Lowry via groups.io <huskyrunnr@...>
Sent: Tuesday, December 31, 2024 1:46 PM
To: [email protected]
Subject: Re: [yaac-users] Can’t get topo lines

Thank you! I’ll study how to implement contour regions. My Toughpad is 8 GB and Java is 23.0.1.
Best wishes for the new year!
David

Alas, I suspect that you're not being patient enough for topo lines to be rendered. I just tried it as well, and found that it took 336 seconds (!) on my older server computer to render over a view spanning 0.7x0.4 degrees. Apparently, the Graphics2D.drawPolyline() method in the Java runtime library has slowed down immensely, and that is what is used to draw all the squiggly contour lines. And, if you pan or zoom the map, all the incomplete work put into rendering for the previous map is tossed out and started over for the new map coverage.

Just out of curiosity, what version of the Java runtime are you using? And how much RAM does your computer have?

Of course, it doesn't help that the process of rendering vector contour lines from raster elevation data is computationally intensive as well, because that is also a contributor, though I have done everything I can to make that part of the algorithm faster (since that, at least, is in my code in YAAC rather than in Oracle's Java libraries or your operating system's graphics subsystem).

I would recommend that you switch to using topographic contour regions rather than lines; they are much faster to compute. In the meantime, I will look at ways to improve the performance of this code.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of David Lowry via groups.io <huskyrunnr@...>
Sent: Tuesday, December 31, 2024 12:56 PM
To: [email protected]
Subject: [yaac-users] Can’t get topo lines

I’m running YAAC 1.0-beta205 on Windows 10, but a previous version behaved the same. I can successfully download pre-imported OSM tiles. I can successfully download a small radius of the NASA topo data. I have correct lat/lon entered in the download dialog. When I toggle on view>layers>show topography>show topographic contour lines I get the citation to NASA in the lower right corner of the map but I can’t see any contour lines. I’m wondering what I’m missing. Thanks for any advice.
David

Greetings, all.

I was just checking over some code in YAAC (unfortunately, _after_ I posted build 205 last night), and discovered there is a bug in the OpenStreetMap tile download code when using an older version of YAAC. Even though the last few versions of YAAC will display the older snapshots of OSM imports I keep available for backwards compatibility, they still will only download the latest snapshot (regardless of what you select), which may not be compatible with the older versions of YAAC (which is why that check exists in the first place). There is a minor map file format change in build 205 that was used to create the map tiles I posted this morning from the December 23rd OSM snapshot, so if you download fresh tiles, you will need to be using build 205 to read the tile files successfully.

So please avoid doing map downloads until you upgrade.

Sorry about the inconvenience. I will have this fixed in the _next_ next build of YAAC, but that doesn't help anybody who's still at an older version. I will tweak the website so the September 8th snapshot will be current again.

Andrew, KA2DDO
author of YAAC

next beta build #205 of YAAC ("Yet Another APRS Client"), created 2024-Dec-30

downloadable from


changes and updates include:
1. update version of Apache compress library, including adding dependent
Apache IO library to fix breakage in OSM XML importer.
2. augment NWSMultiline code to support arbitrary colors (not just ones
looked up by the datatype code) and filled polygons so it can be used
to add arbitrary drawings to messages, especially new protocols from
plugins.
3. add new configuration flag options to support non-APRS-IS or RF
protocols (to support incompatible protocols provided by plugins).
4. add support for more foreign language spellings of units in OpenStreetMap
database snapshots.
5. more minor performance optimizations in OSM importers.
6. fix premature throwing of EOFExceptions for non-empty buffered
input streams.
7. fix spelling errors in Javadocs.
8. add another search directory for FreeBSD's way of installing the
distro's package of the JSSC library.
9. add new generic GUI methods to support user input dialogs with
plugin-provided extensions.
10. fix tactical query message processing so it doesn't annoy the user
asking if it's OK to send tactical names when the local YAAC station
doesn't have any tactical names.
11. improve ?LOCAL query to report if station hasn't heard any local
stations.
12. allow supplemental map layers to be conditionally omitted if the
current environment doesn't allow them for some reason.
13. expose OSM search-related classes in core YAAC so plugins can use
them for their own search code.
14. fix MultiRangeSpinnerNumberModel so a JSpinner-edited numeric value
won't break the UI if it was set to an out-of-range value (e.g.,
by changing the locale country of the computer to a jurisdiction
with a different band plan).
15. keep PopupTaggedNodeWindow from getting excessively large when there
is a large amount of information to display.
16. add a hook so plugins can add data to a PopupTaggedNodeWindow.
17. fix layouts of port configuration panels so fields don't collapse
to invisible sizes if the editor window is reduced in size.
18. fix bug in GUI startup on Mac OS X when using Java 8.
19. fix rendering bug for Locate Landmark table.
20. recognize more types of OpenStreetMap features, such as intermittent
or seasonal bodies of water, and more obscure amenity types.
21. change structure of OSM binary files to allow storing the segment
number of a single segment of an OSM Way.
22. refactor OSM importers so common code isn't duplicated between the
PBF and XML importer variants. fix bugs in XML importer and bring
it up-to-date with the PBF importer.
23. add optional support for extracting postal address information from
OpenStreetMap into a local database, using a plugin to provide the
database support. Also add support to extract the national border
Ways so they could potentially be used to update address points
with country codes.
24. created the Address DB plugin, which provides the above-mentioned
database support for extracting postal addresses from the OpenStreetMap
data and adds YAAC menu choices for searching said database.
25. add extension to Callsign DB plugin to support Address DB plugin.
26. normalize plugin Ant build.xml files to produce output .jar and .zip
files with the same names in the same directories as the Maven POM
files would do, and vice versa for Maven POM files that didn't
formerly completely do what the Ant scripts did.
27. fix Ant build.xml scripts for plugins with unit test code to be able
to run the unit tests from Ant.
28. fix exception in sounds plugin when new station is heard.
29. create new TAK plugin to enable YAAC to be a client of a Team
Awareness Kit (TAK) network.
30. fix documention directory location for telemetryalarm plugin,
update some out-of-date SMS gateway names.
31. include test libraries in source code distribution so Ant build
scripts can run the unit tests.

开云体育

According to chatGPT;

No, you'll have to look in the APRS Protocol Specification document for that.



________________________________________
From: [email protected] <[email protected]> on behalf of Jamie H via groups.io <wa7jh@...>
Sent: Monday, December 30, 2024 2:24 PM
To: [email protected]
Subject: [yaac-users] objects.pos

Andrew,

Do you have a legend that breaks out the object attributes in the object.pos file?

Like what does this all mean:
*111111z4738.27N/12243.53Wr
I feel like the *111111z is time and equals permanent.

What’s the rest mean if I got that right.


Jamie Hughes
WA7JH
(360) 340-8886

No, not really. What you did was stop _displaying_ stations and objects more than 100 kilometers away. But you didn't stop receiving and cataloging them in heap memory.

To overstuff YAAC like this, I presume you are using an APRS-IS connection. But it sounds like you connected to port 10152 (the unfiltered full-planet feed) rather than port 14580 (the filtered feed, where you need to specify the filter for the feed you want). Try using a 14580 feed with a r/lat/lon/100 filter expression (where lat and lon are the degrees North and East of the centerpoint you want to receive at) to get a reduced feed of just what you want.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Jamie H via groups.io <wa7jh@...>
Sent: Monday, December 30, 2024 2:16 PM
To: [email protected]
Subject: Re: [yaac-users] Heap Limit Reached

Thank you, Andrew,

I think I found the thing I was after as it was pretty elementary.

Under the Filter menu, I found that I was set to a Range of over 12,000 Km. set that to 100 and things got way better.

开云体育

The memory utilization bar can be turned on to show your actual heap utilization on the Preferences tab of the expert-mode Configuration dialog. This will show the used versus allocated heap quantities.

To actually override your default Java heap limit, specify the -Xmx option after the Java command but before the -jar option. For example, specify -Xmx4000m to allow up to 4000 MB of heap memory. YAAC will probably not operate with less than 64MB of heap.

I do not recommend specifying more than half of the physical RAM your computer has, as some will be needed for the operating system, desktop, and any other widgets and applications you might be running.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Jamie H via groups.io <wa7jh@...>
Sent: Saturday, December 28, 2024 11:44 PM
To: [email protected]
Subject: [yaac-users] Heap Limit Reached

I noticed that I was seeing the entire world and I was likely running out of memory.

Can someone remind me where to set the range limit?

Jamie Hughes
WA7JH
(360) 340-8886

开云体育

Regarding your two questions:

1. YAAC can import raster map images for a background. However, they are a pain to pin to the grid so the coordinate system is known properly, so I recommend using UTM-coordinate images with an associated .wld file to provide the pinning information.

Also, YAAC does support a lower-resolution form of the imported OpenStreetMap data that only does national boundaries. However, it's a bit sloppy because the boundary map lines aren't consistently identified, so YAAC has trouble finding all of them. To get the planet-level map file, make sure your download range for OSM map tiles covers more than 8 degrees (about 500 nautical miles or 800 kilometers) when you are downloading the tiles; YAAC will then assume you are going to be zoomed out enough to need the planet file and will download it too.

2. The graticule grid lines can be turned off by unchecking the menu choice View->Layers->Lat/Lon Graticule.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Tony via groups.io <73GUDDX@...>
Sent: Friday, December 27, 2024 12:54 AM
To: [email protected]
Subject: [yaac-users] World Map For HF APRS

All:

I'm new to YAAC and I was wondering if it's possible to import a simple World Map? My primary interest is HF APRS so there's no need for a detailed street map. Also wondering if it's possible to remove the grid lines.

Thanks, Tony

That is really peculiar. The FreeBSD JSSC package deliberately installs the jssc JAR file in a subdirectory of /usr/local/openjdk8 (not a Java-version-independent name like /usr/local/java). On the other hand, I can add that directory to the list of operating system directories being searched by YAAC, so it should work with newer Java versions (the openjdk8 directory would be created by the JSSC package even if openjdk8 itself isn't installed). I will fix this in the next build of YAAC.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Peter VE7PPE via groups.io <ve7ppe@...>
Sent: Friday, December 27, 2024 6:28 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC under FreeBSD 14.2

[Edited Message Follows]

Just posted to my VE7PPE blog: I added more detail and some corrections, then better formatted.

@Andrew - Here is the JSSC port page with the details on file locations:

I retested Openjdk8 --> 22 with FreeBSD JSSC, and only openjdk8 works with YAAC. For the rest, YAAC doesn't locate the JSSC and serial posts are not available. Suspecting that the Makefile requires Java-8, but haven't checked yet.

RE USB: Yes, FreeBSD assigns /dev/ttyU0, ttyU1, ....

Peter

This is probably because you were formerly configured to have _no_ icon for your YAAC beacon. YAAC always plots its own station with the symbol specified in the beacon configuration. Since the Microsat was specifying a symbol, but YAAC wasn't, you got the (nonexistent) symbol in your YAAC beacon configuration. I presume you had exactly the same callsign-SSID combination for the Microsat and YAAC's connection to the Microsat; if the callsign-SSID settings didn't match, you would have plotted both components (the Microsat fix and the YAAC fix with its symbol).

If some other component (such as a Microsat WX3in1) is generating the beacon, it's not a YAAC beacon.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Jon Adams via groups.io <n7uv.jon@...>
Sent: Thursday, December 26, 2024 11:33 AM
To: [email protected]
Subject: Re: [yaac-users] YAAC Mobile, symbol not showing on map

I found a work-around. I went into Beacon and configured a truck icon for my YAAC setup and now the pick-up truck icon shows up at the center of the screen.

The Microsat WX3in1 uses SmartBeaconing and sends out a position packet with the proper icon. I'm not sure why YAAC does not place that icon on the map, since in the Raw Packets window the location beacon sent by the WX3in1 shows that it has been digipeated, appears in the correct format, and in black font like the others that also are mapped properly on my display. However, the work-around doesn't explain for me why my position packet is not handled as the others received.
--
Cheers and 73 - Jon N7UV

Greetings.

This looks like the correct sequence with a couple of corrections:

1. JSSC is never bundled in the core JDK or JRE, and the version that is bundled inside YAAC only supports Linux, Microsoft Windows, and Mac OS X, so you will always need to install comms/java-simple-serial-connector on a FreeBSD system in addition to some version of the JDK or JRE. Do you know in what directory the libjssc-java.jar file is stored for the FreeBSD factory installation (or if it is named differently)? I'd like to make sure I'm searching the correct directories when looking for a factory install. Not sure why the newer Java versions wouldn't work with the FreeBSD stock version of JSSC.

8. The "-debug" option to YAAC is generally not needed unless you are debugging some internal feature of YAAC, and specifying it without a qualifier of what subsystems of YAAC you are debugging produces so much extra log output that the performance will be impaired.

Otherwise, this looks good.

Are USB serial devices on FreeBSD named ttyU0 instead of ttyUSB0?

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Peter VE7PPE via groups.io <ve7ppe@...>
Sent: Wednesday, December 25, 2024 6:32 PM
To: [email protected]
Subject: [yaac-users] YAAC under FreeBSD 14.2

I'm returning to FreeBSD after almost 10 years using Debian/Fedora for ham laptop. Its been an expected return with having to compile from source and/or search for obscure packages to get things to work.

YAAC is one of the first ham programs to get installed to my older laptop with a fresh install of FreeBSD 14.2 running a XFCE desktop with 1Tb SSD. Through trial and error, here are my steps to get YAAC communicating with both my GPS and TH-D72:


1. $ pkg install java/openjdk8 [tried openjdk22 --> 11, all fail to find jssc, aka no serial ports. Both YAAC & FreeBSD jssc lib not found >openjdk8]
2. $ pkg install comms/java-simple-serial-connector [>11yrs old, is from source for fork used by YAAC]
3. $ pkg install gpsd
4. $ vi /etc/rc.conf
* add: gpsd_enable="YES"
* add: gpsd_device="/dev/ttyU0" [check your usb port, I will build a udev style rule for the GPS under FreeBSD]
5. download YAAC to /home/user/Software-local/YAAC
6. unzip YAAC
7. cd YAAC
8. java -jar YAAC.jar -debug
9. config as needed

I will continue to test/tune this process with the newest JSSC fork and newer openjdk version. Will report back my findings.