Geofencing data in GBFS feeds

[evansiroky]

Two of the 7 eScooters that we are consuming GBFS feeds for has partially implemented MobilityData/gbfs#92 to include geofencing data. One of those companies has reversed the lat/lons, so until that is fixed, their data is unusable. However, the other company has the following dropoff area:

This area is inconsistent with what we've been using for the manually defined allowable dropoff area.

Furthermore, one other company has been operating eScooters in the Milwaukie area, but hasn't implemented the geofencing as a part of their GBFS. Thus the trip planner is currently plans trips in two ways that are contrary to on-the-ground eScooter company operations. The first is allowing dropoffs where they probably aren't allowed for the company with geofencing data. The second is not allowing dropoffs for the company that operates outside of Portland, but hasn't included that data in their GBFS feed.

There is ongoing work among numerous people to update the GBFS, so OTP will need to be updated once an updated version of the GBFS is published where all companies provide enough data.