Skip to content

Commit

Permalink
Proposal: Add feed_contact_email field to system_information.json (#181)
Browse files Browse the repository at this point in the history
feed_contact_email in system_information.json.
backwards-compatible change will become part of v1.1
  • Loading branch information
yocontra authored and antrim committed Jan 3, 2020
1 parent 9825154 commit 0b90f89
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions gbfs.md
Original file line number Diff line number Diff line change
Expand Up @@ -222,6 +222,7 @@ purchase_url | Optional | A fully qualified URL where a customer can purch
start_date | Optional | String in the form YYYY-MM-DD representing the date that the system began operations
phone_number | Optional | A single voice telephone number for the specified system. This field is a string value that presents the telephone number as typical for the system's service area. It can and should contain punctuation marks to group the digits of the number. Dialable text (for example, Capital Bikeshare’s "877-430-BIKE") is permitted, but the field must not contain any other descriptive text
email | Optional | A single contact email address for customers to address questions about the system
feed_contact_email| Optional | A single contact email address for consumers of this feed to report technical issues
timezone | Yes | The time zone where the system is located. Time zone names never contain the space character but may contain an underscore. Please refer to the "TZ" value in https://en.wikipedia.org/wiki/List_of_tz_database_time_zones for a list of valid values
license_url | Optional | A fully qualified URL of a page that defines the license terms for the GBFS data for this system, as well as any other license terms the system would like to define (including the use of corporate trademarks, etc)
rental_apps *(beta)* | Optional | A JSON object that contains rental app information in the android and ios JSON objects.
Expand Down

0 comments on commit 0b90f89

Please sign in to comment.