[Met_help] [rt.rap.ucar.edu #65984] History for ASCII2NC question

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

I have observations (ADPSFC) from local sensors which I'm reformatting into the MET ASCII point observation format so I can convert them into NetCDF format using ASCII2NC. If my local station IDs are seven characters long is this a problem? I have surveyed a fairly large number of mesonet surface observations obtained from MADIS for other locations in CONUS which are presently in the MET ASCII point observation format and none of the identifiers exceeds five characters.

Thanks.

R/
John


Mr John W. Raby, Meteorologist

U.S. Army Research Laboratory

White Sands Missile Range, NM 88002

(575) 678-2004 DSN 258-2004

FAX (575) 678-1230 DSN 258-1230

Email: john.w.raby2.civ at mail.mil<mailto:john.raby at us.army.mil>


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Re: [rt.rap.ucar.edu #65984] ASCII2NC question
From: John Halley Gotway
Time: Wed Mar 26 10:18:26 2014

John,

The station ids can be of arbitrary length.  The only stipulation is
that they can't have any embedded whitespace - that'd screw up our
parsing of columns.

As I mentioned in answer to your previous question, MET adjusts the
widths of the output columns based on the number of characters being
written.  So the "OBS_SID" column in the MPR output line will
get wide enough to hold the longest station name present in your data.

Thanks,
John

On 03/25/2014 03:45 PM, Raby, John W USA CIV via RT wrote:
>
> Tue Mar 25 15:45:41 2014: Request 65984 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>         Queue: met_help
>       Subject: ASCII2NC question
>         Owner: Nobody
>    Requestors: john.w.raby2.civ at mail.mil
>        Status: new
>   Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65984 >
>
>
> I have observations (ADPSFC) from local sensors which I'm
reformatting into the MET ASCII point observation format so I can
convert them into NetCDF format using ASCII2NC. If my local station
IDs are seven characters long is this a problem? I have surveyed a
fairly large number of mesonet surface observations obtained from
MADIS for other locations in CONUS which are presently in the MET
ASCII point observation format and none of the identifiers exceeds
five characters.
>
> Thanks.
>
> R/
> John
>
>
> Mr John W. Raby, Meteorologist
>
> U.S. Army Research Laboratory
>
> White Sands Missile Range, NM 88002
>
> (575) 678-2004 DSN 258-2004
>
> FAX (575) 678-1230 DSN 258-1230
>
> Email: john.w.raby2.civ at mail.mil<mailto:john.raby at us.army.mil>
>

------------------------------------------------
Subject: ASCII2NC question
From: Raby, John W USA CIV
Time: Wed Mar 26 10:51:17 2014

Classification: UNCLASSIFIED
Caveats: NONE

John -

Many thanks for your response on that. That answers my question on the
station ids.

Regards the previous (from yesterday) question about the formatting of
the MPR files, I am still digesting the information and have passed it
on to my colleague who is working the MS Access data entry for his
use. Will let you after he has looked at it and responds.

Also, I haven’t forgotten that I owe you the results of testing using
the suggestion you made in reference to [rt.rap.ucar.edu #65756]
Point_Stat error. I just got bogged down and could not return to it
"soon" as I told you. Sorry about that.

I continued running Point-Stat on the remaining data and after
processing 125 sets of forecast and little_r observations, I found a
total of 23 little_r files out of the 125 which caused the same
failure. So, I'm at the point now, where I'm going to give your
suggestion a try.

R/
John

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, March 26, 2014 10:18 AM
To: Raby, John W CIV USARMY ARL (US)
Subject: Re: [rt.rap.ucar.edu #65984] ASCII2NC question

John,

The station ids can be of arbitrary length.  The only stipulation is
that they can't have any embedded whitespace - that'd screw up our
parsing of columns.

As I mentioned in answer to your previous question, MET adjusts the
widths of the output columns based on the number of characters being
written.  So the "OBS_SID" column in the MPR output line will get wide
enough to hold the longest station name present in your data.

Thanks,
John

On 03/25/2014 03:45 PM, Raby, John W USA CIV via RT wrote:
>
> Tue Mar 25 15:45:41 2014: Request 65984 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>         Queue: met_help
>       Subject: ASCII2NC question
>         Owner: Nobody
>    Requestors: john.w.raby2.civ at mail.mil
>        Status: new
>   Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65984
> >
>
>
> I have observations (ADPSFC) from local sensors which I'm
reformatting into the MET ASCII point observation format so I can
convert them into NetCDF format using ASCII2NC. If my local station
IDs are seven characters long is this a problem? I have surveyed a
fairly large number of mesonet surface observations obtained from
MADIS for other locations in CONUS which are presently in the MET
ASCII point observation format and none of the identifiers exceeds
five characters.
>
> Thanks.
>
> R/
> John
>
>
> Mr John W. Raby, Meteorologist
>
> U.S. Army Research Laboratory
>
> White Sands Missile Range, NM 88002
>
> (575) 678-2004 DSN 258-2004
>
> FAX (575) 678-1230 DSN 258-1230
>
> Email: john.w.raby2.civ at mail.mil<mailto:john.raby at us.army.mil>
>


Classification: UNCLASSIFIED
Caveats: NONE



------------------------------------------------