time dimension/time extent field with ranges and or periods not fully supported

[Joern Ungermann]

Some servers declare their supported times with a complicated, but documented format, where they define starting/ending times with periods in the middle. E.g. 1999-01-01/2000-08-22/P1D Currently, these things are not fully supported, especially if a period is specified in addition.

Ideally, the field is parsed and entered into the valid times field.

[Reimar Bauer]

@joernu76 can we move this to 1.9.0 ?

[Joern Ungermann]

Fine for me.