Moved config references from viz plugin and common dataplugin (stored in /awips2/cave/etc) to edex plugins (stored in /awips2/edex/data/utility), which included moving some files from the awips2 repo to awips2-goesr. Having the configs on the EDEX side will allow for minor config updates without major rpm releases. I also cleaned up the NWS version of the GOES Menus. Separated out each sector based on what products were available so the menus shouldn't have "extra" menu items that don't exist. I've also reduced the number of submenus so it's easier to load a product. Summary of changes: com.raytheon.viz.satellite -Removed all references of satellite base/goesr/glm/himiwari bundle files (now in awips2-goesr/edexOsgi/com.raytheon.uf.edex.plugin.goesr) -Removed extra copy of goesr menus (localization/menus/satellite/goesr/goesr) -Removed main goesr/glm/himawari menus (now in awips2-goesr/edexOsgi/com.raytheon.uf.edex.plugin.goesr) -Removed all base satellite menus (now in awips2/edexOsgi/com.raytheon.edex.plugin.satellite) com.raytheon.uf.common.dataplugin.satellite -Removed all satellite (base) colormaps references (now in awips2/edexOsgi/com.raytheon.edex.plugin.satellite) -Removed all base satellite derived parameters references (now in awips2/edexOsgi/com.raytheon.edex.plugin.satellite) -Removed all base satellite menu references (now in awips2/edexOsgi/com.raytheon.edex.plugin.satellite) -Removed satelliteImageryStyleRules.xml (now in awips2/edexOsgi/com.raytheon.edex.plugin.satellite) com.raytheon.edex.plugin.satellite +Added base satellite menus from awips2/cave/com.raytheon.viz.satellite here +Added base satellite menus from com.raytheon.uf.common.dataplugin.satellite here +Added base satellite colormaps from com.raytheon.uf.common.dataplugin.satellite here +Added base satellite derived parameters from com.raytheon.uf.common.dataplugin.satellite here +Added satelliteImageryStyleRules.xml from com.raytheon.uf.common.dataplugin.satellite here |
||
---|---|---|
.github/workflows | ||
build | ||
cave | ||
dist | ||
docs | ||
edexOsgi | ||
javaUtilities | ||
localization | ||
pythonPackages/pypies | ||
rpms | ||
tests | ||
.gitignore | ||
.travis.yml | ||
awips_install.sh | ||
environment.yml | ||
FOSS_COTS_License.pdf | ||
mkdocs.yml | ||
README.md |
Unidata AWIPS
https://www.unidata.ucar.edu/software/awips/
AWIPS (formerly know as AWIPS II or AWIPS2) is a meteorological display and analysis package developed by the National Weather Service and Raytheon for operational forecasting. AWIPS is a Java application consisting of a data-rendering client (CAVE, which runs on Red Hat/CentOS Linux, macOS, and Windows), and a backend data server (EDEX, which runs on x86_64 Red Hat/CentOS 6 and 7).
AWIPS takes a unified approach to data ingest, and most data types follow a standard path through the system, starting with an LDM client requesting data from Unidata's IDD, which are then decoded and stored as HDF5 and PostgreSQL/PostGIS metadata. Unidata supports two visualization frameworks for rendering AWIPS data:
- CAVE - the Common AWIPS Visualization Environment
- python-awips - a Python data access framework for requesting Numpy data arrays and Shapely geometries.
License
Unidata AWIPS source code and binaries (RPMs) are considered to be in the public domain, meaning there are no restrictions on any download, modification, or distribution in any form (original or modified). Unidata AWIPS contains no proprietery content and is therefore not subject to export controls as stated in the Master Rights licensing file.
AWIPS Data in the Cloud
Through a grant provided by Jetstream, Unidata is able to run a real-time EDEX data server in cloud, providing free AWIPS data to UCAR member institutions and other geoscience research and education organizations. When prompted in the Connectivity Preferences dialog, enter edex-cloud.unidata.ucar.edu
(without adding http:// before, or :9581/services after), or select it from the default dropdown list.
Documentation - http://unidata.github.io/awips2/
AWIPS Source Code Respositories
Setting up the AWIPS Development Environment (ADE)
Instructions on how to deploy CAVE from Eclipse.
-
Change
/etc/yum.repos.d/awips2.repo
to[awips2repo] name=AWIPS II Repository baseurl=https://www.unidata.ucar.edu/repos/yum/el6-dev/ enabled=1 protect=0 gpgcheck=0 proxy=_none_
-
yum clean all && yum groupinstall awips2-ade
This will install Eclipse (4.6.1), Java (1.8), Ant, Maven, Python 2.7 and its modules (Numpy, Shapely, etc.)
-
git clone https://github.com/Unidata/awips2.git
The full list of repositories required:
git clone https://github.com/Unidata/awips2.git git clone https://github.com/Unidata/awips2-core.git git clone https://github.com/Unidata/awips2-core-foss.git git clone https://github.com/Unidata/awips2-foss.git git clone https://github.com/Unidata/awips2-ncep.git git clone https://github.com/Unidata/awips2-rpm.git
Optional repositories:
git clone https://github.com/Unidata/awips2-nws.git git clone https://github.com/Unidata/awips2-gsd.git git clone https://github.com/Unidata/awips2-drawing.git
-
Run
/awips2/eclipse/eclipse.sh
-
Preferences > Java
Set to /awips2/java
-
Preferences > PyDev > Python Interpreter
Set to /awips2/python/bin/python (should be resolved by Auto-Config)
-
File > Import > General > Existing Projects Into Workspace
Import all of the git cloned project folders EXCEPT for the main (first) github.com/Unidata/awips2.git directory (which should be ~/awips2).
You'll want to import ~/awips2 in three parts to ensure a clean and error-free Eclipse build:
- Import awips2/cave > Select All Projects > Finish
- Import awips2/edexOsgi > Select All Projects > Finish
Now import all other repositories fully:
Select awips2-core, awips2-core-foss, awips2-foss, awips2-ncep, etc. > Select All Projects > Finish
-
Project > Clean
Run a clean build and ensure no errors are reported.
-
-
Run com.raytheon.viz.product.awips/developer.product
Double-click the developer.product file to open the Product View in Eclipse. Select Overview > Synchronize and then right-click the file in the left-side package explorer:
Select Run As > Eclipse Application to launch CAVE in the development environment.
Select Debug > Eclipse Application to launch CAVE in in debug mode.