This is a PR issue I'm dealing with right now. I'm the founder of a nascent startup that uses commercial flights to crowdsource aerial imagery on a massive scale. I was anticipating skepticism around the feasibility of our approach, but I ended up entertaining many more concerns about surveillance and governmental access. Because we leverage commercial flights, we're able to update our map hundreds of thousands of times/day. The majority of people immediately start thinking of all the uses cases made possible by that kind of temporal resolution, but there's a very vocal, skeptical few. As much as I'd like to brush them off, skepticism is critical and I'm forcing myself to listen and take notes in order to address those concerns in our marketing and content moving forward. It's a fine line.
Your stakeholders have all been burned before either personally or by other vendors and you will have to somehow built trust against those mental barriers.
I personally treat any company who can access my information as if they are willing to undermine their previous statements, have non-public contracts which sell/trade my information with disreputable companies, can pivot in a moment of desperation to do everything they previously promised not to do, may be M&Aed in such a way that all previous contracts are significantly modified, could have terrible security controls of their data, or may not actually delete all copies of data when they say they do.
The mental barrier is difficult to overcome, and you can't win them all. Distill the message too much with "We make money by selling data" and you'll never see a customer, but the opposite is true as well; "The startup doth protest too much, methinks"
We're taking a two-pronged approach as we launch and scale up.
Short term: camera resolution on the average cell phone is often better than an array onboard a satellite, so the MVP is a native app that window seat passengers use to record in-flight. Because we know the flight route before takeoff and GPS works in Airplane mode, we load in target coordinates and ping the user to begin recording when flying over a target coordinate. They receive free in-flight wifi for their effort, but we also use the wifi connection to stream the video feed. That gets us more exposure to the 77,000 daily flights across the U.S. each day (also boosts general awareness: "Why are you recording out the window?")
Long term: we're developing a hardware solution much more powerful than a cell phone camera with a 6-camera array and many more sensors, including an infrared dome for near-field cloud penetration and onboard preprocessor for compressing the stream before sending it back down to earth. The form factor is akin to a headphone case (I actually used a Bose headphone case for the prototype) and is mounted to the window within the cabin, mitigating the need for FAA (but not FCC) approval. There are some teaser images on our Instagram if you're curious - @notasatellite.
Pardon the stupid question, but how do you see the ground from the plane window? Most of the time I'm on a plane you can't see much of the ground, not nearly enough to get good aerial view images anyway.
Plus video quality is usually pretty crappy and you'd need heaps of post-processing to stabilize the video/remove dirt spots on the window, etc. I find it difficult to believe that this would work well with random people filming with their smartphones out a plane window.
Not a stupid question at all! If you place your phone near the top of the window and angle it down, you'll see an image that looks remarkably like a satellite image and in many cases, better. I didn't believe it could be done either when I first started. A few friends working in the GIS space saw the images and started requesting them on frequent flights I took, and that's about when the lightbulb went off.
There are still a ton of variables that affect image quality. Type of aircraft, weather conditions, altitude, camera, seat position (sitting forward of the wing is slightly more advantageous because the inference engine doesn't have to correct for the exhaust blur in the aft), angle of view, residual engine vibration/dampening, time of day, flap/aileron position, the list goes on. Part of the go-to-market strategy involves making sure the hardware product and the inference engine handles a number of those limitations. Neither satellite nor aerial imagery is perfect, but you have a vastly higher chance with ~80,000 flights/day vs. the 300 commercial imaging satellites in orbit, with automatic cost savings in the millions that we can pass on to our customers.
Not-so-subtle marketing pitch--you can see a bunch of real-life examples on our socials @notasatellite.
Both, but largely through marketing. It's hard to address concerns in the product if the mechanism to collect the data in question doesn't exist.
Our goal is to even the playing field when it comes to accessing spatial data and I feel that's adequately reflected in the core feature of our mapping software; whether you're a forensic analyst at Interpol or the neighbor kid looking up BMX trails, you'll always be looking at the most up-to-date map data. Paid customers receive features of course, but what appears on the map is the same regardless of whether or not you're paying.
- container volume in and out of ports (which are usually in industrial zones right next to airports)
- daily crop harvest rates from the midwest states
- a small undergrad research team in Oregon is analyzing the mist and water turbidity of Willamette Falls to determine flow rate and the impact to salmon runs
- estimating the amount of oil moving in and out of Cushing, Oklahoma by measuring the shadow cast on tanks over 3,500 times per day
- wildfire detection and monitoring on non-daylight flights
There are a bunch of other demos and use cases on our social accounts as well--we're @notasatellite on all the platforms.
Have you considered archaeology? There are many areas of interest along flight corridors where it can be difficult to get imagery at any recent resolution.
Interesting! Would your primary goal be detecting new or possible archaeological sites, change detection of known sites, or something else? Any particular areas in mind?
Bit of everything, depending on the resolution, frequency, and region. If there's a decent frequency (~once per week) and perhaps meter resolution, you can do new site detection. The specifics you look for vary, but I can go into more detail if you'd like. If there's an oblique view rather than top down (preserving height information) and color accuracy, it could pretty directly compete with satellite in some of those use cases. There are also a lot of people at heritage agencies that have to monitor rather large areas for looters and other damage over time.
On the anthropology side, it might also be useful for looking at statistical information about populations/settlements that's difficult to collect other ways due to either the remoteness of the area and the frequency of other data sources. Things like nomadic migration patterns or land use in areas like Siberia / Mongolia, Myanmar, or northern Canada.
I would urge you to reconsider your stance on this as "a PR issue". Having readily available realtime aerial imaging data involves numerous ethical and safety concerns. Stating that people who have these ethical concerns are "few" and that you would "like to brush them off" shows a lack of consideration for how your technology could negatively impact others. Based on a recent paper [1] , "the results show that Europe is 83.28 percent covered with an average of one aerial photography every half an hour and a ground sampling distance of 0.96 meters per pixel".
Assuming 30m intervals and a 1m GSD I can know when someone is or isn't home based on whether or not a car is in their driveway. For people living in the vicinity of an airport where the GSD and intervals would presumably be much higher I could track individuals to and from their home or office from the comfort of a coffee shop.
Either of the above capabilities has ramifications for things like:
- stalking and harassment (no need to follow someone physically)
- home invasion and theft (can determine when someone is out of the house)
- targeting of dissidents (can track who showed up at a meeting)
- kidnapping and rendition (can know when someone is isolated without committing physical surveillance resources)
Those are just a few of the things I can come up with off the top of my head.
Even if you limit your tools to governments and businesses what prevents illegitimate organizations from using shell companies [2] or other means for establishing legitimate accounts to your services, and what prevents individuals within legitimate organizations from accessing the tools for personal means? [3]
Calling this a "PR issue" grossly understates the potential damage a technology like this can cause in the wrong hands.
I really appreciate this response; banally labeling this a "PR issue" was a bit callous and does nothing to address the underlying concerns or the consequences of leaving them unaddressed.
I'm more or less a team of one at the moment and the original instinct when I had the idea was along the lines of "If I'm having to address privacy concerns, I must be doing something right", implying some degree of public interest in the product. There's now quantifiable interest and the waitlist hasn't stopped growing. Comments like yours make me realize I need a rock-solid set of first principles before enlisting outside help. The eternal optimist sees infinite use cases and it's easy to discard the bad and the ugly ones for the good, but the ramifications you've listed will kill the product before it even truly starts.
I'd love to chat more about this side of product development and throw some questions your way if you've got some time to spare (chris@notasatellite.com), but thank you again for the thoughtful response and reading material.
Do you genuinely believe those drones flying over every major city taking high resolution photos of everyone within 30 miles are there for fun?