Or, at least that’s what I am calling it. The .NET framework provides quite a rich set of data structures for dealing with Dates. You’ve got DateTime which represents a single point in time, You’ve got TimeSpan which represents a interval.
However I noticed something somewhat absent- a DateTime Range, with a start time, and an ending time. This came about because I required a way to coalesce a set of DateTime’s organized as Starting and Ending time so that there weren’t any overlaps. For example, if I had datetimes for one interval from 9AM to 12PM, another from 8AM to 11AM, and a third from 5PM to 9PM, the coalesced result would be two intervals, one from 8AM to 12PM, and one from 5PM to 9PM. Basically, the point was to “simplify” a set of datetime intervals so that overlapping time would not be counted.
At first, I figured it would be built-in functionality of one of the DateTime classes. It’s not. so I did some googling, no real luck there either. So, I decided to write my own “DateRange” class that encapsulated a Start Time and an Ending time and had the functionality I required.
Obviously, the first thing we know is that the class is going to need Starting Time and Ending Time. Of course, once we’ve defined the data structures, the tricky part will be the “coalescing” code. The implementations for which can be found in the “CoalesceRanges” and “Coalesce” methods.
-
-
public class DateRange : ICloneable
-
-
{
-
-
-
-
private DateTime _StartTime, _EndTime;
-
-
-
-
public DateTime StartTime { get { return _StartTime;}}
-
-
public DateTime EndTime { get { return _EndTime; }}
-
-
-
-
public TimeSpan Span
-
-
{
-
-
get {
-
-
-
-
return EndTime-StartTime;
-
-
}
-
-
set {
-
-
_EndTime = StartTime+value;
-
-
-
-
}
-
-
-
-
}
-
-
public DateRange(DateTime sTime, DateTime eTime)
-
-
{
-
-
if (sTime < eTime) _StartTime = sTime; else _StartTime=eTime;
-
-
if (sTime > eTime) _EndTime = sTime; else _EndTime=eTime;
-
-
-
-
-
-
}
-
-
public override string ToString()
-
-
{
-
-
return "Range:(" + StartTime.ToString() + ")-(" + EndTime.ToString() + ")";
-
-
}
-
-
public static DateRange [] Coalesce(DateRange RangeA, DateRange RangeB)
-
-
{
-
-
bool CondA = RangeA.StartTime > RangeB.EndTime;
-
-
bool CondB = RangeA.EndTime < RangeB.StartTime;
-
-
bool overlaps = !(CondA || CondB);
-
-
-
-
-
-
// bool overlaps = (RangeA.StartTime > RangeB.EndTime) && (RangeA.EndTime < RangeB.StartTime);
-
-
-
-
//overlap exists if neither A or B is true.
-
-
if (overlaps)
-
-
{
-
-
//overlap exists.
-
-
//create a new starttime the lower of the given two…
-
-
DateTime newstart, newEnd;
-
-
-
-
if (RangeA.StartTime < RangeB.StartTime) newstart = RangeA.StartTime; else newstart = RangeB.StartTime;
-
-
if (RangeA.EndTime > RangeB.EndTime) newEnd = RangeA.EndTime; else newEnd = RangeB.EndTime;
-
-
-
-
return new DateRange [] { new DateRange(newstart, newEnd) };
-
-
-
-
}
-
-
else
-
-
{
-
-
//there is no overlap, return a daterange array with both the same elements.
-
-
return new DateRange [] { (DateRange)RangeA.Clone(), (DateRange)RangeB.Clone() };
-
-
-
-
}
-
-
-
-
-
-
}
-
-
-
-
public DateRange [] Coalesce(DateRange Otherdaterange)
-
-
{
-
-
-
-
return DateRange.Coalesce(this, Otherdaterange);
-
-
-
-
}
-
-
-
-
-
-
-
-
-
-
public static DateRange [] CoalesceRanges(DateRange [] ranges)
-
-
{
-
-
//coalesces/simplifies a given set of date ranges to the simplest form. For example:
-
-
/* a
-
-
* |—-|
-
-
* b
-
-
* |—-| c
-
-
* |—-|
-
-
* */
-
-
//will return an array of two Dateranges:
-
-
-
-
/* a
-
-
* |—–|
-
-
* b
-
-
* |—-|
-
-
-
-
* */
-
-
//this is the "simplest" reduction of what the previous ranges were.
-
-
List<daterange> userange = ranges.ToList();
-
-
-
List<daterange> workalist = userange;
-
-
List<daterange> result = new List<daterange>();
-
-
-
-
-
-
//algorithm
-
-
//set a flag indicating a coalesce was discovered to true.
-
-
//iterate while said flag is true.
-
-
-
-
//set flag to false as loop begins.
-
-
//iterate through every possible pair X and Y in the List. skip iterations where X==Y.
-
-
-
-
//for each possible pairing:
-
-
//coalesce the two DateRanges. If the results coalesce (the return value array has a length of 1)
-
-
//mark x and y for removal, set the new Array to be AddRanged() to the List, and break out of both loops, and set the flag saying that
-
-
//a coalesce was discovered.
-
-
-
-
bool coalescefound =true;
-
-
while (coalescefound)
-
-
{
-
-
List<daterange> removalmarked = new List<daterange>();
-
-
List<daterange> addmarked = new List<daterange>();
-
-
bool breakouter=false;
-
-
coalescefound=false;
-
-
foreach (DateRange x in workalist)
-
-
{
-
-
foreach (DateRange y in workalist)
-
-
{
-
-
if (x != y)
-
-
{
-
-
DateRange [] coalresult = DateRange.Coalesce(x, y);
-
-
-
-
if (coalresult.Length == 1)
-
-
{
-
-
coalescefound=true;
-
-
//add new array to be added…
-
-
addmarked.AddRange(coalresult);
-
-
//remove both x and y. We can’t remove them here since we are iterating…
-
-
removalmarked.Add(x);
-
-
removalmarked.Add(y);
-
-
breakouter=true;
-
-
break;
-
-
-
-
}
-
-
-
-
-
-
-
-
}
-
-
-
-
-
-
}
-
-
-
-
if (breakouter) break; //break out of outer iterator if flag set.
-
-
-
-
}
-
-
//add and remove the marked items.
-
-
foreach (var removeme in removalmarked)
-
-
{
-
-
-
-
workalist.Remove(removeme);
-
-
-
-
}
-
-
foreach (var addme in addmarked)
-
-
{
-
-
workalist.Add(addme);
-
-
-
-
}
-
-
-
-
-
-
-
-
-
-
-
-
}
-
-
-
-
-
-
-
-
return workalist.ToArray();
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
}
-
-
-
-
public object Clone()
-
-
{
-
-
return new DateRange(StartTime, EndTime);
-
-
}
-
-
}
-
For this case I’ve decided that I would make the class Immutable. This should make our accessors simpler to implement. As a result, the StartTime and EndTime implementations only define get accessors. I also add a “Span” parameter that actually does change the EndTime in it’s setter, so I guess I lied. Oh well. Anyways, the meat of the class is in the various coalescing methods, which makes sense since that is what I sort of wrote the class to do. the class could surely be fleshed out with other, useful methods and properties, but as it is now it meets my own needs admirably so I’ve not really expanded it past what I’ve got here.
976 total views, 2 views today
Have something to say about this post? Comment!
Previous 
Next 
Categories
Tag Cloud
Blog RSS
Comments RSS
Last 50 Posts
Back
Void 
Life 
Earth 
Wind 
Water 
Fire 