Closed steeling closed 2 years ago
Is this a new requirement? If so let's discuss.
On Mon, Sep 30, 2019 at 6:10 PM steeling notifications@github.com wrote:
Allow DSS geofencing. DSS should have the ability to not accept writes outside of an area of interest.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/interuss/dss/issues/119?email_source=notifications&email_token=AKWUMKCEUT55XG3KZWO6TDDQMJ2MNA5CNFSM4I4BLRMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HOV2VZQ, or mute the thread https://github.com/notifications/unsubscribe-auth/AKWUMKAWRU27YNLFZW7E3Q3QMJ2MNANCNFSM4I4BLRMA .
-- [image: Wing] Reinaldo Negron Head of UTM / Wing (415) 736-9996 rnegron@wing.com
Sounds like UTM's UssVolumeReservation (UVR) whereby an authority (the FAA, or service acting on its behalf) with elevated privs can publish the airspace reservations. Note, the FAA disliked NASA's original name which was something like Airspace Restriction because federal use cases such as the the DOD need certain vehicles to get through. This is the property UVR.permitted_uas
Obsolete/inapplicable
Allow DSS geofencing. DSS should have the ability to not accept writes outside of an area of interest.