“With this update, DJI’s Fly and Pilot flight app operators will see prior DJI geofencing datasets replaced to display official Federal Aviation Administration (FAA) data. Areas previously defined as Restricted Zones (also known as No-Fly Zones) will be displayed as Enhanced Warning Zones, aligning with the FAA’s designated areas. In these zones, in-app alerts will notify operators flying near FAA designated controlled airspace, placing control back in the hands of the drone operators, in line with regulatory principles of the operator bearing final responsibility.”
Will this also affect DJIGo4 users?
Per that article, this change only affects users of DJI Fly and DJI Pilot. They might have plans to update other apps in the future.
I guess I was wondering whether it might be the case that changes to the underlying GEO database might be experienced in all the apps that leveraged it, and the omission of Go from the PR was more due to it being considered legacy than the fact that it won’t be affected. But I guess we’ll see.
It sounds like updating that database is all that’s needed for at least DJI Fly and DJI Pilot. If you’re flying with DJI GO and fly near No-Fly Zones, you could update and see what happens when starting up in a No-Fly Zone.
@Pat_Iampietro in other forums, people have mentioned they were able to fly in No-Fly Zones with DJI GO after updating the FlySafe database from within DJI GO.
Thanks for the update @msinger ! I posted over in the Pro Systems section of the DJI Forum, but hadn’t gotten any responses yet.
I figured the change would affect all apps that rely on FlySafe, but it’s good to hear that is definitely the case.
Finally a good reason to update FlySafe!