CmnGEO-Anomaly-TLE

Data formats, HDF5, XML profiles, etc.
Post Reply
markgreenman
Posts: 9
Joined: Wed Jan 19, 2011 2:41 pm

CmnGEO-Anomaly-TLE

Post by markgreenman »

What is the source for the CmnGEO-Anomaly-TLE ?

What should this internal product contain?
What is the internal filename pattern?
What should the accompanying Metadata (.asc) file contain?

I believe from code inspection that the file should just be a TLE input.
Mark Greenman Computer Scientist IV
Space Dynamics Laboratory mark.greenman@sdl.usu.edu
1695 N Research Park Way 435.713.3336 T,W,F (SDL Office)
North Logan, UT 84341
kbisanz
Posts: 280
Joined: Wed Jan 05, 2011 7:02 pm
Location: Omaha NE

Re: CmnGEO-Anomaly-TLE

Post by kbisanz »

You are correct that the "group name" of CmnGeo-Anomaly-TLE refers to TLE with a collection short name of TLE-AUX-Int.

You can get TLE-AUX from CLASS. It's under the NP_AUX category.

TLE-AUX-Int is actually an "internal" version of the "normal" TLE. The normal TLE has 140 bytes. TLE-AUX-Int has 142 bytes. To "convert" TLE-AUX to TLE-AUX-Int, you can use a text editor to add a space at the end of each of the 2 lines in the file. I do not know the reasoning for that decision.

As far as the .asc file, if you downloaded any example data, you can find a TLE file and look at a sample .asc file.

Additionally, here is an example:

Code: Select all

("4e89df64-5b242-9b9dea83-ea2d2a09" UR "2011-10-03 16:14:28.000000"
 ("FILELIST" COLLECTION
  ("/runtime_PRO/tjensen/oracle/data//DmSm//Default/03_16/4e89df64-5b242-9b9dea83-ea2d2a09.TLE-AUX_npp_20090519000021Z_20030125000000Z_ee00000000000000Z_-_c3s-_ops_all-_ops.txt_Internal" FILE
   ("METADATALIST" COLLECTION)
  )
 )
 ("METADATALIST" COLLECTION
  ("DatasetLock" INTEGER EQ 0)
  ("Effectivity" DATETIMERANGE EQ "2003-01-25 00:00:00.000000" "2038-01-19 03:14:07.000000")
  ("N_Collection_Short_Name" STRING EQ "TLE-AUX-Int")
  ("N_Granule_Version" STRING EQ "A1")
  ("RangeDateTime" DATETIMERANGE EQ "2000-05-18 14:00:30.000000" "2038-01-19 03:14:07.000000")
  ("UpdateDateTime" DATETIME EQ "2011-10-03 16:14:28.373663")
  ("CreationDateTime" DATETIME EQ "2011-10-03 16:14:28.373651")
  ("Platform_Short_Name" STRING EQ "NPP")
  ("N_Dataset_Type_Tag" STRING EQ "AUX-Int")
  ("N_Dataset_Source" STRING EQ "AFWA")
  ("SourceDomain" STRING EQ "Ops")
  ("N_Processing_Domain" STRING EQ "OPS")
  ("Mission_Name" STRING EQ "NPP")
  ("N_Spacecraft_Maneuver" STRING EQ "Normal Operations")
  ("ObservedDateTime" DATETIMERANGE EQ "2000-05-18 14:00:30.000000" "2038-01-19 03:14:07.000000")
  ("N_Software_Version" STRING EQ "Unknown")
 )
)
Regarding the example, you can create a new URID using $ADL_HOME/tools/bin/UridCreator.exe. For the directory path, the file name ("4e89df64-5b242-9b9dea83-ea2d2a09.TLE-AUX_npp_20090519000021Z_20030125000000Z_ee00000000000000Z_-_c3s-_ops_all-_ops.txt_Internal") must match the file name of the data file on disk, but the directory path information does not matter. The code assumes the data file and the .asc file are in the same directory.

I believe I've answered your questions. Please reply back is something is not clear.
Kevin Bisanz
Raytheon Company
Post Reply