On Wed, May 29, 2019 at 3:42 PM David Sutherland wrote: > > Hi Alexandra, > > Some of this info is hard to find quickly and would require me tracking down the owners (who are both in Alaska and hard to reach!). Ive attempted some info the best I can below. > > MV Steller > built: 1978 > length: 70 > call sign: - > Owner: Dan Foley (cell: 907-723-2371) > MMSI: - > IMO number: 8886955 > > MV Pelican > built: > length: 25 landing craft > call sign: - > Owner: Scott Hursey (cell: 907-518-0013) > MMSI: - > IMO number: > The Pelican in particular is not really a research boat and is a small landing craft. ---------- Forwarded message --------- From: David Sutherland Date: Sat, May 25, 2019 at 5:05 PM Subject: Re: Submission Package Reference ID: WL01P3 To: Alexandra Grodsky - NOAA Affiliate Okay, great. I added the files to the ftp pub/incoming directory. I did not update the multibeam.nc file and would like to just link to that file on my github if possible. That link is: https://github.com/das7105/LeConteMultibeam_2016_2017 Thanks! Dave Sutherland - oceanice.org University of Oregon > On May 25, 2019, at 10:11 AM, Alexandra Grodsky - NOAA Affiliate wrote: > > Hi David, > (1) FTP is OK. > (2) NCEI requires actual coordinates. I think that switching to double > precision would allow for enough accuracy. Also, please include a > proper description of Z in a long_name attribute. If you choose to > keep this file separate as is, we will remove it from dataset content > and include a link to it. > --Alexandra > > On Sat, May 25, 2019 at 12:14 PM Dave Sutherland wrote: >> >> Hi Alexandra, >> >> Thanks! I can fix 1 and 3. For item 2, the file is bathymetry but its of a tidewater glacier front, ie not the sea floor. To keep more precision it made sense to keep the x/y positions in UTM coordinates and not geographical. Is that possible in NCEI? If not I can post them on GitHub or something. >> >> Im happy to send the corrected files the easiest way for you. Is that FTP? Let me know, thanks! >> >> Dave From: Alexandra Grodsky - NOAA Affiliate Date: Sat, May 25, 2019 at 10:55 AM Subject: Submission Package Reference ID: WL01P3 To: David Sutherland Dear David, thank you very much for submitting data to the NOAA/NCEI. Unfortunately, I can't proceed with this dataset until the following issues fixed (1) All netcdfs have lon in degrees_west. Longitude MUST be in degrees_east (-180 to +180, jump at the date change line). Some files have wrong longitudes (+132 instead of -132) float lon(profile) ; lon:long_name = "longitude" ; lon:units = "degrees_west" ; lon:standard_name = "longitude" ; lon:axis = "X" ; ncdump -v lon LeConte_Aug2016_Pelican600kHz_ADCP_data.nc |head -100 ncdump -v lon LeConte_May2017_Pelican150kHz_ADCP_data.nc |head -100 (2) Convert x,y distances into geographical coordinates in file LeConte_Aug2016_May2017_Multibeam_Data.nc This file includes only x,y,z and is missing any data. Explain the purpose of this file. (3) the last coordinate in LeConte_May2017_Pelican600kHz_ADCP_data.nc have NaNf. Please remove unknown coordinates. --------------------- Because data files are large, I see the following ways forward * reject this data, then you will resubmit with corrected files *put corrected files on your ftp * put corrected files on NCEI ftp see instructions at https://www.nodc.noaa.gov/submit/submission_alternatives.html Please let me know. Best, --Alexandra From: Alexandra Grodsky - NOAA Affiliate Date: Monday, September 9, 2019 at 11:49 AM To: "Eidam, Emily" Subject: Submission Package Reference ID: H1CMAX Dear Emily, your data files contain longitudes with wrong sign. Please correct longitudes and also remove data with unknown (NaN) coordinates/dates. Given the volume of files, I'll request rejection of the current package and ask you to resubmit it subject to the above corrections. Thanks, --Alexandra From: Eidam, Emily Date: Mon, Sep 30, 2019 at 9:36 AM Subject: Re: Submission Package Reference ID: H1CMAX To: Alexandra Grodsky - NOAA Affiliate I just uploaded five .nc files to the ftp site (under incoming): LeConte_Jul2017_CTD_data.nc LeConte_May2017_CTD_data_withTurbidity.nc LeConte_Sep2017_CTD_data.nc LeConte_Jul2017_Pelican600kHz_ADCP_data.nc LeConte_Sep2017_Pelican600kHz_ADCP_data.nc Thanks! Emily From: Eidam, Emily Date: Wed, Aug 19, 2020 at 1:03 PM Subject: Re: Submission Package Reference ID: H1CMAX To: Alexandra Grodsky - NOAA Affiliate Hi Alexandra, I would like to upload new data to this existing accession number (0189574). What is the best way to go about that? Should I start a new submission and simply add that number in the notes? Thanks for your help, Emily