Swath Corridor and TLE validity date

[William Bourque]

While using the SpacecraftSwathCorridor feature, the user has to be very careful with its time sources.

If the timesource are outside the TLE validity range, then the following exception is generated:

!ENTRY ca.gc.asc_csa.apogy.core.environment.orbit.earth 4 0 2016-05-30 16:45:21.201
!MESSAGE SpacecraftSwathCorridorImpl: Start date is outside the validity range !
java.lang.Exception: Start date is outside the validity range !
Forward null
    at ca.gc.asc_csa.apogy.core.environment.orbit.earth.impl.SpacecraftSwathCorridorImpl.update(SpacecraftSwathCorridorImpl.java:887)
    at ca.gc.asc_csa.apogy.core.environment.orbit.earth.ui.impl.SpacecraftSwathWorldWindLayerImpl$1.run(SpacecraftSwathWorldWindLayerImpl.java:961)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
java.lang.NullPointerException
    at ca.gc.asc_csa.apogy.core.environment.orbit.earth.ui.impl.SpacecraftSwathWorldWindLayerImpl$1.run(SpacecraftSwathWorldWindLayerImpl.java:970)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Apogy Planner() allow going outside the TLE validity range. As such, Swath (and possibly all the other orbital viewing tools) should allow it as well and avoid raising an Exception in those case.