<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Mark, <div>GrADS is not going to be able to do what you want effortlessly. The data do not have linear X or Y axes, so GrADS will never consider it to be 'wrapping' the globe and won't convert longitudes for you. You will have to do some manipulation of the coordinate vaues yourself, outside of GrADS. </div><div><br></div><div>I would try to write out the data that you want with the original longitudes using sdfwrite, then create a 2nd netcdf file with a new variable that is lon-360 (or whatever conversion is necessary to get the range of values you require), then use ncdump/ncgen or one of the NCO tools to overwrite the coordinate data in your output file and create a 3rd netcdf file that meets your needs. </div><div><br></div><div>Another thing to try is to use lterp to regrid the data to a regular, linear, wrapping grid that is similar to the native grid. Defined grids will never 'wrap', but you might be able to sdfwrite the regridded data, then bring that back in, make it wrap and write it out again with your desired longitudes. Kludgey, but it might work. I think plan A in the previous paragraph will be simpler. </div><div><br></div><div>--Jennifer</div><div><br><div><div>On Apr 18, 2012, at 11:36 AM, Mark Hess wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div bgcolor="#ffffff" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font size="2" face="Arial">I should clarify. These are ocean current data retrieved as U & V vector components from the HYCOM oceanographic model. I am now getting the data directly from their server and then sub setting using the sdfwrite command. The script for the U component is below. The longitude parameter in the original data is 0-360 and opposed to -180 to 180, so if I 'set lon -121 -116' to extract an area off of Southern California, it will not work. Ultimately, what I need is an .nc file covering 32N-35N x 116W-121W for both the U and V vector components with the longitude in geographic or world format (i.e. -180 to 180). Just not sure how to convert from the original format. I can get the numbers I need by subtracting 360 from the lon value, but not sure how to do this in GrADS. The ncdump output from the file created by the .gs script below is attached. Any ideas you can offer are much appreciated.</font></div><div><font size="2" face="Arial"></font> </div><div><font size="2" face="Arial">'reinit'<br>'sdfopen<span class="Apple-converted-space"> </span><a href="http://tds.hycom.org/thredds/dodsC/datasets/global/GLBa0.08_rect/data/uvel/rarchv.2012_106_00_3zu.nc'">http://tds.hycom.org/thredds/dodsC/datasets/global/GLBa0.08_rect/data/uvel/rarchv.2012_106_00_3zu.nc'</a><br>*<br>* Save sub-sectioned NetCDF files<br>*<br>* Create Southern California .nc file<br>'q file'<br>'set gxout shaded'<br>'set lat 32 35'<br>'set lon 239 244'<br>'set lev 0'<br>'d u'<br>'define u = u'<br>'set sdfwrite hycom_u_socal.nc'<br>'sdfwrite u'<br>'quit'<br></font></div><div><font size="2" face="Arial"></font> </div><div><font size="2" face="Arial">Thanks.</font></div><div><font size="2" face="Arial"></font> </div><div><font size="2" face="Arial">Mark</font></div><div><font size="2" face="Arial"> </font></div><div><font size="2" face="Arial"></font> </div><div><font size="2" face="Arial"></font> </div><blockquote style="border-left-color: rgb(0, 0, 0); border-left-width: 2px; border-left-style: solid; padding-left: 5px; padding-right: 0px; margin-left: 5px; margin-right: 0px; "><div style="font: normal normal normal 10pt/normal arial; ">----- Original Message -----</div><div style="font: normal normal normal 10pt/normal arial; background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: rgb(228, 228, 228); background-position: initial initial; background-repeat: initial initial; "><b>From:</b><span class="Apple-converted-space"> </span><a title="jma@cola.iges.org" href="mailto:jma@cola.iges.org">Jennifer Adams</a></div><div style="font: normal normal normal 10pt/normal arial; "><b>To:</b><span class="Apple-converted-space"> </span><a title="gradsusr@gradsusr.org" href="mailto:gradsusr@gradsusr.org">GrADS Users Forum</a></div><div style="font: normal normal normal 10pt/normal arial; "><b>Sent:</b><span class="Apple-converted-space"> </span>Wednesday, April 18, 2012 8:20 AM</div><div style="font: normal normal normal 10pt/normal arial; "><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [gradsusr] Saving NetCDF lon parameter in geographic</div><div><br></div>Mark,<div>If your original data set "wraps" the globe, then it should work fine: </div><div><br></div><div>'sdfopen foo.nc</div><div>'set lon -180 180'</div><div>'define var'</div><div>'sdfwrite var'</div><div><br></div><div>If not, please send the output from ncdump -c on your original file, your script to generate a new netcdf file using sdfwrite, and the output from ncdump -c on your new netcdf file. Your GrADS version would be helpful too.</div><div><br></div><div>--Jennifer</div><div><br></div><div><div><div>On Apr 13, 2012, at 7:36 PM, Mark Hess wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Thanks Chuck - Looks like that validates my suspicion that I cannot change<span class="Apple-converted-space"> </span><br>the lon coordinates from the 0-360 to world coordinates 180 to -180 when<span class="Apple-converted-space"> </span><br>extracting a subset of the original file to a smaller .nc file. I'll<span class="Apple-converted-space"> </span><br>consider different options. Thanks. Mark.<br><br><br>----- Original Message -----<span class="Apple-converted-space"> </span><br>From: "Charles Seman" <<a href="mailto:charles.seman@noaa.gov">charles.seman@noaa.gov</a>><br>To: "GrADS Users Forum" <<a href="mailto:gradsusr@gradsusr.org">gradsusr@gradsusr.org</a>><br>Sent: Thursday, April 12, 2012 3:44 PM<br>Subject: Re: [gradsusr] Saving NetCDF lon parameter in geographic<br><br><br><blockquote type="cite">Mark,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The documentation at<br></blockquote><blockquote type="cite"><a href="http://grads.iges.org/grads/gadoc/gradcomdsdfwrite.html">http://grads.iges.org/grads/gadoc/gradcomdsdfwrite.html</a><span class="Apple-converted-space"> </span>states:<br></blockquote><blockquote type="cite">"By default, the output file will have a coordinate variable only for<br></blockquote><blockquote type="cite">varying dimensions in the defined variable; non-varying dimensions will<br></blockquote><blockquote type="cite">not appear as a coordinate variable with a size of 1. However, as of<br></blockquote><blockquote type="cite">version 2.0.a5, options have been added to the set sdfwrite command to<br></blockquote><blockquote type="cite">force the variable in the output file to have at least 4 or all 5<br></blockquote><blockquote type="cite">dimensions. When either of these options to set sdfwrite are used, the<br></blockquote><blockquote type="cite">output file will retain information about the values of the dimensions<br></blockquote><blockquote type="cite">that were fixed when the variable was defined; non-varying dimensions<br></blockquote><blockquote type="cite">will appear as a coordinate variable of size 1. For example, if your<br></blockquote><blockquote type="cite">defined variable is 500mb height on14may2002 (a 2D variable that varies<br></blockquote><blockquote type="cite">only in lon and lat), and you use the -4d option, the output file with<br></blockquote><blockquote type="cite">show height as a 4D variable with a Z dimension of size 1 called 'lev'<br></blockquote><blockquote type="cite">with a value "500 mb", and a T dimension of size 1 called 'time' with a<br></blockquote><blockquote type="cite">value of "0 minutes since 2002-05-14 00:00".<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Seems the key phrase seems to be "the output file will retain<br></blockquote><blockquote type="cite">information about the values of the dimensions that were fixed when the<br></blockquote><blockquote type="cite">variable was defined"... I confirmed what I thought this meant on a file<br></blockquote><blockquote type="cite">which has grid longitudes in the -180 to 180 range and found the<br></blockquote><blockquote type="cite">following results:<br></blockquote><blockquote type="cite">--------------------------------------------------------------------<br></blockquote><blockquote type="cite">...using "native" longitude range:<br></blockquote><blockquote type="cite">ga-> sdfopen 3B42.1002.V6.nc<br></blockquote><blockquote type="cite">Scanning self-describing file: 3B42.1002.V6.nc<br></blockquote><blockquote type="cite">SDF file 3B42.1002.V6.nc is open as file 1<br></blockquote><blockquote type="cite">LON set to 0 360<br></blockquote><blockquote type="cite">LAT set to -49.875 49.875<br></blockquote><blockquote type="cite">LEV set to 0 0<br></blockquote><blockquote type="cite">Time values set: 2010:2:14:22 2010:2:14:22<br></blockquote><blockquote type="cite">E set to 1 1<br></blockquote><blockquote type="cite">ga-> q file<br></blockquote><blockquote type="cite">File 1 : NASA TRMM 3B42 3-Hourly 0.25 degree TRMM and Other Satellites<br></blockquote><blockquote type="cite">Precipitation Product (Version 6)<br></blockquote><blockquote type="cite"> Descriptor: 3B42.1002.V6.nc<br></blockquote><blockquote type="cite"> Binary: 3B42.1002.V6.nc<br></blockquote><blockquote type="cite"> Type = Gridded<br></blockquote><blockquote type="cite"> Xsize = 1440 Ysize = 400 Zsize = 1 Tsize = 1 Esize = 1<br></blockquote><blockquote type="cite"> Number of Variables = 2<br></blockquote><blockquote type="cite"> precipitation 0 t,y,x precipitation<br></blockquote><blockquote type="cite"> relativeerror 0 t,y,x relativeError<br></blockquote><blockquote type="cite">ga-> set lon -180 180<br></blockquote><blockquote type="cite">LON set to -180 180<br></blockquote><blockquote type="cite">ga-> set lat -90 90<br></blockquote><blockquote type="cite">LAT set to -90 90<br></blockquote><blockquote type="cite">ga-> set sdfwrite precipitation.3B42.1002.V6.nc<br></blockquote><blockquote type="cite">SDFWrite file name = precipitation.3B42.1002.V6.nc<br></blockquote><blockquote type="cite">SDFWrite will replace an existing file<br></blockquote><blockquote type="cite">ga-> sdfwrite precipitation<br></blockquote><blockquote type="cite">SDFWRITE error: no defined variables<br></blockquote><blockquote type="cite">ga-> define precipitation = precipitation<br></blockquote><blockquote type="cite">Define memory allocation size = 8328992 bytes<br></blockquote><blockquote type="cite">ga-> sdfwrite precipitation<br></blockquote><blockquote type="cite">Wrote variable precipitation to precipitation.3B42.1002.V6.nc<br></blockquote><blockquote type="cite">...<br></blockquote><blockquote type="cite">cjs: /tmp/data/precip/trmm/3B42.V6/pp/0.25x0.25/av/monthly/update/ --><br></blockquote><blockquote type="cite">\ncdump -c precipitation.3B42.1002.V6.nc<br></blockquote><blockquote type="cite">netcdf precipitation.3B42.1002.V6 {<br></blockquote><blockquote type="cite">dimensions:<br></blockquote><blockquote type="cite"> longitude = 1442 ;<br></blockquote><blockquote type="cite"> latitude = 722 ;<br></blockquote><blockquote type="cite">...<br></blockquote><blockquote type="cite">longitude = -180.125,...,180.125<br></blockquote><blockquote type="cite">latitude = -90.125,...,90.125<br></blockquote><blockquote type="cite">...<br></blockquote><blockquote type="cite">...so the output file runs from longitude = -180.125 to 180.125 and from<br></blockquote><blockquote type="cite">latitude = -90.125 to 90.125 (a couple extra points added in each<br></blockquote><blockquote type="cite">direction, so be careful)<br></blockquote><blockquote type="cite">--------------------------------------------------------------------<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">--------------------------------------------------------------------<br></blockquote><blockquote type="cite">...using a "global" longitude range, using x,y coordinates to define<br></blockquote><blockquote type="cite">exact boundaries:<br></blockquote><blockquote type="cite">ga-> sdfopen 3B42.1002.V6.nc<br></blockquote><blockquote type="cite">Scanning self-describing file: 3B42.1002.V6.nc<br></blockquote><blockquote type="cite">SDF file 3B42.1002.V6.nc is open as file 1<br></blockquote><blockquote type="cite">LON set to 0 360<br></blockquote><blockquote type="cite">LAT set to -49.875 49.875<br></blockquote><blockquote type="cite">LEV set to 0 0<br></blockquote><blockquote type="cite">Time values set: 2010:2:14:22 2010:2:14:22<br></blockquote><blockquote type="cite">E set to 1 1<br></blockquote><blockquote type="cite">...<br></blockquote><blockquote type="cite">ga-> set y 1 400<br></blockquote><blockquote type="cite">LAT set to -49.875 49.875<br></blockquote><blockquote type="cite">ga-> set x 721 2160<br></blockquote><blockquote type="cite">LON set to 0.125 359.875<br></blockquote><blockquote type="cite">ga-> set sdfwrite precipitation.3B42.1002.V6.nc<br></blockquote><blockquote type="cite">SDFWrite file name = precipitation.3B42.1002.V6.nc<br></blockquote><blockquote type="cite">SDFWrite will replace an existing file<br></blockquote><blockquote type="cite">ga-> define precipitation = precipitation<br></blockquote><blockquote type="cite">Define memory allocation size = 4608000 bytes<br></blockquote><blockquote type="cite">ga-> sdfwrite precipitation<br></blockquote><blockquote type="cite">Wrote variable precipitation to precipitation.3B42.1002.V6.nc<br></blockquote><blockquote type="cite">cjs: /tmp/data/precip/trmm/3B42.V6/pp/0.25x0.25/av/monthly/update/ --><br></blockquote><blockquote type="cite">\ncdump -c precipitation.3B42.1002.V6.nc<br></blockquote><blockquote type="cite">netcdf precipitation.3B42.1002.V6 {<br></blockquote><blockquote type="cite">dimensions:<br></blockquote><blockquote type="cite"> longitude = 1440 ;<br></blockquote><blockquote type="cite"> latitude = 400 ;<br></blockquote><blockquote type="cite">longitude = 0.125,...,359.875<br></blockquote><blockquote type="cite">latitude = -49.875,...,49.875<br></blockquote><blockquote type="cite">...<br></blockquote><blockquote type="cite">...so the output file runs from longitude = 0.125,...,359.8755 and from<br></blockquote><blockquote type="cite">latitude = -49.875,...,49.875<br></blockquote><blockquote type="cite">--------------------------------------------------------------------<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Could you try defining the variable to sdfwrite using parameters<br></blockquote><blockquote type="cite">appropriate to the netCDF file's original grid?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hope this helps,<br></blockquote><blockquote type="cite">Chuck<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 04/12/2012 03:57 PM, Mark Hess wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">I have a NetCDF file which I can ingest and display in GrADS with out a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">problem. The LON parameter is set to a 0-360 grid as opposed to 0-180W &<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">0-180E (or 0 to 180 for east and 0 to -180 for west). If I "set lon 239<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">244" and then display my variable of interest (in this case U), the data<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">display properly showing the data between 116W-121W (116W equaling<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-116=244-360 and 121W equaling -121=360-239). That all is fine until I<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">try to save my geographically subsetted area to a new .nc file using the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">sdfwrite function. The file saves fine, but it saves the LON information<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">in the 0-360 format instead of the 0 to -180 format which I need for<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">another application. Is there a way to either 1) save the new, subsetted<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">.nc file with the lons converting to the in 0 to -180 format as part of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the process or 2) convert the lon format within GrADS first and then<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">save the new .nc file with the lon values in the format I want? Can I<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">subtract 360 from my "lon" variable to create a 'new' lon variable?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Thanks,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Mark<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">gradsusr mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="mailto:gradsusr@gradsusr.org">gradsusr@gradsusr.org</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://gradsusr.org/mailman/listinfo/gradsusr">http://gradsusr.org/mailman/listinfo/gradsusr</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">--<span class="Apple-converted-space"> </span><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Please note that<span class="Apple-converted-space"> </span><a href="mailto:Charles.Seman@noaa.gov">Charles.Seman@noaa.gov</a><span class="Apple-converted-space"> </span>should be considered my NOAA<br></blockquote><blockquote type="cite">email address, not<span class="Apple-converted-space"> </span><a href="mailto:cjs@gfdl.noaa.gov">cjs@gfdl.noaa.gov</a>.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">********************************************************************<br></blockquote><blockquote type="cite">Charles Seman <a href="mailto:Charles.Seman@noaa.gov">Charles.Seman@noaa.gov</a><br></blockquote><blockquote type="cite">U.S. Department of Commerce / NOAA / OAR<br></blockquote><blockquote type="cite">Geophysical Fluid Dynamics Laboratory voice: (609) 452-6547<br></blockquote><blockquote type="cite">201 Forrestal Road fax: (609) 987-5063<br></blockquote><blockquote type="cite">Princeton, NJ 08540-6649 <a href="http://www.gfdl.noaa.gov/~cjs/">http://www.gfdl.noaa.gov/~cjs/</a><br></blockquote><blockquote type="cite">********************************************************************<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">"The contents of this message are mine personally and do not reflect any<br></blockquote><blockquote type="cite">official or unofficial position of the United States Federal Government,<br></blockquote><blockquote type="cite">the United States Department of Commerce, or NOAA."<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">gradsusr mailing list<br></blockquote><blockquote type="cite"><a href="mailto:gradsusr@gradsusr.org">gradsusr@gradsusr.org</a><br></blockquote><blockquote type="cite"><a href="http://gradsusr.org/mailman/listinfo/gradsusr">http://gradsusr.org/mailman/listinfo/gradsusr</a><span class="Apple-converted-space"> </span><br></blockquote><br>_______________________________________________<br>gradsusr mailing list<br><a href="mailto:gradsusr@gradsusr.org">gradsusr@gradsusr.org</a><br><a href="http://gradsusr.org/mailman/listinfo/gradsusr">http://gradsusr.org/mailman/listinfo/gradsusr</a><br></div></blockquote></div><br><div apple-content-edited="true"><span class="Apple-style-span" style="widows: 2; text-transform: none; text-indent: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; border-collapse: separate; font: normal normal normal 12px/normal Helvetica; white-space: normal; orphans: 2; letter-spacing: normal; word-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; "><span class="Apple-style-span" style="widows: 2; text-transform: none; text-indent: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; border-collapse: separate; font: normal normal normal 12px/normal Helvetica; white-space: normal; orphans: 2; letter-spacing: normal; word-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; "><span class="Apple-style-span" style="widows: 2; text-transform: none; text-indent: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; border-collapse: separate; font: normal normal normal 12px/normal Helvetica; white-space: normal; orphans: 2; letter-spacing: normal; word-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; "><div>--</div><div>Jennifer M. Adams</div><div>IGES/COLA</div><div>4041 Powder Mill Road, Suite 302</div><div>Calverton, MD 20705</div><div><a href="mailto:jma@cola.iges.org">jma@cola.iges.org</a></div><div><br class="khtml-block-placeholder"></div><br class="Apple-interchange-newline"></span></span></span></div><br></div><div><br class="webkit-block-placeholder"></div><hr><div><br class="webkit-block-placeholder"></div>_______________________________________________<br>gradsusr mailing list<br><a href="mailto:gradsusr@gradsusr.org">gradsusr@gradsusr.org</a><br><a href="http://gradsusr.org/mailman/listinfo/gradsusr">http://gradsusr.org/mailman/listinfo/gradsusr</a><br></blockquote><span><hycom_u_socal.ncdump></span>_______________________________________________<br>gradsusr mailing list<br><a href="mailto:gradsusr@gradsusr.org">gradsusr@gradsusr.org</a><br><a href="http://gradsusr.org/mailman/listinfo/gradsusr">http://gradsusr.org/mailman/listinfo/gradsusr</a><br></div></span></blockquote></div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div>--</div><div>Jennifer M. Adams</div><div>IGES/COLA</div><div>4041 Powder Mill Road, Suite 302</div><div>Calverton, MD 20705</div><div><a href="mailto:jma@cola.iges.org">jma@cola.iges.org</a></div><div><br class="khtml-block-placeholder"></div><br class="Apple-interchange-newline"></span></span></span>
</div>
<br></div></body></html>