### channelEffectiveTimeOverlap

Matches if the channel effective time overlaps the given time range. This is generally used to avoid processing channels that did not yet exist, or were deactivated before a time range of interest. By default, SOD uses a channelEffectiveTimeOverlap configured with the event arm's time range. If all you want to do is make sure your channels are active during your events, that's already done.

### Example

    <channelEffectiveTimeOverlap>
      <startTime>20020701T00:00:00.001Z</startTime>
      <endTime>20021030T00:00:00.001Z</endTime>
    </channelEffectiveTimeOverlap>

### This consists of

<channelEffectiveTimeOverlap>

<startTime>
time
</startTime>
<endTime>
time
</endTime>
</channelEffectiveTimeOverlap>

### Places this can be found

In channel there is a choice between all of the following

- siteCode
- siteDepthRange
- siteEffectiveTimeOverlap
- siteArea
- siteBoxArea
- sitePolygonFile
- channelCode
- bandCode
- gainCode
- orientationCode
- sampling
- channelEffectiveTimeOverlap
- orientationRange
- orientationAzimuthRange
- orientationDipRange
- channelAND
- channelOR
- channelNOT
- externalChannelSubsetter
- hadDataLastWeek
- printlineChannelProcess
- responseWriter
- sacPoleZeroWriter
- stationHas
- alwaysSuccess
- hasResponse
- hasSensitivity
- repairSensitivity
- responseFilterType
- stageTransferType
- stageInputUnit
- stageOutputUnit
- clockId
- clockManufacturer
- clockModel
- clockSerial
- clockType
- dasId
- dasManufacturer
- dasModel
- dasSerial
- dasStyle
- sensorId
- sensorManufacturer
- sensorModel
- sensorSerial
- sensorNominalHighFreq
- sensorNominalLowFreq
- hasNegativeSensitivity
- isFlipped
- isGroupable
- channelScript