-------- Original Message -------- Delivered-To: sheri.phillips@noaa.gov Received: by 10.182.214.134 with SMTP id oa6cs5214obc; Fri, 3 Feb 2012 05:36:53 -0800 (PST) Received: by 10.68.72.9 with SMTP id z9mr17562236pbu.124.1328276212561; Fri, 03 Feb 2012 05:36:52 -0800 (PST) Return-Path: Received: from psmtp.com ([74.125.149.54]) by mx.google.com with SMTP id h6si8207235pbn.27.2012.02.03.05.36.51 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 03 Feb 2012 05:36:52 -0800 (PST) Received-SPF: error (google.com: error in processing during lookup of erik.hund@noaa.gov: DNS timeout) client-ip=74.125.149.199; Authentication-Results: mx.google.com; spf=temperror (google.com: error in processing during lookup of erik.hund@noaa.gov: DNS timeout) smtp.mail=erik.hund@noaa.gov Received: from na3sys009aog108.obsmtp.com ([74.125.149.199]) (using TLSv1) by na3sys009amx214.postini.com ([74.125.148.10]) with SMTP; Fri, 03 Feb 2012 13:36:52 GMT Received: from mail-qy0-f174.google.com ([209.85.216.174]) (using TLSv1) by na3sys009aob108.postini.com ([74.125.148.12]) with SMTP ID DSNKTyvi82y7qbcxu+w03l+UKsy/24hM37gF@postini.com; Fri, 03 Feb 2012 05:36:52 PST Received: by mail-qy0-f174.google.com with SMTP id w6so2345947qcq.33 for ; Fri, 03 Feb 2012 05:36:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.77.69 with SMTP id f5mr2780204qck.12.1328276210760; Fri, 03 Feb 2012 05:36:50 -0800 (PST) Received: by 10.224.133.7 with HTTP; Fri, 3 Feb 2012 05:36:50 -0800 (PST) In-Reply-To: <4F2B31C5.20409@noaa.gov> References: <4F2ACB42.4060309@noaa.gov> <4F2B31C5.20409@noaa.gov> Date: Fri, 3 Feb 2012 08:36:50 -0500 Message-ID: Subject: Re: One more question! From: Erik Hund To: Sheri Phillips Cc: Yuanjie Li X-pstn-neptune: 0/0/0.00/0 X-pstn-levels: (S:99.90000/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 1 (0.1500:0.0150) cv GT3 gt2 gt1 r p m c X-pstn-addresses: from [db-null] X-pstn-nxpr: disp=neutral, envrcpt=sheri.phillips@noaa.gov X-pstn-nxp: bodyHash=8f07f4978d5758571abcf742f9b093f0b322c4e2, headerHash=e952d25c858d3d08f3b9409ac994ac41c6f942a3, keyName=4, rcptHash=e8c63c6534f24d9f6b7c194879bbc6db593c9f1d, sourceip=74.125.149.199, version=1 Content-Type: multipart/alternative; boundary=002354471184b4bd7c04b80f6711 Yes, you can delete those also. Erik On Thu, Feb 2, 2012 at 8:00 PM, Sheri Phillips wrote: Hi Erik Since it is not necessary to permanently archive the .ovr files, may I also delete the .rrd files from the final accession? Thank you, Sheri On 2/2/2012 1:01 PM, Erik Hund wrote: > Hi Sheri, > > Don't worry about archiving the .ovr files for geotiff or img files. They are created by EarthWhere, an image management software, and don't need to be archived. It is fine if you want to separate the South Carolina set into smaller sets. I agree that it would be difficult to download all at once. > > I am working on getting more data ready to send to you, probably by next week. > > Erik > > On Thu, Feb 2, 2012 at 12:43 PM, Sheri Phillips wrote: > > Hi Erik and Happy New Year! > > Hope it started on a good note. > > We are still working on accessioning the mosaic tile data for the archive - just some quick questions: > > 1) I have not been archiving the "pyramid" (.ovr) files as when the Geotiff files are opened on a local system, ArcGIS generates more .ovr files unless instructed otherwise > (though the program seems to really "want" to). It seems this would 1) Possibly confuse future users and 2) Take up a lot of space for a long-term archive product. > Is it OK to not archive these files - we are keeping everything else (e.g., .his, .tiff, and all other auxiliary files). Note that this is in reference to sets that contain Geotiffs. > We have not archived .ovr files in connection with other GIS products previously at the NODC. > > 2) EXCEPTION! I am working on the South Carolina set, which contains .IMG files. No-one at NODC has worked with this file type very much, so with these files should > we keep the .ovr files? We are trying to insure this ERDAS format will be readable and usable in the future. > > 3) Finally, the South Carolina set is enormous, after I decompress looks like all the file will run to about 750 GB - would it be OK to separate this into 5 different data accessions? > We try to keep all data together in a logical fashion, but in this case a user might have problems if they tried to download the entire South Carolina data set at one time. > We do not archive files in a compressed format. > > Thank you for advice on handling these data, and your time. > > Serhi > > > > > > -- > Erik Hund > NOAA Coastal Services Center > 2234 S. Hobson Ave. > Charleston, SC 29405-2413 > > 843 740-1280 > 843 740-1315 Fax > > email: erik.hund@noaa.gov -- Erik Hund NOAA Coastal Services Center 2234 S. Hobson Ave. Charleston, SC 29405-2413 843 740-1280 843 740-1315 Fax email: erik.hund@noaa.gov