[Kflog-user] A bug or a PICNIC problem?

Sun Apr 26 22:12:20 CEST 2009

Thank you / Danke Axel!

Yes, you are right about the "Q" rather than "D" for the Danger areas. Sorry, that is my PICNIC mistake!

To show the issues I have with the airspace rendering, here parts of the airspace to illustrate:

* <start of example>
*Johannesburg TMA
AC CTR
AN JHB TMA 123.7 / 124.5
AL 7600 FT
AH FL110
DP 25:48:20 S 028:45:45 E
DP 25:45:00 S 029:12:30 E
DP 25:55:20 S 029:12:30 E
DP 26:06:10 S 028:58:33 E
V X=26:08:31 S 028:14:15 E
DB 26:06:10 S 028:58:33 E, 26:09:30 S 027:30:50 E *CLOCKWISE RADIUS=40
DP 26:09:30 S 027:30:50 E
DP 26:01:50 S 027:36:20 E
V X=26:08:31 S 028:14:15 E
DB 26:01:50 S 027:36:20 E, 25:34:00 S 028:09:00 E *CLOCKWISE RADIUS=35
DP 25:34:00 S 028:09:00 E
DP 25:38:30 S 028:06:00 E
DP 25:49:30 S 028:06:00 E
*V D=-                                  *these three lines must make a curve...
*V X=25:49:29 S 028:13:49 * ...centred here to follow Waterkloof airspace below... - remove * to see the effect.
*DB 25:49:30 S 028:06:00 E, 25:56:30 S 028:11:40 E *ANTI-CLOCKWISE RADIUS=7
DP 25:56:30 S 028:11:40 E
DP 26:00:00 S 028:23:45 E
DP 25:48:20 S 028:45:45 E

* Pelindaba
AC P
AN FAP 64 PELINDABA
AL SFC
AH 6500 FT
DP 25:46:51.01 S 027:53:55.72 E
DP 25:47:00.68 S 027:57:30.55 E
DP 25:48:51.97 S 027:57:27.45 E
DP 25:49:26.63 S 027:55:32.35 E
DP 25:48:27.01 S 027:53:44.47 E
DP 25:46:51.01 S 027:53:55.72 E

*Lanseria TMA "A"
AC C
AN LANSERIA TMA "A"
AL 6500 FT
AH 7600 FT
V X=26:00:37 S 027:50:22.33 E
DB 26:11:49.13 S 027:53:25.58 E, 25:52:35.65 S 027:41:12.7 E *CLOCKWISE RADIUS=11.5
DP 25:47:27.51 S 027:48:27.02 E
DP 25:46:29.70 S 027:57:06.78 E
DP 25:50:47.94 S 028:00:51.75 E
DP 25:57:53.81 S 028:00:56.41 E
DP 26:07:08.51 S 027:57:17.50 E
DP 26:11:49.13 S 027:53:25.58 E

*Lanseria TMA "B"
AC C
AN LANSERIA TMA "B"
AL 7000 FT
AH 7600 FT
DP 25:47:27.51 S 027:48:27.02 E
DP 25:45:39.11 S 027:50:59.54 E
DP 25:45:06.31 S 027:55:54.22 E
DP 25:46:29.70 S 027:57:06.78 E
DP 25:47:27.51 S 027:48:27.02 E

* Waterkloof TMA
AC C
AN WATERKLOOF TMA
AL 7600 FT
AH FL195
DP 25:48:20 S 028:45:45 E
DP 26:00:00 S 028:23:45 E
DP 25:56:30 S 028:11:40 E
V X=25:49:29 S 028:13:49 E
DB 25:56:30 S 028:11:40 E, 25:49:30 S 028:06:00 E *CLOCKWISE RADIUS=7nm
DP 25:49:30 S 028:06:00 E
DP 25:38:30 S 028:06:00 E
DP 25:34:00 S 028:09:00 E
V X=26:09:25.62 S 028:13:51.69 E
DB 25:34:00 S 028:09:00 E, 25:48:20 S 028:45:45 E *CLOCKWISE RADIUS=35nm

* <end of example>

I hope this is sufficient?  If not, I can post the entire thing as I have it defined so far...

Rgds / Mit freundlichem Gruss,

Hendrik.

PS: If you are wondering why I do THIS airspace, I fly on The Dark Side as well (that is, I fly powered aircraft (out of Grand Central - FAGC) too).

