NCMC Location Code Implementation Plan
	Doug Neuhauser, doug@seismo.berkeley.edu
	Last updated:	2005/07/07

As of 2005/07/06:

1.  All waveform data received by the NCMC has a blank SEED location code.
    However, non-seismic channels in the BK network, and some historic
    data for the NCSN network has non-blank location codes.

2.  All station and channel metadata at the NCEDC is fully location code compliant.
    All database tables with a location code field have the corresponding
    location code stored in this field (2 blanks for a blank location code),
    and all programs written by the NCMC or NCEDC for storing, retrieving, or 
    comparing SEED channels use all 4 values for channel names:
	sta, net, seedchan, location

3.  There is correspondence between the SNCL in all database tables for
    the Parametric, HT, IR, and Waveform schemas and the SNCL stored in the
    MiniSEED waveform at the NCEDC, with the exception of:
    a.	1991 - 1993 BK waveform files, which do not have a network code in the 
	MiniSEED files (pre-network code SEED files).
    We do plan to eventually update these waveform files to include the Network code
    and the MiniSEED blockette 1000.

4.  When historic catalog and phase data are written to the database, they
    will be written with the full SEED compliant channel names, including
    the proper location code.

5.  We have procedures and database tables in place to provide mapping a
	sta,net,chan,chansrc=USGS -> sta,net,seedchan,location,chansrc=SEED
    since the USGS/MP still uses non-SEED channel names for analog stations.

Conversion to SEED / SNCL channel names:

Phase 1:  Retire CUSP

1.  Implement channel mapping (#5 above) in current REDI system to populate
    real-time events into the parametric database in full SEED SNCL format.
    Status:	
	1.	Implemented in test code, need to finalize mapping of all 
		required hypoinverse field to the corresponding database tables
		and values.

2.  Implement RCG to generate request cards from current REDI system.
    Status:
	1.	Lombard adapting new SCSN RCG for NCMC - SNCL compliant.

3.  Implement WFA to archive waveforms (test mode):
    Status:
	1.	Proxy waveserver complete (but not well tested) 
		which implement Trinet waveserver API and interfaces to:
		1.  BSL SWS (simple wave server), which is SNCL compliant.
		2.  SNC Earthworm WS-V
		Proxy WS will map (using DB) from USGS SNC to SEED SNCL.
	2. 	WFA will be SNCL compliant.

4.  Test SNCL-compliant jiggle against fully compliant SNCL events and waveforms.

--> Retire CUSP!

Phase 2:  Implement new NCMC system:

1.  Install SNCL-compliant Earthworm system, and convert all NCSN data from
    USGS to SEED channel name (SNCL compliant).
    Status:
	1.	EW system SNCL compliant and tested.
	2.	SEED SNCL Hypoinverse config being created.

2.  Implement new hyp2ps and SNCL-compliant event coordinator to enter all
    event parameters with full SEED SNCL names.

3.  NCMC's gcda codes and program are SNCL compliant:
    	wda, rad, ada, ada_export, ada_import

4.  Use SNCL-compliant Trimag for ML computation.

5.  NCMC's MT and Mw code is SNCL compliant.

6.  Requires implementation of Md code, mag coordinator, etc.

--> New system will be SNCL compliant.

Phase 3:

1.  Allow incoming data (waveform, phases, amplitudes, etc) to have non-blank 
    location codes.

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

Issues to be discussed:

1.  If we (CISN) want to use SNCLs BEFORE we implement the new NCMC system,
we have to make changes to our existing EW/EB/REDI system to allow this.

EW changes:
1.  Migrate to EW-SNCL code (digitizer, picker, waveserver, etc).
2.  Change from USGS to SEED channel names.
    If we move to SNCL format but continue to use USGS channel names,
    this will get very confusing in the USGS->SEED name conversion.

EB changes:
1.  Unknown.

REDI changes:
1.  Install EW-SNCL codes.
2.  Rest of REDI is SNCL compliant.

When does USGS want to migrate from USGS SNC to SEED SNCL?