comment on

Thanks Walt!

I have an as yet un-posted version of this that takes out the manual intervention steps, saves an intermediate Cabrillo format file, and then creates the ADIF format file. I then go onto QRZ.com and manually import the ADIF and then export changes to LoTW. Working good so far.

Another un-posted script queries the QRZ XML interface for the callsign data for a hard-coded callsign. This was subsetted into a query script that asks for a callsign and displays a selected group of fields, easy to add or delete fields for your own needs. A bug was found in the QRZ XML interface that they will fix in the next release, but for now has a simple work-around.

I intend to post the updated ADIF script after I add code to enter a "comment" field.

James

There's never enough time to do it right, but always enough time to do it over...

In reply to Re^2: Linux/Perl Cabrillo to ADIF Conversion Script by jmlynesjr
in thread Linux/Perl Cabrillo to ADIF Conversion Script by jmlynesjr

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks