CVS commands to manage site xml
From PTAGISWiki
Assuming that the ALRS tables contain new information about sites, the procedure to get the Data Sites Flash map is:
- Before generating the new site xml, run
cvs -nq up
to see if there are any uncommitted changes from the last update.
- execute the perl program at sockeye:/home/ptagdev/ptagis3/source/sitexml/source/create_site_xml.pl
This directory is under CVS control so before running the script, do a
cvs -nq up
to make sure that everything is up to date.
Normal output of the script looks like this:
sockeye:/home/ptagdev/ptagis3/source/sitexml/source$ create_site_xml.pl Use of $* is deprecated at /home/pittag/bin/UTIL/HashAssemblage.pm line 359, <DEF> line 101. connect to DB ... via -> dbi:Ingres:blueback::ptagis3;-uwebjsp Creating tagging.xml... ----------------- Creating juvenile.xml... ----------------- Creating adult.xml... ----------------- Creating separation.xml... -----------------
- run cvs -nq up again to see what sites have been added to which xml files
sockeye:/home/ptagdev/ptagis3/source/sitexml/source$ cvs -nq up M adult.xml M juvenile.xml M separation.xml M tagging.xml
sockeye:/home/ptagdev/ptagis3/source/sitexml/source$ cvs diff adult.xml Index: adult.xml =================================================================== RCS file: /home/ptagdev/CVS/home/ptagdev/ptagis3/source/sitexml/source/adult.xml,v retrieving revision 1.35 diff -r1.35 adult.xml 2,78c2,78 < <row><modification_date></modification_date><loc_name>Abernathy Creek Farmers Bridge</loc_name><category>obs</category><site>AB2</site><type>ADU</type><rkm></rkm><huc></huc><latlng>0,0</latlng></row> < <row><modification_date></modification_date><loc_name>Instream detectors at Abernathy Creek, rkm 1</loc_name><category>obs</category><site>AB3</site><type>ADU</type><rkm>087.1</rkm><huc>17080003</huc><latlng>46.19556,-123.16454</latlng></row> < <row><modification_date></modification_date><loc_name>Burlingame Diversion Dam and Canal</loc_name><category>obs</category><site>BGM</site><type>ADU</type><rkm>509</rkm><huc>17070102</huc><latlng>46.023271,-118.424483</latlng></row> < <row><modification_date></modification_date><loc_name>Bonneville Bradford Is. Ladder</loc_name><category>obs</category><site>BO1</site><type>ADU</type><rkm></rkm><huc></huc><latlng>0,0</latlng></row> < <row><modification_date></modification_date><loc_name>Bonneville Cascades Is. Ladder</loc_name><category>obs</category><site>BO2</site><type>ADU</type><rkm></rkm><huc></huc><latlng>0,0</latlng></row> < <row><modification_date></modification_date><loc_name>Bonneville WA Shore Ladder/AFF</loc_name><category>obs</category><site>BO3</site><type>ADU</type><rkm></rkm><huc></huc><latlng>0,0</latlng></row> < <row><modification_date></modification_date><loc_name>Washington Shore Ladder Vertical Slots</loc_name><category>obs</category><site>BO4</site><type>ADU</type><rkm>000</rkm><huc>17070105</huc><latlng>0,0</latlng></row>
- Now the new XML files should be copied from sockeye to pitblade to verify that the changes look correct.
Deploy (copy) to pitblade:/dsk2/ptagis-1.0/web/ptagis/sites/map/
- Test by visiting the site map and clicking on the new sites
- If all looks good, deploy to bay://usr/local/pitweb/ptagis-1.0/web/ptagis/sites/map/
