User Shapefiles
[ In this document LLL stands for your site ID. ]
It is recommended that this proceedure be used only for testing shapefiles since you are limited to 5 shapefiles with this method. After testing, adding shapefiles via the the custom and national map methods is a better way to go. This documentation uses polygon shapefiles as an example. Another set of instructions using line shapefiles as an example was written by Wayne Martin of the SST. Full instructions written by FSL can be found on your AWIPS Workstation in the file localization/documentation/shapeFileDisplay.html.
Step 1: Close D2D sessions.
Step 2: Get the three components of the shapefile (.shp, .shx, .dbf) and store them in one of the following locations:
$FXA_HOME/data/localizationDataSets/LLL
$FXA_HOME/data.

(If you expect that a localization may be done during the lifetime of this shapefile as a user shapefile, DO NOT put it in $FXA_HOME/data/localizationDataSets/LLL as it will be deleted).
Step 3: Cd to $FXA_HOME/data/localization/nationalData.
Step 4: Make a backup copy of dataInfo.manual.
Step 5: Edit dataInfo.manual.
Step 6: Scroll down or search until you come to the section where the number in the first column is 1311. This is where the information about shapefiles is to be added.
Here is a section of dataInfo.manual with the user shapefile section untouched. 
 1311 |        |  |   |  |        |  |NAME              |userFile1  |     |user shape file map 1 |
 1312 |        |  |   |  |        |  |NAME              |userFile2  |     |user shape file map 2 |
 1313 |        |  |   |  |        |  |NAME              |userFile3  |     |user shape file map 3 |
 1314 |        |  |   |  |        |  |LAT,LON,NAME      |userFile4  |     |user shape file map 4 |
 1315 |        |  |   |  |        |  |LAT,LON,NAME      |userFile5  |     |user shape file map 5 |
Step 7: The second non blank field will contain NAME or LAT,LON,NAME. If the shapefile you are adding is a line or polygon (e.g., roads or urban boundaries) then this field should be NAME. If the shapefile contains point data (e.g., mesonet sites) the field should read LAT,LON,NAME.
Step 8: The next field, which in the example reads userFileX, should be filled with the file name of the shapefile (i.e., MyShape).

The shapefiles are accessible from the Maps menu in the User Shape File submenu. There will be five product buttons, Map 1 through Map 5.
Step 9: To change the product buttons to a custom name, edit productButtonInfo.txt still in /nationalData. Go to the user shapefile section.
Here is the user shapefile section of productButtonInfo.txt: 
 1311     |   1311                           |Map 1                       |User Shp File Map 1        | 1
 1312     |   1312                           |Map 2                       |User Shp File Map 2        | 1
 1313     |   1313                           |Map 3                       |User Shp File Map 3        | 1
 1314     |   1314                           |Map 4                       |User Shp File Map 4        | 1
 1315     |   1315                           |Map 5                       |User Shp File Map 5        | 1
Step 10: Change Map 1 through Map 5 to the appropriate name.
Step 11: The final step is to run localization:
/awips/fxa/data/localization/scripts/mainScript.csh f -tables -maps

Return to the How do I add maps to AWIPS?
Return to the FAQ Webpage
Return to the AWIPS GIS Map Group Homepage