All,

I got this input from Larry Conklin regarding long file names. Arie has a
web page that describes the three letter component code name. Here's the
link http://members.iinet.net.au/~ajbv/AutoDRM/Example/Alaska.html. It's
part of this AutoDRM documentation.

As far as station/sensor ID there is no standard. It just needs to be unique
so if you send in an event file to my system it won't overwrite an existing
file. Since SDR and EMON are DOS programs, the ID string was limited to 3
characters. As 32 bit dataloggers come online this could be any length.
Since the sensor ID should be the same as the Sensor Name defined in the PSN
4 format it will be limited to 6 characters.

If anyone has comments about lone file names please send to the list and not
just to me. Thanks.

-Larry Cochrane
Redwood City, PSN


----- Original Message -----
From: "Larry Conklin" 
To: "Larry Cochrane" 
Sent: Tuesday, July 10, 2001 12:43 PM
Subject: Long file names


> Larry
>
> I am more or less neutral on the question of using long file names to
convey
> more discriptive information about PSN4 files, but I do think that
defining
> a unique file extension to denote PSN4 files and allow Windows to make
file
> associations with Winquake would be a very good idea.
>
> Regarding the component type field in your proposed file name format,
> evidently there is an established convention for the three letter code,
but
> I have'nt run across a source that explains how the codes are defined.
Can
> you point me to a source?
>
> Also, are there any existing conventions or restrictions on the sensor ID
> that should be followed to ensure compatability with the rest of the PSN
> community?
>
> Larry Conklin
> lconklin@............
>
>

__________________________________________________________

Public Seismic Network Mailing List (PSN-L)