awips2/edexOsgi/com.raytheon.uf.common.dataplugin.warning/utility/common_static/base/warngen/geospatialConfig_ZONE.xml
Baoyu Yin 8568cd8419 VLab Issue #4796 - AWIPS2_DR_17420 WarnGen IBW templates and 14.2.1 template corrections; fixes #4796
Change-Id: Ieb4a6d68b48351deacbddda65f1ff53485c3402d

Former-commit-id: f077d3cd4084faf8ad7c8865e84df53e59a5db72
2014-09-19 15:02:23 -04:00

202 lines
6.8 KiB
XML
Executable file

<!-- CREATED 9-16-2013 EVAN BOOKBINDER WFO EAX
THIS DOCUMENT CONTAINS GLOBAL SPATIAL CONFIGURATION SETTINGS FOR **ZONE**
BASED PRODUCTS. INCLUDE THIS FILE INTO EACH ZONE TEMPLATE'S .XML FILE.
THIS REPLACES THE PER-TEMPLATE XML SECTIONS BELOW. IF YOU HAVE LOCAL
CONFIGURATIONS, YOU CAN EITHER:
1.) Copy this file to another geospatialConfig_XXXX.xml file and include
that filename at the top of that WarnGen template's XML file.
2.) Copy one or more of the sections (areaSource, pointSource, etc..)
below and paste them into your template's XML file below the following line
<include file="geospatialConfig_COUNTY.xml"/>
If you have multiple objects with the same name, the last one read is used.
THIS CHANGE WAS DONE SO THAT CONFIGURATIONS COULD BE MADE IN ONE LOCATION
AND NOT ACROSS 20-30 TEMPLATES. A COUNTY-BASED and MARINE-BASED COUNTERPART
EXISTS TO THIS FILE.
-->
<!-- CREATE DEFAULT OBJECTS. THIS SHOULD GENERALLY NOT BE TOUCHED-->
<geospatialConfig>
<pointSource>WarnGenLoc</pointSource>
<areaSource>Zone</areaSource>
<parentAreaSource>States</parentAreaSource>
<timezoneSource>TIMEZONES</timezoneSource>
<timezoneField>TIME_ZONE</timezoneField>
</geospatialConfig>
<!-- CREATE PRIMARY areaSource OBJECT TO GENERATE ZONE-BASED INFORMATION OFF WARNGEN HATCHING -->
<areaSource variable="areas">
<areaSource>Zone</areaSource>
<inclusionPercent>0</inclusionPercent>
<inclusionAndOr>AND</inclusionAndOr>
<inclusionArea>0</inclusionArea>
<areaField>NAME</areaField>
<parentAreaField>NAME</parentAreaField>
<areaNotationField>STATE</areaNotationField>
<feAreaField>FE_AREA</feAreaField>
<timeZoneField>TIME_ZONE</timeZoneField>
<areaNotationTranslationFile>countyTypes.txt</areaNotationTranslationFile>
<fipsField>STATE_ZONE</fipsField>
<pointField>NAME</pointField>
<sortBy>
<sort>parent</sort>
</sortBy>
<pointFilter>
<mapping key="WARNGENLEV">
<constraint constraintValue="1" constraintType="EQUALS" />
</mapping>
</pointFilter>
<includedWatchAreaBuffer>0</includedWatchAreaBuffer>
</areaSource>
<!-- Add in areaSource object to generate county-based information. This could be
used by a template that has a zone based UGC and a county-based headline -->
<areaSource variable="affectedCounties">
<areaSource>COUNTY</areaSource>
<type>INTERSECT</type>
<inclusionPercent>0</inclusionPercent>
<inclusionAndOr>AND</inclusionAndOr>
<inclusionArea>0</inclusionArea>
<areaField>COUNTYNAME</areaField>
<parentAreaField>NAME</parentAreaField>
<areaNotationField>STATE</areaNotationField>
<feAreaField>FE_AREA</feAreaField>
<timeZoneField>TIME_ZONE</timeZoneField>
<areaNotationTranslationFile>countyTypes.txt</areaNotationTranslationFile>
<fipsField>FIPS</fipsField>
<pointField>NAME</pointField>
<sortBy>
<sort>parent</sort>
</sortBy>
<pointFilter>
<mapping key="WARNGENLEV">
<constraint constraintValue="1" constraintType="EQUALS" />
</mapping>
</pointFilter>
<includedWatchAreaBuffer>0</includedWatchAreaBuffer>
</areaSource>
<!-- CREATE pointSource OBJECT TO GENERATE LIST OF CLOSEST POINTS TO DOT (3RD BULLET) -->
<!-- type = AREA allows us to use multi-polygonal shapefiles despite the pointSource misnomer -->
<pointSource variable="closestPoints">
<pointField>NAME</pointField>
<type>AREA</type>
<searchMethod>POINTS</searchMethod>
<maxResults>1</maxResults>
<distanceThreshold>100</distanceThreshold>
<filter>
<mapping key="WARNGENLEV">
<constraint constraintValue="1,2" constraintType="IN" />
</mapping>
<mapping key="LANDWATER">
<constraint constraintValue="L,LW,LC" constraintType="IN" />
</mapping>
</filter>
<sortBy>
<sort>distance</sort>
<sort>warngenlev</sort>
</sortBy>
</pointSource>
<!-- CREATE pointSource OBJECT TO GENERATE LIST OF SECONDARY POINTS TO DOT (3RD BULLET)
...OR ABOUT XXX MILES FROM LARGER KNOWN LOCATION -->
<pointSource variable="otherClosestPoints">
<pointField>NAME</pointField>
<type>AREA</type>
<searchMethod>POINTS</searchMethod>
<maxResults>5</maxResults>
<distanceThreshold>100</distanceThreshold>
<filter>
<mapping key="WARNGENLEV">
<constraint constraintValue="1" constraintType="IN" />
</mapping>
<mapping key="LANDWATER">
<constraint constraintValue="L,LW,LC" constraintType="IN" />
</mapping>
</filter>
<sortBy>
<sort>distance</sort>
<sort>warngenlev</sort>
</sortBy>
</pointSource>
<!-- CREATE pathcastConfig OBJECT FOR PATHCAST (4TH BULLET) -->
<pathcastConfig>
<type>AREA</type>
<inclusionPercent>1</inclusionPercent>
<withinPolygon>true</withinPolygon>
<distanceThreshold>8.0</distanceThreshold>
<interval>5</interval>
<delta>5</delta>
<maxResults>10</maxResults>
<maxGroup>8</maxGroup>
<pointField>Name</pointField>
<areaField>NAME</areaField>
<parentAreaField>STATE</parentAreaField>
<areaNotationField>STATE</areaNotationField>
<areaNotationTranslationFile>countyTypes.txt</areaNotationTranslationFile>
<sortBy>
<sort>warngenlev</sort>
<sort>population</sort>
<sort>distance</sort>
</sortBy>
<filter>
<mapping key="WARNGENLEV">
<constraint constraintValue="1,2" constraintType="IN" />
</mapping>
<mapping key="LANDWATER">
<constraint constraintValue="L,LW,LC" constraintType="IN" />
</mapping>
</filter>
</pathcastConfig>
<!-- CREATE pointSource OBJECT FOR LOWER ORDER CITIES FOR PATHCAST SETTING (4TH BULLET) -->
<pointSource variable="otherPoints">
<pointField>NAME</pointField>
<inclusionPercent>1</inclusionPercent>
<type>AREA</type>
<searchMethod>TRACK</searchMethod>
<withinPolygon>true</withinPolygon>
<maxResults>10</maxResults>
<distanceThreshold>10</distanceThreshold>
<sortBy>
<sort>distance</sort>
<sort>warngenlev</sort>
</sortBy>
<filter>
<mapping key="WARNGENLEV">
<constraint constraintValue="3,4" constraintType="IN" />
</mapping>
<mapping key="LANDWATER">
<constraint constraintValue="L,LW,LC" constraintType="IN" />
</mapping>
</filter>
</pointSource>
<!-- CREATE pointSource OBJECT FOR NON-PATHCAST CITY LIST -->
<pointSource variable="cityList">
<pointField>NAME</pointField>
<inclusionPercent>1</inclusionPercent>
<type>AREA</type>
<searchMethod>TRACK</searchMethod>
<withinPolygon>true</withinPolygon>
<maxResults>20</maxResults>
<distanceThreshold>10</distanceThreshold>
<filter>
<mapping key="WARNGENLEV">
<constraint constraintValue="1,2,3,4" constraintType="IN" />
</mapping>
<mapping key="LANDWATER">
<constraint constraintValue="L,LW,LC" constraintType="IN" />
</mapping>
</filter>
<sortBy>
<sort>warngenlev</sort>
<sort>population</sort>
<sort>distance</sort>
</sortBy>
</pointSource>