Skip to content

Commit

Permalink
Specify IDs caracters range restrinctions (#545)
Browse files Browse the repository at this point in the history
* Specify IDs caracters range restrinctions
  • Loading branch information
tdelmas authored Nov 2, 2023
1 parent 5c07bdf commit d0acc51
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion gbfs.md
Original file line number Diff line number Diff line change
Expand Up @@ -204,7 +204,8 @@ Example: The `rental_methods` field contains values `creditcard`, `paypass`, etc
* ID - Should be represented as a string that identifies that particular entity. An ID:
* MUST be unique within like fields (for example, `station_id` MUST be unique among stations)
* Does not have to be globally unique, unless otherwise specified
* MUST NOT contain spaces
* MUST be in the ASCII printable character range, space excluded (0x21 to 0x7E) https://en.wikipedia.org/wiki/ASCII#Printable_characters *(as of v3.0-RC2)*
* SHOULD be restricted to `A-Z`, `a-z`, `0-9` and `.@:/_-` *(as of v3.0-RC2)*
* MUST be persistent for a given entity (station, plan, etc.). An exception is `vehicle_id`, which MUST NOT be persistent for privacy reasons (see `vehicle_status.json`). *(as of v2.0)*
* Language - An IETF BCP 47 language code. For an introduction to IETF BCP 47, refer to https://www.rfc-editor.org/rfc/bcp/bcp47.txt and https://www.w3.org/International/articles/language-tags/. Examples: `en` for English, `en-US` for American English, or `de` for German.
* Latitude - WGS84 latitude in decimal degrees. The value MUST be greater than or equal to -90.0 and less than or equal to 90.0. Example: `41.890169` for the Colosseum in Rome.
Expand Down

0 comments on commit d0acc51

Please sign in to comment.