I don't know how many SAS.Planet users own a Garmin device with support of BirdsEye JNX format (Colorado, Dakota, Oregon, Montana, GPSMAP62, EDGE800 and few others).
If there would be an interest, I have clear idea how to
integrate JNX map generation into SAS.Planet.
My idea is based on this post:
http://gpsunderground.com/forum/garmin- ... #post65410Very shortly: MOBAT2JNX now supports KML file, generated by SAS.Planet using area selection -> Export -> KML (for Google Earth). The KML file with absolute paths to cache tiles can be used as parameter for MOBAT2JNX. This way not only rectangular selection, but also polygonal selection is supported.
An example MOBAT2JNX call (
http://gpsunderground.com/forum/garmin- ... #post65605):
mobat2jnx selection.kml -tilelist -sas
The switch -sas is used only to understand the relevant part of the <href>...</href> lines within the KML:
<href>D:\SAS.Planet\cache_gmt\Dolomiti-4land.it\
z14\5808\8730.png</href>
JNX file generation could be integrated into SAS.Planet for example by one of these 2 possible ways
a) To allow to configure an optional command, which could be executed automatically just after the KML file generation
b) To implement JNX file generation as explicit option in SAS.Planet, either in the Stick tab, or in the Export tab. In this case tilelist would be generated and external MOBAT2JNX command would be executed. The generated tilelist could have the format of KML (for Google Earth), but it would be sufficient if it would contain only a pure list of absolute paths to cache tiles.
I mean it has no sense to fully implement JNX file generation into SAS.Planet, because the JNX format is not so simple. There are specialized external tools available and there are people, who are fully involved into creating of these tools. It's much easier to use an external tool, than to try to implement the JNX geenratiom within SAS.Planet.