r_x

Assuming you are using a recent version of MOBAC: I use JDK 21 for MOBAC development. Java 17 also works, but as most Java 17 based distributions are end-of-life in Oct 2026 I wouldn't start using it anymore unless required by a program. Java 25 has not been intensively tested with MOBAC.

The web site mentions an API key that needs to be present. But I have not found the documentation how to obtain such a key.

For editing GPX files I mostly use https://sourceforge.net/projects/prune-gps/ especially when the GPX track was recorded from actual GPS positions as this tool has great features for filtering/thinning GPX track waypoints. In MOBAC the GPX editor is so lightweight because it's main purpose was to provide a source for downloading map tiles around a GPX track. I never needed more features so it was never implemented. I will check your code if it makes sense to include it into MOBAC and how much work...

section about source code formatting added

instructions added how to get org.beanshell:bsh:3.0.0-SNAPSHOT

Thanks nono303, yes I think it makes sense to perform the http engine change also for the trunk/main branch. The main reason from my perspective is not the speed, but the left over connections which also affect the server side. That is unnecessary resource consumtion... The problem is that the old HttpURLConnection is exposed to map sources. Especially the BSH map sources are a complicated case I have to find a workaround for. At the moment my dev system is out of order so merging your patch will...

Thanks nono303, yes I think it makes sense to perform the http engine change also for the trunk/main branch. The problem is that the old HttpURLConnection is exposed to map sources. Especially the BSH map sources are a complicated case I have to find a workaround for. At the moment my dev system is out of order so merging your patch will delay a bit.

fixed some deprecation warnings