台灣無線電俱樂部 TAIWAN RADIO CLUB ( TRC )

 找回密碼
 註冊
搜索
無線王資訊有限公司台灣摩托羅拉授權代理商anytone 自由通無線電對講機歡迎贊助廣告歡迎贊助廣告
查看: 3108|回復: 3
打印 上一主題 下一主題

Amateur Data Interchange Format 1.0

[複製鏈接]
  • TA的每日心情
    擦汗
    2024-8-12 06:11
  • 簽到天數: 2110 天

    [LV.Master]伴壇終老

    跳轉到指定樓層
    樓主
    發表於 2013-11-29 18:15:39 | 只看該作者 回帖獎勵 |倒序瀏覽 |閱讀模式
    http://www.adif.org/adif.html

    1. Physical Specifications:
    Each data field is preceded by a field name and length enclosed in angle brackets. The name and length are separated by a colon. The field name may be in upper, lower, or mixed case. Case is insignificant. For instance, CALL, Call, or call are equivalent. The length specification is ASCII text in display format, and may be of any non-negative value. The data follows the closing angle bracket. For example:
    <CALL:6>WN4AZY

    Records are made up of multiple fields and terminated with <EOR> or <eor> as an end-of-record marker. For example:
    <call:6>WN4AZY<band:3>20M<mode:4>RTTY<qso_date:8>19960513<time_on:4>1305<eor>

    An optional field type indicator may follow the field length, separated by a colon: For example:
    <qso_date:8:d>19960513

    The field type indicator may be in upper, lower, or mixed case. A field type indicator is optional. For instance, the Field Definition for QSO_DATE specifies that the field is always of type Date, so it is not necessary to repeat it here. However, when exporting user-defined fields that are not part of the ADIF specification, a type indicator will assist anyone attempting to import the data.
    Any number of characters of any value except < may be added after a field’s data or <eor> and before the start of the next field. This is typically carriage returns and/or line-feeds to make the file easier to read in a text viewer. For example:
    <call:6>WN4AZY<band:3>20M<mode:4>RTTY
    <qso_date:8:d>19960513<time_on:4>1305<eor>
    <call:5>N6MRQ<band:2>2M<mode:2>FM
    <qso_date:8:d>19961231<time_on:6>235959<eor>

    In this example, a new line is inserted in the middle of each record, and two newlines are inserted at the end of each record. This makes long records easy to read in a text editor.
    Optional header information may be included before the actual data in the file. To include optional header info, the first character of the file must be something other than <. Any amount of header info of any value except <eoh> may be included. The header info must be terminated with <eoh>. Any number of characters of any value except < may follow <eoh>. The first < after <eoh> is the start of the first field of the first data record in the file. Here is an example:
    this data was exported using WF1B RTTY version 9, conforming to ADIF standard specification version 9.99<eoh>
    <call:4>aa1a...
    If the first character of a file is <, it is presumed to be the first field of the first data record.
    The ADIF version may be included in the header info as follows: <adif_ver:4>1.00 is included as part of the header specification, an importing program can easily determine the ADIF version used to create the file. Note that this must not be at the beginning of the header info, because < as the first character indicates that there is no header.
    It is important for the programmer importing ADIF data to note that any number of characters of any value may follow the actual data in a field. For example, carriage return/linefeed, or just a line feed. There is nothing in the specifications to prevent an exporter from placing a comment after the actual data. Therefore, after reading a field’s data based on the length specification, the programmer should read and discard characters until the start of a new field (<) or <eor> is encountered.
    There is no specification for the order in which fields appear. They may appear in any order. Unused fields may be omitted entirely. Therefore, each record will not necessarily have the same fields. The specification does not prohibit a zero-length field, so those writing import programs should allow for this.
    There is no specification for field length or maximum field length in the Physical Specifications. Unless there is a length specification in the Field Definition, exporters simply export all data in their field. Importers import as much data as their program can accept.
    Note that while these examples have all been of simple ASCII fields, the specification permits data of any type or length. It could be easily used to transfer pictures or text documents, for instance.

    2. Field Type Definitions:
    Type
    Description
    DateA date specification in YYYYMMDD format
    TimeA time specification. May be 6 characters long (HHMMSS) if seconds are included, 4 characters (HHMM) if seconds are not included. Time is in 24-hour format, from 0000 to 235959. A zero-length field or omission of the field indicates an empty time value.
    MMulti-line text field. For xBase MEMO and similar data.
    C (Character)So far everyone who has written an export program has not specified a type for character data. However, it is included in the specifications for consistency.


    回復

    使用道具 舉報

  • TA的每日心情
    擦汗
    2024-8-12 06:11
  • 簽到天數: 2110 天

    [LV.Master]伴壇終老

    沙發
     樓主| 發表於 2013-11-29 18:25:12 | 只看該作者
    3. Field Definitions:
    NameTypeComment
    ADDRESSMAs it will appear on the mailing label
    AGEN
    ARRL_SECTC
    BANDC160M, 80M, 40M, 30M, 20M, 17M, 15M, 12M, 10M, 6M, 2M, 70CM,23CM...see table below
    CALLC
    CNTYCUS County in the format STATE,COUNTY. For example GA,BARROW. Use CQ County list
    COMMENTCComment field for QSO
    CONTCContinent: NA,SA,EU,AF,OC,AS
    CONTEST_IDCContest Indentifier -- SS, ARRLVHF, ARRLDX, etc.
    CQZNCQ Zone
    DXCCNNumeric identifiers from ARRL. See table below
    FREQNin Megahertz
    GRIDSQUAREC4, 6, or 8 or however many characters
    IOTACHYPHEN MUST BE INCLUDED. Example: NA-001 IOTA PROVIDES DISK IN THIS FORMAT
    ITUZNITU Zone
    MODECSSB, CW, RTTY, TOR=AMTOR, PKT, AM, FM, SSTV, ATV, PAC=PACTOR,CLO=CLOVER
    NAMEC
    NOTESMLong text for digital copy, third party traffic, etc.
    OPERATORCCallsign of person logging the QSO
    PFXCWPX prefix
    PROP_MODEC
    QSLMSGMPersonal message to appear on qsl card
    QSLRDATEDQSL Rcvd Date
    QSLSDATEDQSL Sent Date
    QSL_RCVDCY=Yes, N=No, R=Requested, I=Ignore or Invalid
    QSL_SENTCY=Yes, N=No, R=Requested, I=Ignore or Invalid
    QSL_VIAC
    QSO_DATEDYYYYMMDD in UTC
    QTHC
    RST_RCVDC
    RST_SENTC
    RX_PWRNPower of other station in Watts
    SAT_MODECSatellite Mode
    SAT_NAMECName of satellite
    SRXNReceived serial number for a contest QSO
    STATECUS state
    STXNTransmitted serial number for a contest QSO
    TEN_TENN
    TIME_OFFCHHMM or HHMMSS in UTC
    TIME_ONCHHMM or HHMMSS in UTC
    TX_PWRNPower of this station in watts
    VE_PROVC2-letter abbreviations: AB, BC, MB, NB, NF, NS, NT, ON, PE, QC, SK, YT


    回復 支持 反對

    使用道具 舉報

  • TA的每日心情
    開心
    2016-8-3 01:11
  • 簽到天數: 211 天

    [LV.7]常住居民III

    板凳
    發表於 2013-11-29 18:56:48 | 只看該作者
    上傳LoTW就要用ADIF的格式,像我這個手寫LOG的古代人,
    每個月都要勞煩高手幫我轉檔,才能上傳LoTW,金拍謝!!
    回復 支持 反對

    使用道具 舉報

  • TA的每日心情
    擦汗
    2024-8-12 06:11
  • 簽到天數: 2110 天

    [LV.Master]伴壇終老

    地板
     樓主| 發表於 2013-11-29 19:12:54 | 只看該作者
    我那個守聽 JT65 是 CSV 的檔
    三天就要"手工" 用 Excel 把他變成 ADIF ....才能上傳
    回復 支持 反對

    使用道具 舉報

    您需要登錄後才可以回帖 登錄 | 註冊

    本版積分規則

    小黑屋|手機版|Archiver|TRC 台灣無線電俱樂部 taiwan radio club  

    GMT+8, 2024-11-23 07:32 , Processed in 0.043962 second(s), 16 queries .

    Powered by Discuz! X3.3

    © 2001-2017 Comsenz Inc.

    快速回復 返回頂部 返回列表