| Author |
 Topic  |
|
|
JBlyth
Aquilotto
Australia
229 Posts |
 Posted - 24/09/2018 : 10:42:22
|
I have been able to use the Japanese Airspace file from OpenAip http://www.openaip.net/system/files/airspaces/openaip_airspace_japan_jp.aip_1537751786 without problem in the Android version of LK8000 6.1t, but it fails to load in the Windows CE PNA version, and the dialogue box loses the file name.
Is there still a limitation in Windows CE on file size, or do OpenAip files not work with that version?
Many thanks John
(currently towing and gliding at Takikawa Skypark, Hokkaiido, Japan) |
Edited by - JBlyth on 24/09/2018 13:24:25 |
|
|
AlphaLima
Moderator
Germany
1978 Posts |
Posted - 24/09/2018 : 18:11:44
|
Hmm,
strange the japan aip airspace has 1,7MB only and works fine on my devices. Are you 100% sure it is the same file on you CE device?
Can you send the runtime.log |
Edited by - AlphaLima on 24/09/2018 20:38:48 |
 |
|
|
JBlyth
Aquilotto
Australia
229 Posts |
Posted - 25/09/2018 : 10:34:05
|
Thanks AlphaLima,
Here is a "new" clean Runtime.log, which shows some strange things...
- The Windows and Windows/Font folders are not found - but they most definitely exist!
- The trouble with the Airspace AIP files seems to be the conversion from UTF-8. I tried saving it as an ANSI file, but that just crashes LK8000 when the AIP file is selected.
- I am using a Glider Guider running standard Windows Mobile
- I am using the LK8000 PNA executable.
What do you suggest I try next?
Many thanks
John
[000087341] ------------------------------------------------------------
[000087357] . [000087354] Starting LK8000 v6.1t Sep 10 2018 PNA
[000087498] . Free ram=58164 K storage=2101216 K
[000087508] . Host and Cpu informations not available
[000087646] ------ InstallSystem PROBLEM: cannot locate the Windows folder, got string:<>
[000087655] ------ InstallSystem attempting to use default "\Windows" but no warranty!
[000087664] . Special RegKey for fonts not found on this PNA, using standard folder.
[000087673] ------ PROBLEM: cannot locate the Fonts folder, got string:<>
[000087685] ------ Attempting to use directory <\Windows> as a fallback
[000087694] . InstallSystem: Copy/Check Fonts from <\Storage Card\LK8000\_System> to <\Windows>
[000088001] . Language load file: <\Storage Card\LK8000\_Language\ENG_MSG.TXT>
[000089175] Init Bluetooth
[000089217] Bluetooth Is OK
[000089237] Bluetooth : Device Count = 2
[000089295] . InitLKScreen: 272x480
[000096625] . Loading polar file <\Storage Card\LK8000\_Polars\ASW28-18.PLR>
[000096786] . Terrain Open RasterMapRaw <\Storage Card\LK8000\_Maps\Hokkaido_500_18.DEM>
[000096811] ... Terrain size is 2847460
[000096821] ... Available memory is 56968kB
[000096835] ... Terrain : use heap memory
[000097189] . Waypoint file 1 format: SeeYou
[000097653] . LOADED 314 WAYPOINTS + 19 virtuals
[000097674] . LoadRecentList: loaded 3 recent waypoints
[000097715] . open AirfieldFile <WAYNOTES.TXT>
[000097788] . HomeWaypoint set to <Pinneshiri> wpnum=213
[000097858] . Reading OpenAir airspace file
[000109524] . Now we have 581 airspaces
[000109536] ... No airspace file 2
[000109802] . Settings for 581 of 581 airspaces loaded from file <\Storage Card\LK8000\_Airspaces\AspConfig.LK>
[000110000] ------ WARN Topology, shape bounds reading failed, fallback to mode0
[000110968] ------ WARN Topology, shape bounds reading failed, fallback to mode0
[000115708] . LKMAPS Advanced Topology file found
[000115755] . FLARMNET database, found 0 IDs
[000115769] . Local IDFLARM, found 1 IDs
[000115835] . ComCheck Init
[000115852] . Device A is <Generic> Port=COM7
[000115861] . ComPort 1 Initialize <COM7> speed=19200 bit=8
[000115871] . ComPort 1 <COM7> is now open
[000115881] . ComPort 1 Init <COM7> end OK
[000115893] . ComPort 1 ReadThread : started
[000115906] . Device B is <Generic> Port=COM4
[000115915] . ComPort 2 Initialize <COM4> speed=19200 bit=8
[000115925] . ComPort 2 <COM4> is now open
[000115988] . ComPort 2 Init <COM4> end OK
[000115997] . Device C is DISABLED.
[000116012] . ComPort 2 ReadThread : started
[000116022] . Device D is DISABLED.
[000116031] . Device E is DISABLED.
[000116039] . Device F is DISABLED.
[000117700] . GCE_STARTUP_REAL
[000117955] . ProgramStarted=NormalOp h11:41:35 (NO FIX)
[000117991] . Free ram=45764 K storage=2101216 K
[000118279] . LoadTask : <\Storage Card\LK8000\_Tasks\Default.lkt>
[000122556] . LK Battery Manager V1 started, current charge=93%
[000123689] . First GPS DATE: 2008-9-6 h11:41:35 (NO FIX)
[000129300] . GPS NMEA source changed to port 1 h8:59:57 (NO FIX)
[000129758] . Change GPS DATE: 2008-9-9 h8:59:57 (NO FIX)
[000139561] . Change GPS DATE: 2018-9-25 h11:42:20 (NO FIX)
[000152535] . Settings for 581 airspaces saved to file <\Storage Card\LK8000\_Airspaces\AspConfig.LK>
[000152566] . CloseLKAirspace
[000152575] . Reading OpenAIP airspace file
[000152771] .. Not able to allocate memory to convert from UTF8.
[000152792] ... Failed to parse airspace file 1: \Storage Card\LK8000\_Airspaces\openaip_japan0918.aip
[000152803] ... No airspace file 2
[000152910] . Settings for 0 of 0 airspaces loaded from file <\Storage Card\LK8000\_Airspaces\AspConfig.LK>
[000181994] . Entering shutdown h11:43:03 (UTC 02:43)
[000183591] . Save history to <\Storage Card\LK8000\_Configuration\History.txt>
[000183628] . SaveRecentList: saved 3 recent waypoints
[000183710] . SaveTask : saving <\Storage Card\LK8000\_Tasks\Default.lkt>
[000184007] . Stop COM devices
[000184050] . ComPort 1 ReadThread : terminated
[000186166] . ComPort 1 closed Ok.
[000186543] . ComPort 2 ReadThread : terminated
[000189690] . ComPort 2 closed Ok.
[000189709] Restore Bluetooth power state
[000189722] . ComPort 0: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[000189731] . ComPort 1: status=1 Rx=12025 Tx=0 ErrRx=0 ErrTx=0
[000189738] . ComPort 2: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[000189746] . ComPort 3: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[000189754] . ComPort 4: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[000189762] . ComPort 5: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[000189773] . Finished shutdown h11:43:08 (UTC 02:43)
[000190025] . WndMain::OnDestroy
|
|
|
|
JBlyth
Aquilotto
Australia
229 Posts |
Posted - 30/09/2018 : 07:38:19
|
Hi AlphaLima,
I have been chatting to Alberto about the AIP file for Japan (and his AIP to OpenAir converter). It seems there are a couple of errors in the Japan Airspace AIP file with upper limits not stated in a couple of areas, and some other irregularities.....
This seems to make the PNA version of LK8000 fail to load the required AIP file as the log above shows. Interestingly, the Android version of LK8000 seems to be able to skip these errors and to parse the AIP data effectively.
Cheers
John |
|
|
|
AlphaLima
Moderator
Germany
1978 Posts |
Posted - 30/09/2018 : 10:22:21
|
Thanks John,
I saw this upper limit problem as well. This need to be fixed but I doubt thats realy causing your problem.
The XML UTF8 conversion need a lot of RAM for the huge XML lines in the japan airspce. I suspect the elder CE Devices are very limited in RAM. Eventually some "Carrige Returns/Line Feeds" in the very huge <POLYGON> rows can solve that problem.
The SAVANNAKHET TMA and XIENGKHOUANG TMA for example, each have over 200000 characters in one row. |
Edited by - AlphaLima on 01/10/2018 09:09:56 |
|
|
|
brunotl
Pterodattilo
France
1095 Posts |
Posted - 01/10/2018 : 10:10:26
|
this probleme wil be fixed after v7 release
job are done but i wait v7 relase for publish. |
|
|
|
Alus
Pulcino
Netherlands
30 Posts |
Posted - 27/05/2019 : 15:54:55
|
quote:
Originally posted by JBlyth
Hi AlphaLima,
I have been chatting to Alberto about the AIP file for Japan (and his AIP to OpenAir converter). It seems there are a couple of errors in the Japan Airspace AIP file with upper limits not stated in a couple of areas, and some other irregularities.....
This seems to make the PNA version of LK8000 fail to load the required AIP file as the log above shows. Interestingly, the Android version of LK8000 seems to be able to skip these errors and to parse the AIP data effectively.
Cheers
John
Yes, I remember when John contacted me, some month ago, about this problem.
Then, at that time, we solved converting properly (some fix was necessary in the converter) the openAIP Japan file to OpenAir (using OpenAir circle and arc definitions instead to listing all points) which resulted in a much smaller file encoded in ANSI loadable also by older devices.
Anyway I'm trying to simplify further the things: I'm working on a webpage with almost all openAIP data (only "hotspots" points are missing at the moment) already and automatically converted.
You have just to download the files for the countries you need.
I'm updating that page, as soon as openAIP releases new data, possibly every week.
I hope it can be useful.
Al. |
Edited by - Alus on 16/06/2019 10:19:03 |
|
|
|
BravoLima
Aquilotto
Netherlands
276 Posts |
Posted - 27/05/2019 : 16:48:35
|
Hi Alberto,
I'm sorry to say but there are some errors in the files for the Netherlands
KMZ file: all airspaces are rectangular and some are missing (see txt file).
CUP file: in SeeYou you get a single waypoint at the intersection of the Greenwich meridian and the Equator.
I think this is caused by all the text that is added to the file between the first line and the waypoint data.
TXT file: part of the Dutch airspace is not shown in SeeYou and Google Earth (Nieuw Milligen TMA D and TMZ D). However it seems that the airspace data is in the file. |
Edited by - BravoLima on 27/05/2019 16:55:15 |
|
|
|
Alus
Pulcino
Netherlands
30 Posts |
Posted - 27/05/2019 : 21:35:53
|
quote:
Originally posted by BravoLima
Hi Alberto,
I'm sorry to say but there are some errors in the files for the Netherlands
Yes you are right, something went wrong there.
Anyway thanks for reporting!
I will let you know when it will be fixed.
Al. |
Edited by - Alus on 28/05/2019 17:40:05 |
|
|
|
Alus
Pulcino
Netherlands
30 Posts |
Posted - 28/05/2019 : 17:45:01
|
quote:
Originally posted by BravoLima
KMZ file: all airspaces are rectangular and some are missing (see txt file).
CUP file: in SeeYou you get a single waypoint at the intersection of the Greenwich meridian and the Equator.
I think this is caused by all the text that is added to the file between the first line and the waypoint data.
TXT file: part of the Dutch airspace is not shown in SeeYou and Google Earth (Nieuw Milligen TMA D and TMZ D). However it seems that the airspace data is in the file.
KMZ file: bug found ad hopefully fixed, let me know if now is OK.
CUP file: removed all the text before the waypoints.
TXT file: To me it seems that all the Dutch airspace from the openAIP is being translated. |
Edited by - Alus on 16/06/2019 10:18:25 |
|
|
|
BravoLima
Aquilotto
Netherlands
276 Posts |
Posted - 16/06/2019 : 12:12:31
|
The KMZ file seems to be alright now.
However, the source files for the airspace (ASP.txt) and the waypoints (NAV+WPT.cup) are outdated and/or incomplete.
The information in these files does not always correspond to the current Dutch AIP.
These errors are therefore also copied in the KMZ file.
For example:
- A large part of the airspace in the south of the Netherlands is missing.
- The runways of the airports all have a north-south direction. |
Edited by - BravoLima on 16/06/2019 12:15:30 |
|
|
|
Alus
Pulcino
Netherlands
30 Posts |
Posted - 17/06/2019 : 20:10:16
|
Hi BravoLima, thanks for your feedback and for coming back to this topic.
All the contents in that page are from openAIP, I'm just converting them.
Apparently for the Netherlands, on openAIP, there isn't a wide community keeping it up to date.
If you find something that differ from openAIP, then there is a problem in the conversion, and, in this case, I will be happy to fix it.
|
|
|
|
BravoLima
Aquilotto
Netherlands
276 Posts |
Posted - 18/06/2019 : 10:07:28
|
quote:
Originally posted by Alus
Apparently for the Netherlands, on openAIP, there isn't a wide community keeping it up to date.
The GliderPilotShop https://www.gliderpilotshop.com/databases is the unofficial source for Dutch airspace data. The Soaring Web also used this until 2018, but apparently is no longer being updated.
I am not really a fan of OpenAip because it is often unclear where the information was obtained.
Often the required information is collected and compiled by enthusiastic well-meaning people. After a while, this information is then considered to be the only correct information, simply because no other sources are available. In the beginning the information can certainly still be useful, but the problem is keeping it up-to-date.
It would therefore be nice if an Aeronautical Information Service (AIS) or another official recognized organization would make the airspace information available (preferably in one or more of the usual formats). |
Edited by - BravoLima on 10/08/2019 21:11:51 |
|
|
|
AlphaLima
Moderator
Germany
1978 Posts |
Posted - 11/08/2019 : 12:44:13
|
@BL.: Totally agree, but you are adressing the wrong people here.
;-) AL |
|
|
| |
Topic |
|
Using OpenAip Airspace with Windows CE LK8000?