When you specify the FORMAT=KMZ option, the SASENOAA interface engine requests the SWDI data in KMZ format. This results in the retrieval of a zipped KML file, which is then unzipped, saved with the .kml extension, and named by the OUTKMZ= option. In addition, the corresponding KMZ file is saved in the location specified by the fully qualified file name given in the KMZMAP= option. You can then use virtual globe software provided by Google Maps to import your KML data so that you can visualize the results both geospatially and timewise by holding the mouse pointer over each data point to see the variable values that correspond to the requested NOAA data set.
When you specify the FORMAT=SHP option, the SASENOAA engine requests the SWDI data in SHP format. This results in the retrieval of a zipped SHP file, which is then unzipped; the four resulting files are saved with the extensions .dbf, .prj, .shp, and .shx and named by the OUTSHP= option. In addition, the corresponding SHP ZIP file is saved in the location that is specified by the fully qualified file name given in the SHPMAP= option. You can then use virtual globe software such as SAS Bridge for Esri or use PROC MAPIMPORT and PROC GMAP to map your results.
The KMZ map (by default) is automatically created and placed in the file that is named by the fully qualified file name specified in the KMZMAP= option of the LIBNAME libref SASENOAA statement. The SASENOAA interface engine invokes PROC HTTP to create the map and to read the KMZ data into SAS.
The SAS KMZ (zipped KML format) data that are returned by the NOAA SWDI web service are placed in a file that is named by the OUTKMZ= option. The SASENOAA interface engine unzips the KMZ file and creates a separate KML file for each SASENOAA engine libref. The SAS KML data file is given the name specified by the OUTKMZ= option and is placed in the location that is specified by the physical-name in your LIBNAME libref SASENOAA statement, which is described in the section The LIBNAME libref SASENOAA Statement.
The SAS SHP (zipped Esri shapefiles format) data that are returned by the NOAA SWDI web service are placed in a file that is named by the OUTSHP= option. The SASENOAA interface engine creates a separate SHP ZIP file for each SASENOAA engine libref. The SASENOAA engine unzips the SHP data file, creating four files that are given the name specified by the OUTSHP= option plus the four file extensions (.dbf, .prj, .shp, and .shx). The four files are saved in the location that is specified by the physical-name in your LIBNAME libref SASENOAA statement, which is described in the section The LIBNAME libref SASENOAA Statement.
The SHP map (by default) is automatically created and placed in the file that is named by the fully qualified file name specified in the SHPMAP= option of the LIBNAME libref SASENOAA statement. The SASENOAA interface engine invokes PROC HTTP to create the map and to read the SHP data into SAS.