Open testower opened 2 months ago
Some thoughts on this:
The model is tied to the GeoJSON protocol, which makes it a bit cumbersome to extend (as we have experienced already with #403). In addition individual zones don't have IDs which make them hard to identify, so a separate query to lookup stations by a specific zone would be difficult. I'm tempted to remodel geofencing zones to better fit the GraphQL api and deprecate the current one.
Is your feature request related to a problem? Please describe.
When considering parking in a geofencing zones which only allows parking at stations, it would be useful to know which stations are located within the zone.
Goal / high level use-case Some operators allow only to park at stations within certain geofencing_zones, but currently there is now way to lookup stations located in a zone, the calculation must be done client-side.
Describe the solution you'd like TBD
Additional context
Note that at Entur, this requires allowing station data for free-floating systems, which may break some clients and OTP. Extensive testing needed. The stations query should possible not include virtual stations by default but require a flag.