### fullDataCoverage

This processor checks the data returned from the dataCenter for complete coverage of the original request. If from the begin time of the earliest piece is before the start of the request, and the end time of the latest piece is past the end of the request, the data passes. This does not guarantee that there are no gaps in the middle of the request though. To ensure that, combine this processor with a noDataGaps processor in a seismogramAND.

### Example

    <fullDataCoverage/>

### This consists of

<fullDataCoverage/>

### Places this can be found

In seismogramProcess there is a choice between all of the following

- printlineSeismogramProcess
- sacWriter
- mseedWriter
- asciiWriter
- wavWriter
- recordSectionDisplayGenerator
- responseGain
- phaseCut
- requestCut
- merge
- gapFill
- rMean
- rTrend
- taper
- externalWaveformProcess
- seismogramScript
- localSeismogramTemplateGenerator
- filter
- rms
- oregonDSPFilter
- forkProcess
- alwaysSuccess
- phaseSignalToNoise
- compoundPhaseSignalToNoise
- seismogramImageProcess
- legacyExecute
- seismogramAND
- seismogramOR
- seismogramNOT
- someDataCoverage
- noDataGaps
- fullDataCoverage
- integrate
- differentiate
- transferResponse
- collapseOverlaps
- div
- mul
- invertFlippedChannels
- seismogramSampling
- decimate
- stddev
- rms
- mean
- minMax
- compressionType
- availableDataPlus