awips2/edexOsgi/com.raytheon.uf.common.dataplugin.warning/utility/common_static/base/warngen/geospatialConfig_COUNTY.xml
Ron Anderson 0d3e04935f Omaha #4853 TO56 - Comment out "affectedZones" in geospatialConfig_COUNTY.xml
Change-Id: I449c946255a3cdaa43ca43e0f27021768372ebe7

Former-commit-id: dea2bfdc4cc26392fc001e83382a1de135704740
2015-09-09 14:19:53 -05:00

204 lines
7 KiB
XML
Executable file

<!-- CREATED 9-16-2013 EVAN BOOKBINDER WFO EAX (MODIFIED 2-6-14 CORRECT TYPO)
THIS DOCUMENT CONTAINS GLOBAL SPATIAL CONFIGURATION SETTINGS FOR **COUNTY**
BASED PRODUCTS. INCLUDE THIS FILE INTO EACH COUNTY 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_MARINE.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 ZONE-BASED and MARINE-BASED COUNTERPART
EXISTS TO THIS FILE.
-->
<!-- CREATE PRIMARY areaSource OBJECT TO GENERATE COUNTY-BASED INFORMATION OFF WARNGEN HATCHING -->
<areaSource variable="areas">
<areaSource>County</areaSource>
<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>
<!-- Add in secondary areaSource object to generate zone-based information.
Not sure why a FIPS product would need zone info, but it's here as a placeholder.
Uncomment the following section only if needed as it can impact performance -->
<!-- areaSource variable="affectedZones">
<areaSource>Zone</areaSource>
<type>INTERSECT</type>
<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 -->
<!-- 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>
<sort>population</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>COUNTYNAME</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">
<searchMethod>TRACK</searchMethod>
<pointField>NAME</pointField>
<inclusionPercent>1</inclusionPercent>
<type>AREA</type>
<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>
<!-- CREATE DEFAULT OBJECTS. THIS SHOULD GENERALLY NOT BE TOUCHED-->
<geospatialConfig>
<pointSource>WarnGenLoc</pointSource>
<areaSource>County</areaSource>
<parentAreaSource>States</parentAreaSource>
<timezoneSource>TIMEZONES</timezoneSource>
<timezoneField>TIME_ZONE</timezoneField>
</geospatialConfig>