Suggestion: Replace start_point,end_point, start_time, end_time, route, and sample rate with route containing timestamp

[dmklinger]

First and last points in route are start and end; all points in route are marked with timestamps.

[dmklinger]

It would look something like this:

{
    "company_name": "ScooterCompany",
    "device_type": "scooter",
    "trip_id": 107384,
    "trip_duration": 124.8681321144104,
    "trip_distance": 321.869243535,
    "route": {
        "type": "FeatureCollection",
        "features": [
            {
                "type": "Feature",
                "properties": {
                    "timestamp": 1529968782.421409
                },
                "geometry": {
                    "type": "Point",
                    "coordinates": [
                        -118.46710503101347,
                        33.9909333514159
                    ]
                }
            },
            {
                "type": "Feature",
                "properties": {
                    "timestamp": 1531007628.3774529
                },
                "geometry": {
                    "type": "Point",
                    "coordinates": [
                        -118.464851975441,
                        33.990366257735
                    ]
                }
            },
            {
                "type": "Feature",
                "properties": {
                    "timestamp": 1532046474.333497
                },
                "geometry": {
                    "type": "Point",
                    "coordinates": [
                        -118.46594363451004,
                        33.99065981258349
                    ]
                }
            },
            {
                "type": "Feature",
                "properties": {
                    "timestamp": 1529968907.289541
                },
                "geometry": {
                    "type": "Point",
                    "coordinates": [
                        -118.46710503101347,
                        33.9909333514159
                    ]
                    
                }
            }
        ]
    },
    "accuracy": 6,
    "device_id": 8745531,
    "parking_verification": "urlhere",
    "standard_cost": 0.05,
    "actual_cost": 1.15
}

[thekaveman]

@kevinsmgov and I were discussing along similar lines (pun intended!)

He brought up the GPX data format, which might be applicable here.

[dmklinger]

Can GPX be done in JSON? (Probably not) I like this way also b/c then Route is valid GeoJSON and can be exported to MapBox (or whatever we want) relatively easily without having to pull a bunch of fields

I also think it is relatively flexible in allowing for a variety of input methods: it doesn't matter what rate they poll the device (the polling can be irregular) or how often. It allows us to see exactly whether interpolation makes sense rather than requiring interpolation from the onset.

[thekaveman]

Yes, I agree... my comment about GPX wasn't so much that it should literally be the format here (as you rightly point out, it is an XML format not JSON). But more along the lines of what you're already proposing: a series of timestamps with associated GPS location.

Agree on all your points, and this definitely seems like a more useful representation that the individual start_point, end_point, etc.