Creating the XML source documents --------------------

From the deployments table of the harp database:

cmd /c csv_to_xml.py -d Deployment -f HARP-DataSummary -e fixed -t $(cygpath -w ~/txt/bioacoustics/database/harp/DeploymentInformation.txt) DeploymentInformation.xml

$ cmd /c csv_to_xml.py -d Detections -e Detection -f DataProcLogs -t $(cygpath -w ~/txt/bioacoustics/database/SOCAL33N_logs_sbp.csv) SOCAL33M_logs_sbp.xml

# pretty print
cmd /c xmlpp.py DeploymentInformation.xml >DeploymentInformationPP.xml

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

ODBC can probably be used to access the HARP database
Had problems connecting to the ODBC server after opening port 1526 for
	local host
Tried to setup ODBC via control panel
then configured odbc source, unable to connect...
Not worrying about it now....

Safari:
http://proquest.safaribooksonline.com/1565926218/part3-64623#X2ludGVybmFsX1NlY3Rpb25Db250ZW50P3htbGlkPTE1NjU5MjYyMTgvY2gxMy00NTU0Nw==
see also:
http://www.freelance-developer.com/howto_odbcyp


Structuring XML database
Deployment container
	   Probably makes sense to have each entry be a separate
	   container.  Could use Data_ID as a document name.  Possible
	   deployment types which enclose the document:
	   	      <fixed> 
		      <moving>
           Things to think about:  how much drift?  Are sonobuoys
	   fixed or moving?  If moving, how do we handle long/lat if
	   not reported.  Perhaps treat as fixed and use a <drift> or
	   <mooring> that indicates how likely we are to drift from
	   the deployed site.

detections container
	   add metadata by hand on front
	   still have problem in tags, no ? allowed in <..._file?>

	   



	   
----------------------------------------
line sweep algorithm

