Skip to content

Add other Veo Mobility markets - #804

Merged
mplsmitch merged 2 commits into
MobilityData:masterfrom
msun-veo:msun-veo-add-systems-1
Oct 20, 2025
Merged

mplsmitch merged 2 commits into
MobilityData:masterfrom
msun-veo:msun-veo-add-systems-1

Conversation

@msun-veo

@msun-veo msun-veo commented Oct 17, 2025 •

Copy link
Copy Markdown
Contributor

Adds multiple Veo cities to systems.csv

@CLAassistant

CLAassistant commented Oct 17, 2025 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@msun-veo msun-veo changed the title Update systems.csv Add other Veo Mobility markets Oct 17, 2025
@mplsmitch

Copy link
Copy Markdown
Contributor

@msun-veo Could you alphabetize this list by name. This is wonderful, thank for the submission.

Sort in alphabetical order
@msun-veo

Copy link
Copy Markdown
Contributor Author

New commit made with rows alphabetized in ascending order by name!

@mplsmitch mplsmitch left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks Good - Thanks for the contribution!

@mplsmitch
mplsmitch merged commit a8b8fde into MobilityData:master Oct 20, 2025
1 check passed
@mplsmitch

Copy link
Copy Markdown
Contributor

@msun-veo We just realized that all of these share a common system_id and that's causing issues in our database. Each of your markets MUST be assigned it's own unique system_id that conforms to the ID field type in the specification - for example they can't contain spaces.

The system_id is defined as following:

This is a globally unique identifier for the vehicle share system. Each distinct system or geographic area in which vehicles are operated MUST have its own unique system_id. It is up to the publisher of the feed to guarantee uniqueness and MUST be checked against existing system_id fields in systems.csv to ensure this. This value is intended to remain the same over the life of the system.

System IDs SHOULD be recognizable as belonging to a particular system as opposed to random strings - for example, bcycle_austin or biketown_pdx.

Can you assign unique IDs to each of your feeds? If not we'll need to remove them from the systems.csv catalog.

Thanks!

@richfab

richfab commented Mar 9, 2026 •

Copy link
Copy Markdown
Contributor

Hi @msun-veo,

Thank you for adding Veo feeds to the GBFS public catalog.

However, I must remove the feeds unless you are able to update the system ids to make them unique.

For example, in system_information.json, system_id could become veo-asb.

Without any action from your part, the feeds will be removed in 2 weeks (March 23rd, 2026).

Thank you,
Fabien (MobilityData)

@richfab

richfab commented Mar 16, 2026 •

Copy link
Copy Markdown
Contributor

Hello @msun-veo,

This is a reminder to update the system ids to make them unique.

For example, in system_information.json, system_id could become veo-asb.

Without any action from your part, the Veo feeds will be removed in 1 week (March 23rd, 2026).

Thank you for your understanding,
Fabien (MobilityData)

@msun-veo

Copy link
Copy Markdown
Contributor Author

Hello @richfab!

Thank you for bringing this to our attention.
We've updated our system IDs to be unique per area. Please test and let me know if you encounter any issues. Thank you!

Matthew

@richfab

richfab commented Mar 17, 2026 •

Copy link
Copy Markdown
Contributor

Hi @msun-veo!

Thank you for updating the system IDs! The update in systems.csv will be merged today.

Fabien (MobilityData)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants