design and operate databases for a living.  The newest of these are assembled on analytic platforms structured to “draw conclusions” for clients in a wide (and formerly random) variety of scenarios.  One of my developers is an analytic tools assembly expert who also works for some “security, emergency, and enforcement” government agencies in Washington, DC – all formerly separate agencies, and because of advancements in the technologies -- now “interoperating”.  I am also a prepper with a Bug Out locale that fulfills my “survival vision” and inherently has most of the natural survival essentials on site, but one which needs some structural work that would be visible to aerial mapping when implemented.  Another prepper colleague of mine who is part of our group has skills that I will generally classify as “ravine and bluff engineering”.  Together we have tried to develop plans to address the visibility problem, and in doing so have hit a “snag” and have come to a conclusion that might be useful to many readers.  So, it is with some expertise and some insight that I pose some thoughts for you today, with the hope that, if you are already knowledgeable on this subject, you might use these to simply update your information, or if you are not, that I might help to guide some of your decision making as I understand that your survival is at stake.

Two ideas:  Presume for the moment that databases have already classified you as a threat or even a likely insurgent. Presume that your resources and assets are already known and well-catalogued, and that access, use, seizure, and in a worst case scenario, potential counter-insurgency plans are in the “system” that can be implemented against you -- precisely directed at what you have been “certain” all along are the excellent and generally secret attributes of your plans in rural and remote areas.