CSTARS / spatial-cimis

New repository for the DWR Spatial CIMIS program
MIT License
0 stars 1 forks source link

Create a working version of the WMS.CGI cgi package for the DWR's setup #32

Closed qjhart closed 5 years ago

qjhart commented 5 years ago

The current spatial cimis program for the GOES-16/17 satellites do not include a continuation of the old GOES satellite WMS services. DWR wants to to continue using those services using the new server setup. The Service would be a re-write of the existing wms.cgi perl script, updated for format of the new grass database.

qjhart commented 5 years ago

I have updated this script, to work on the new grass db and with the new data. There is one problem however, it'd be good if we could use the same code for both the GOES15 and GOES17 setup. However, the naming scheme for the days are different. We need a method to connect to both of these machines.

qjhart commented 5 years ago

@gjscheer-ucd this is blocked on our decision related to merging GOES-16-17 into master.

qjhart commented 5 years ago

I have pretty much got the cg.cgi grass script to work, the next thing I need is to get the zipcode summary data to work. This requires the zipcode mapset to be included. I think I will move that to the PERMANENT database however.

First get the data:

# Your dev connection should have it's tunnels setup.
 rsync --exclude=.tmp --exclude=.bash_history --rsh='ssh -p 2222' \ qhart@localhost:/apps/cimis/gdb/cimis/zipcode ~cimis/gdb15/cimis/ -a -v

# Then let's copy the zipcode_2012 to PERMANENT
 g.copy rast=zipcode_2012@zipcode,zipcode_2012
# Then remove that mapset
rm -rf ~/gdb15/cimis/zipcode

Then update the zipcode, to use the PERMANENT mapset.

In addition, I updated the script to use the g.parser command. This allows automatic html generation, and it more standard.

g.cimis-dwr

Next, I created a g.cimis-dwr script that wraps up the DWR make files. Since these scripts use the state mask, I also added that mask to the PERMANENT mapset.

qjhart commented 5 years ago

Added #63 to complete this step

qjhart commented 5 years ago

This is fully completed, with two additional endpoints on the system.