New Routes Implementation. fixes #19

[hunterowens]

This change replaces start_point, end_point and associated field with routes, a new datatype which is a geojson list of points to represent the route a device took during a trip.

[hunterowens]

@dmklinger @thekaveman does this meet your needs?

[thekaveman]

This leaves start_time and end_time as part of the Trip structure, where we assume this data would also be captured as part of the first/last points in the new Route object, correct?

In #19, @dmklinger suggests removing these time fields. I can see the benefit of not having to dive into the geoJSON to get these two values, but they may be duplicative. Were they intentionally left as part of the Trip object? Perhaps these represent when the vehicle was locked/unlocked by the user, vs. when the vehicle actually started moving?

[hunterowens]

@thekaveman / @dmklinger do we have resolution on this?

[dmklinger]

looks good to me