droneflyers.com
Second Officer
Flight distance : 60709 ft
United States
Offline
|
I don't like it because it's somewhat of a afterthought put in for consumer demand. It's not perfected, IMHO.
Maybe with two separate GPS systems the P3 will be better for SDK solutions.
GS is "dumb" in that it doesn't know if you are going to fly into a hill or even into the ground if it slopes up a bit. Yet GPS and google maps DO know the basic slope of the ground, so a smarter app would warn you about these things.
If I had a really important use for it I would then be very careful and set up a mission. I've been tech nut since I was a kid - and yet I almost flew my first GS mission into the ground. I take experiences like that and think "OK, I'm no newbie to maps and tech...and if I almost did this, what is going to happen when regular people try this"....
I think most people who are technical fail to understand how most of the population thinks. Most people can't read maps and topography well. That's a fact.
I think the current generation of drones requires pilot input. This may change very soon - but I'd want to see a lot more checks in the system and warning that say "hey, if you fly this particular mission you are going to hit the ground as indicated by our maps and GPS" warnings.
Lastly, it's impossible to really test what might happen when the usual errors occur in mid-GS missions. For example, DJI has claimed to fix a lot of telemetry errors which caused flyaway when things like bad pin contacts are occurring. BUT, I doubt there was every enough real world testing to prove what happens in every scenario when you are in the middle of a mission....
Again, that's my humble opinion. It could change with the P3 or with new software and hardware. |
|