Take a look at the ADIF (Amateur Data Interchange Format) definitions
at www.adif.org. ADIF defines a method of transferring data between
applications but it does not define what data must be present in any
transfer. In addition, ADIF provides for "application-defined" fields
in the form: "<APP_{PROGRAMID}_{FIELDNAME}: " Many applications use
and maintain custom data, making use of "application-defined" fields to
export and import that data for back-up and/or to transfer data among
modules (e.g. between the logger and a post contest analysis module
or export from one contest log into a history file for future years
and other contests).
>> Anyone know why .ADI files saved in N1MM and some other programs
>> cannot be imported into WL?
It is entirely probably that WL is looking for information in its
own format (multiplier data, etc.) that is not present in the same
format from another logger. However, since all major and most minor
contests use data already enumerated by ADIF, it seems strange that
a logging program would continue to insist on exporting (and importing)
data in an application specific manner rather than using the standard
ADIF fields and ADIF enumerated values. For example - some logging
programs insist on exporting the "DXCC Prefix" which is not standard
as "<APP_LOGGERNAME_COUNTRY: " or even "<APP_LOGERNAME_MULT1: " rather
than use the "country number" which is assigned by ARRL and enumerated
by ADIF. Another example ... some loggers store state, province,
oblast, prefecture, etc. names in fields like <VE_PROV (deprecated)
or <APP_Logger_Oblast:, <APP_Logger_Prefecture:, <APP_Logger_PY_PROV,
etc. rather in the "<STATE: " field as defined by ADIF. All of this
makes it difficult for other loggers to make use of the data - even
though the state/province/etc. abbreviations and/or numbers are
standardized!
73,
... Joe, W4TV
On 11/13/2012 11:39 PM, Gary AL9A wrote:
I've not looked at an N1MM adi file, but I'm assuming the main problem
is in the field name variables. Some to them may be common, such as
CALL, but many WL field names start with <Writelog_App...> or some such
thing. I'm sure N1MM doesn't know how to handle those fields.
Similarly, a "generic" adi file created by N1MM or some other logger
will probably have field names that WL won't recognize.
73,
Gary AL9A
----- Original Message ----- From: "Hal Kennedy" <halken@comcast.net>
To: <writelog@contesting.com>
Sent: November 13, 2012 5:15 PM
Subject: [WriteLog] .ADI compatability
Anyone know why .ADI files saved in N1MM and some other programs
cannot be
imported into WL? They always seem to be missing a column here or there.
Is the WL "standard" for >ADI somehow different that others?
73
Hal
N4GG
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|