You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This problem first came up with the NYC DOT, which operates the Staten Island Ferry (https://transit.land/feed-registry/operators/o-dr5r7-nycdot). It only has two stops, at the ends of the ferry route; its operator geometry (convex hull) has been computed as a LineString with just two points. This makes it complicated to parse client-side, if you're not guaranteed a polygon.
This problem first came up with the NYC DOT, which operates the Staten Island Ferry (https://transit.land/feed-registry/operators/o-dr5r7-nycdot). It only has two stops, at the ends of the ferry route; its operator geometry (convex hull) has been computed as a LineString with just two points. This makes it complicated to parse client-side, if you're not guaranteed a polygon.
For the time being, we're manually edited the operator geometry to be a polygon: https://transit.land/dispatcher/changesets/2108
In the future, let's look into adding a buffer around stops so that an operator with only two stops gets a polygon.
Timeframe: Not urgent.
The text was updated successfully, but these errors were encountered: