This repository was archived by the owner on Nov 25, 2025. It is now read-only.
This repository was archived by the owner on Nov 25, 2025. It is now read-only.
FlightPart geometries supporting LineStrings #1
Description
If a user were to specify a LineString geometry for a flight - the implication is that the service would need to infer some sort of bounding radius for that string to calculate overlapping flight paths.
Is it worth either explicitly specifying the degree of 'inflation' of the LineString on the API? (The degree of 'inflation' might have something to do with the speed at which the drone is capable of travelling)
It may be worth removing LineString support, leaving Polygons, which would probably better describe the expanded LineString geometry without ambiguity?
Edit: Spelling