Hey Albert,
thanks a lot for the detailed information. Shouldn't be much of a
problem to implement this 1/not 1 thing. I guess if the newer flags
exist, we'll take those and otherwise we'll use you suggestion. I'll
have a look at it tomorrow.
Turbo
Am 05.01.2011 00:17, schrieb Albert Kiessling:
Hello, Turbo,
I know the coding of the Zander files very well since more than 20
years. The original Zander-file corresponds to the file you have
described with the 44 characters line. The so-called optional
description is called "info"-line in the Zander-description.
This info-line contains the principal coding of "turnpoint" or
"airport". Is the character at position 35 a "1", this means
"airport", because traditionally the airport-info begins with the
frequency of the airport (for example 122.5MHz). Any other character
than "1" is interpreted as a turnpoint. The information in
the positions 49 and more are optional codings, which are not
interpreted by the Zander-vario, but only by the PC-Programs and
perhaps newer devices. In the attachment, you will find an original
Zander Airfield-Database with the extension .wz and a lot of special
codings. The "1" or "not 1"-coding in position 35 is mandatory for the
SR940.
The original Zander-computer knows 2 database-files:
The turnpoint-file with the file extension .wpz and a maximum of 990
turnpoints. The "1" or "not 1" differs between airfield and turnpoint.
The airfield-file contains a maximum of 4500 airfields with the coding
"1" in position 35 and a lot of further codings in the further positions.
So it would be easy for XCsoar to interprete the "1" in position 35 as
the airfield-code. Another possibility would be to take simply the
file-extension which is not so precise because a turnpoint-file can
contain airfields as well (which are on the same time turnpoints).
I would appreciate it if you could realize this official
Zander-decoding in XCSoar as other programs like "Strepla" do since
years. A further step could be to interprete the positions 49... for a
more detailled description of the airfields.
With best regards
Albert Kiessling
----- Original Message -----
*From:* Tobias Bieniek <mailto:tobias.bien...@gmx.de>
*To:* albert.kiessl...@t-online.de
<mailto:albert.kiessl...@t-online.de>
*Cc:* Xcsoar-user@lists.sourceforge.net
<mailto:Xcsoar-user@lists.sourceforge.net>
*Sent:* Monday, January 03, 2011 10:00 PM
*Subject:* Re: [Xcsoar-user] XCSoar Final version 6.0
Hi Albert,
about the Zander file issue:
A Zander waypoint file usually consists of an number of text
lines, with one waypoint each.
Each line has usually 44 characters. 0-12 is the name, 13-20 is
latitude, 21-29 is longitude, 30-34 is altitude/elevation and
35-44 is an optional description.
Some files I have found on http://soaringweb.org/TP/HomePage.html
however have another field starting at 45, so that the lines can
be 49 characters long.
Usual values for that field are WP=Waypoint, HA=Home Airfield,
WA=Airfield, WL=Landing Field.
If the field isn't found the waypoint is assumed to be a normal
waypoint.
I hope I explained it well enought, if you have any more questions
feel free to reply.
Turbo
Am 01.01.2011 23:41, schrieb albert.kiessl...@t-online.de:
Hello,
today I could do some tests with the new XCSoarversion on my
Fujitsu-Siemens Loox PDA with Windows Mobile. It worked very
fine, even as I used the software for the first time, it was very
easy to understand and to applicate. Congratulation to that.
In coherence with the new support of Zander turnpoint-files I
found 2 small bugs:
1. The help text does not refer to the new file-extension .wpz
2. All waypoints in the file are declared as "turnpoints".
Obviously the Zander code for the different kinds of waypoints is
not decoded.
A simple way to decide between airports and turnpoints could be,
that the waypoints in the airport-file with the extension
.wz could be interpreted as "airports" whereas all waypoints in
the turnpointfile with the extension .wpz could be be
interpreted as "turnpoints"
Is there another possibility to solve the problem in the actual
version?
The third bug seems somehow more serious:
In coherence with the HTC Advantage PDA with Windows Mobile 6.1
professional and PXA270-624MHz processor the installation
interrupted and failed with the .cab-file as well as with the
.exe-file.
With best regards
Albert
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment,
and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcsoar-user
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcsoar-user
