Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I made three suggested additions to the provider API:
trip/accuracy: For both technical (GPS accuracy limitations) and privacy (deliberate blurring of location information), the start/end point information may have limited accuracy. This flag allows data consumers to understand the limitations of the data reported. This presumes blurring will by done by a fixed radius. We may need to expand this to support blurring by geographic area (e.g. census block group).
trip/parking_verification: Many dockless providers request a photo of the parked vehicle from the user to verify correct parking. This field could be used to provide access to the photos to agencies for spot checks or other monitoring.
availability/allowed_placement: A boolean to indicate whether the provider believes the placement was in compliance with rules. Could be used by agencies to analyze rate and location of misplacements by users (e.g. out of service area), and to compare providers on their success at avoiding misplacement.