________________________________________
From: Axel Pauli [Axel.Pauli at gmx.net]
Sent: 26 April 2009 21:05
To: Hendrik Stheeman (Britehouse); kflog-user at kflog.org
Subject: Re: [Kflog-user] A bug or a PICNIC problem?

Hi Hendrik,

I'm Axel the maintainer of Cumulus the KFLog fork for soaring navigation. I cannot speak for KFLog directly but one thing of you is wrong. An airspace Danger is coded as letter Q and not D. The following items are used for OpenAir airspace coding:

*  AIRSPACE related record types:
*  ==============================
*
* AC class    ;    class = Airspace Class, see below:
*     R restricted
*     Q danger
*     P prohibited
*     A Class A
*     B Class B
*     C Class C
*     D Class D
*     GP glider prohibited
*     CTR CTR
*     W Wave Window

KFLog uses the following mapping according to the source code:

("A", "AirA");
("B", "AirB");
("C", "AirC");
("D", "AirD");
("E", "AirElow");
("F", "AirF");
("GP", "Restricted");
("R", "Restricted");
("P", "Prohibited");
("TRA", "Restricted");
("Q", "Danger");
("CTR", "ControlC");
("TMZ", "Tmz");
("W", "AirEhigh");
("GSEC", "SuSector");
   |        +- KFLog type
   +- OpenAir Type

The mapping is coded in the source and not configureable from the outside. Maybe there is a bug in the mapping, that must be investigated by us. In Germany we have no prohibited airspaces. Can you post here on the list your openair file definition?

Also a Hendrik is the current maintainer of KFLog. I hope he will read your message too and can give you more detailed ansers to KFLog.

greetings Axel

-------- Original-Nachricht --------
Datum: Sun, 26 Apr 2009 20:31:47 +0200
Von: "Hendrik Stheeman (Britehouse)" <Hendrik.Stheeman at za.didata.com>
An: "kflog-user at kflog.org" <kflog-user at kflog.org>
Betreff: [Kflog-user] A bug or a PICNIC problem?

Good day Folks,

I am not sure whether the below issues are PICNIC problems, the result of the way I installed KFlog or bugs - any advice or pointers to "how-to's" would be appreciated! (I have installed the snapshot of 24 April, although it shows KFlog 2.2.0 beta / OpenSuse 11.1 & KDE 3.5.10)

1.) The "tip of the day" containing "...that we would be pleased if you let us know about..." with hyperlink in "let us know" leads to a page with hosting service standard message starting with "Herzlich Willkommen auf www.heiner-lamprecht.eu! Dies ist die Standard-Index-Seite Ihres Webs. Sie können sie..." Is this configurable somewhere to change it to the right site?

2.) Airspaces: I have added some "Prohibited" airspace to my OpenAir formatted airspace file. However, the text lines "AC P / AN FAP 64 PLNDABA / AL SFC / AH 6500 FT" (where "/" is a carriage return) render as "unknown" rather than as "Prohibited" (which would be similar to "Restricted" - and, BTW, the "D" renders a "D" instead of "Danger"). Is there a way to control how the "P" and "D" are interpreted?

3.) Airspaces: I have added some airspace definitions containing the "V X=...S ...E / DB A1 S A2 E, B1 S B2 E" (a circle, centred at X and going clockwise from A to B). These work fine, however the tag "V D=-" to force the counter-clockwise rotation does not seem to work. Where am I going wrong? Do I have the tag correctly defined for counter-clockwise?

4.) > Settings > Configure KFlog > Map projections: When defining conical & adding in two standard parallels (home site 26deg02 S and 27deg36E plus one parallel at 24S and the other at 28S), I get a very strange looking map such that circular airspace definitions are extremely eliptical & appear oblique. If I use the cylindrical projection, the map appears okay, but the circles are still elliptical instead of round... Where am I going wrong here?

Any assistance, tips or other comments will be most appreciated (replies in EN, DE, NL or AF).

Regards, Hendrik.

This email and all contents are subject to the following disclaimer:

"http://www.dimensiondata.com/emaildisclaimer.htm"
_______________________________________________
Kflog-user mailing list
Kflog-user at kflog.org
http://kflog.org/mailman/listinfo/kflog-user

--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
This email and all contents are subject to the following disclaimer:

"http://www.dimensiondata.com/emaildisclaimer.htm"