
<!-- We can also use the HAT file to selectively replace the values
read in via a RESP file. In the following example the RESP file
hill.resp is used verbatim, except for all occurances of Blockette50,
field 4 will now read 30.2" and all Blockette53 field 3 (tranfer
function type) will now be type "B" (analog response).  -->

<SHAPEFILE>


<!-- To build up a response from a collection of snippet, we need to
know how to piece the snippets together. As a response is
hierarchical, we need to represent the hierarchy of the
blocketts. i.e. a station can have 0-N B51s. a B54 can have a B57 and a
B58. We are proposing that each snippet file have stages grouped together (i.e. B54/B57/B58 is one stage) Here is an example where we glue together 6 stages from 2 different files. -->

<station name="DAV">
	<init name="latitude">
	 <field> B50F4</field>
	 <val> 30.2 </val>
	</init>
	<init>
	 <field> B50F10</field>
	 <val> this is a station comment B50F10 </val>
	</init>
	<init name="longitude">
	 <field> B50F5</field>
	 <val> 40.5 </val>
	</init>
	
	<channel name="dav_BHN">

	        <snipfile>hill4_BHN.snip</snipfile> 

                <!-- For Channel blockettes (and station blockettes)
                we just look through a snippet file looking for the
                first channel (station) blockette -->

              <stage>
                <first>1</first>
		<last>4</last>
			<snipfile>b58_1.snip</snipfile>
                <!-- We will get the rest of the stages from the first file again  -->

              </stage>

              <stage>
                <first>0</first>
		<last>0</last>
			<snipfile>b58_1.snip</snipfile>
                <!-- We will get the rest of the stages from the first file again  -->

		<init name="overall sensitivity">
		<field> B58F4 </field>
		<val> 1.11111E+09 </val>
		</init>

              </stage>

	</channel>
	
	
</station>

<!-- Here is an example of the combination of snippets and a RESP file. -->

<!-- I'm not really convinced that this is a good idea to mix the
snippets and a RESP file, but let's at least discuss it at this
point. -->



</SHAPEFILE>
