Consider including secondary GPS data in spec: speed, course, altitude, verticalAccuracy

[ezheidtmann]

These fields are provided by both dominant smartphone platforms, but they can be null. I believe the field names should be defined in the spec, but allowed to be empty. Proposed definitions:

• speed: Instantaneous speed in meters per second. Ref: iOS Android
• course: The direction in which the device is traveling, measured in degrees and relative to due north. Ref: iOS Android
• altitude: The altitude, measured in meters. Ref: iOS Android
• verticalAccuracy: The uncertainty of the altitude value, in meters. Ref: iOS Android

Example point:

    {
        "type": "Feature",
        "properties": {
            "timestamp": 1529968782.421409,
            "speed": 5.23,
            "course": 290,
            "altitude": 40,
            "verticalAccuracy": 30
        },
        "geometry": {
            "type": "Point",
            "coordinates": [
                -118.46710503101347,
                33.9909333514159
            ]
        }
    }

[hunterowens]

👍 from me. @ezheidtmann do you want to PR?

@thekaveman this seems like something for a 0.2.0 release?

[marie-x]

This is covered in Agency 0.3.0. I don't know if we want to go back and update Provider.

[marie-x]

What say ye @ezheidtmann ?

[ezheidtmann]

I'd advocate for including these fields as optional in Provider feeds.

[schnuerle]

Sounds good to add these to provider too. What do you think @thekaveman @Karcass?

[marie-x]

Yes, it would further align Agency and Provider.

[schnuerle]

Would anyone like to do a PR for this and make all the fields optional to ensure it's not breaking for 1.1.0? Otherwise we can push to next release. See PR #73 for some ideas.

[schnuerle]

I think this may require some more discussion and work and could be a breaking change so moving to 2.0.0.

[schnuerle]

Being addressed by #653. Please review that PR and leave comments there if interested.

[schnuerle]

We will be addressing most of this in 1.2.0 with the #653 PR. The only thing missing will be vertical accuracy, which we have created a new Issue for at #661.