<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Spase xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.spase-group.org/data/schema" xsi:schemaLocation="http://www.spase-group.org/data/schema http://www.spase-group.org/data/schema/spase-2_2_0.xsd">
  <Version>2.2.0</Version>
  <NumericalData>
    <ResourceID>spase://VMO/NumericalData/GOES/1/EPM/PT3S</ResourceID>
    <ResourceHeader>
      <ResourceName>GOES 1 Energetic Particle Monitor at 3 sec Resolution</ResourceName>
      <AlternateName>GOES 1 EPM data</AlternateName>
      <ReleaseDate>2011-11-17T00:50:58Z</ReleaseDate>
      <Description>The GOES 1 EPM data set contains various parameters at 3 s resolution. Within the data files is the time given as seconds of the month where the date is given in the filename, a flag word that provides information on the data and satellite command state in a flagword, and the measured counts for a subset of available channels, which are indicated by the flagword.</Description>
      <Acknowledgement>NOAA Environmental Research Laboratories; Dr. Harold Leinbach; Dr. Herbert H. Sauer; Dr. Terry Onsager</Acknowledgement>
      <Contact>
        <PersonID>spase://SMWG/Person/Harold.Leinbach</PersonID>
        <Role>PrincipalInvestigator</Role>
      </Contact>
      <Contact>
        <PersonID>spase://SMWG/Person/Herbert.H.Sauer</PersonID>
        <Role>PrincipalInvestigator</Role>
      </Contact>
      <Contact>
        <PersonID>spase://SMWG/Person/Terry.Onsager</PersonID>
        <Role>PrincipalInvestigator</Role>
      </Contact>
      <Contact>
        <PersonID>spase://SMWG/Person/James.M.Weygand</PersonID>
        <Role>MetadataContact</Role>
      </Contact>
      <InformationURL>
        <Name>GOES 1 Energetic Particle Monitor</Name>
        <URL>http://nssdc.gsfc.nasa.gov/nmc/experimentDisplay.do?id=1975-100A-02</URL>
        <Description>Introduction to the GOES 1 Energetic Particle Monitor.</Description>
      </InformationURL>
      <InformationURL>
        <Name>GOES 1 Energetic Particle Monitor Data File Information</Name>
        <URL>http://goes.ngdc.noaa.gov/software/part.txt</URL>
        <Description>Additional GOES EPM information, e.g. the muliplex counter lookup table.</Description>
      </InformationURL>
      <InformationURL>
        <Name>GOES 1 Energetic Particle Monitor Additional Data File Information</Name>
        <URL>ftp://satdat.ngdc.noaa.gov/sem/goes/data/full/readme.txt</URL>
        <Description>Additional GOES EPM dtaa file information.</Description>
      </InformationURL>
      <PriorID>spase://VMO/NumericalData/GOES/1/EPM/HighRes/PT3S</PriorID>
      <PriorID>spase://VMO/NumericalData/GOES/1/EPM/PT3S</PriorID>
    </ResourceHeader>
    <AccessInformation>
      <RepositoryID>spase://SMWG/Repository/NOAA/SEC</RepositoryID>
      <Availability>Online</Availability>
      <AccessRights>Open</AccessRights>
      <AccessURL>
        <Name>Direct access to the GOES 1 EPM data</Name>
        <URL>ftp://satdat.ngdc.noaa.gov/sem/goes/data/full/particles/</URL>
        <Description>Direct link to the GOES 1 EPM data in FITS format as well as the energetic particle data from other GOES spacecraft. The data are sorted by year. The file names indicates the data type, spacecraft number, year, month, and resolution. For example, P0137607.FIT indicates particle data (P) for spacecraft 1 (01) at 3 second resolution (3) from July 1976 (7607). Note that spacecraft IDs 91 and 92 refer to SMS satellites, not GOES.</Description>
      </AccessURL>
      <Format>FITS</Format>
      <Encoding>None</Encoding>
      <Acknowledgement>NOAA Environmental Research Laboratories; Dr. Harold Leinbach; Dr. Herbert H. Sauer; Dr. Terry Onsager</Acknowledgement>
    </AccessInformation>
    <ProcessingLevel>Calibrated</ProcessingLevel>
    <ProviderResourceName>NOAA GOES 1 EPM</ProviderResourceName>
    <ProviderProcessingLevel>Level-2</ProviderProcessingLevel>
    <InstrumentID>spase://SMWG/Instrument/GOES/1/EPM</InstrumentID>
    <MeasurementType>EnergeticParticles</MeasurementType>
    <TemporalDescription>
      <TimeSpan>
        <StartDate>1976-01-01T00:00:00</StartDate>
        <StopDate>1978-05-31T00:00:00</StopDate>
        <Note>Time format in data files is seconds of the month. The year and month are derived from the file name.</Note>
      </TimeSpan>
      <Cadence>PT3S</Cadence>
    </TemporalDescription>
    <Caveats>Flags=32711000</Caveats>
    <Keyword>3 sec</Keyword>
    <Keyword>geosynchronous</Keyword>
    <Keyword>GOES</Keyword>
    <Keyword>energetic particle monitor</Keyword>
    <Keyword>energetic particles</Keyword>
    <Parameter>
      <Name>Seconds of the Month</Name>
      <ParameterKey>Time</ParameterKey>
      <Description>Time is given as seconds of the month. The year and month values are derived from the filename.</Description>
      <Cadence>PT3S</Cadence>
      <Support>
        <SupportQuantity>Temporal</SupportQuantity>
      </Support>
    </Parameter>
    <Parameter>
      <Name>Flag Word</Name>
      <ParameterKey>Flag Word</ParameterKey>
      <Description>The flag word contains packed information about the data such as the multiplex counter, data processing error flag, the satellite command state, and archive version number. The multiplex counter value indicates the 3 data channels from which the counts per second are recorded. Because the multiplex counter can change every 3 sec is is not possible to give the data channel, energy range, and other information in the next 3 parameters. To calculate the multiplex counter, multiplex counter = flagword mod 16. With the multiplex counter use the look up table at see http://goes.ngdc.noaa.gov/software/part.txt to determine the energy channels, the associated particle, and the energy range.</Description>
      <Support>
        <SupportQuantity>Other</SupportQuantity>
      </Support>
    </Parameter>
    <Parameter>
      <Name>GOES 1 EPM 2-Channel Multiplexer at 3 s Resolution</Name>
      <ParameterKey>MPX2</ParameterKey>
      <Description>These data are the measured counts per sec from the data in 2nd channel identified by multiplex counter given in the flagword. </Description>
      <Caveats>The user must know what the multiplex count value is from the flagword</Caveats>
      <Units>counts/second</Units>
      <Particle>
        <ParticleType>Proton</ParticleType>
        <ParticleType>Electron</ParticleType>
        <Qualifier>Scalar</Qualifier>
        <ParticleQuantity>Counts</ParticleQuantity>
      </Particle>
    </Parameter>
    <Parameter>
      <Name>GOES 1 EPM 4-Channel Multiplexer at 3 s Resolution</Name>
      <ParameterKey>MPX4</ParameterKey>
      <Description>These data are the measured counts per sec from the data in 2nd channel identified by multiplex counter given in the flagword. </Description>
      <Caveats>The user must know what the multiplex count value is from the flagword</Caveats>
      <Units>counts/second</Units>
      <Particle>
        <ParticleType>Proton</ParticleType>
        <ParticleType>Electron</ParticleType>
        <Qualifier>Scalar</Qualifier>
        <ParticleQuantity>Counts</ParticleQuantity>
      </Particle>
    </Parameter>
    <Parameter>
      <Name>GOES 1 EPM 8-Channel Multiplexer at 3 s Resolution</Name>
      <ParameterKey>MPX8</ParameterKey>
      <Description>These data are the measured counts per sec from the data in 2nd channel identified by multiplex counter given in the flagword. </Description>
      <Caveats>The user must know what the multiplex count value is from the flagword</Caveats>
      <Units>counts/second</Units>
      <Particle>
        <ParticleType>Proton</ParticleType>
        <ParticleType>Electron</ParticleType>
        <Qualifier>Scalar</Qualifier>
        <ParticleQuantity>Counts</ParticleQuantity>
      </Particle>
    </Parameter>
  </NumericalData>
</Spase>
