=rk=
Resource contributor
- Messages
- 4,470
- Country
I think it is most helpful to encourage others, lead a horse to water, so to speak. There are no specific links and it seems like the term Google is being applied loosely. Google Earth is a global explorer browser that mostly orients locations and also provides cross platform links. Google purchases it's imagery from many sources as well as providing its own and has strict guidelines on end use. While Goggle is genuinely encouraging on the grassroots and hobbyist level, the extremely lucrative market for GPS type apps, forces them to be extremely protective of their investment. So we can use it but we're not supposed to share it.
Google Earth imagery is different. They have their own satellites, but only over the US. When we use geo image browsers, like QGIS, we can access Google imagery as well as bing and quite a few others. The Ortho4XP app that Augustin Winther uses, has 8 or 7 image servers pre programmed into it. I just created a project from the other side of the world, so it is good to have options, but when I do have to use Google, the kychungdotcom technique allows for easy image manipulation, I simply repaint the Google, so what ends getting compiled is an "inferior" derivative, useless for anyone but people enjoying my scenery.
OK so now I will tell you what I do. I use the AW MSFS Guide, by Augustin Winther, which I believe is available here and certainly from our friend Google. Of that procedure, I use this amendment recommended by user kychungdotcom. For me, it only took a few passes, before the procedure became fairly rote. The necessary software is all free and if you look into the amended procedure, you can see that you are relatively free to go ahead and process a screen grab from G.E., with far more precision than transcribing numbers, I'd estimate the kill radius, for each placed georeference point, to be about 3 feet. Yes, it is almost exactly like that view from "Syriana," if anyone remembers that movie.
Google Earth imagery is different. They have their own satellites, but only over the US. When we use geo image browsers, like QGIS, we can access Google imagery as well as bing and quite a few others. The Ortho4XP app that Augustin Winther uses, has 8 or 7 image servers pre programmed into it. I just created a project from the other side of the world, so it is good to have options, but when I do have to use Google, the kychungdotcom technique allows for easy image manipulation, I simply repaint the Google, so what ends getting compiled is an "inferior" derivative, useless for anyone but people enjoying my scenery.
OK so now I will tell you what I do. I use the AW MSFS Guide, by Augustin Winther, which I believe is available here and certainly from our friend Google. Of that procedure, I use this amendment recommended by user kychungdotcom. For me, it only took a few passes, before the procedure became fairly rote. The necessary software is all free and if you look into the amended procedure, you can see that you are relatively free to go ahead and process a screen grab from G.E., with far more precision than transcribing numbers, I'd estimate the kill radius, for each placed georeference point, to be about 3 feet. Yes, it is almost exactly like that view from "Syriana," if anyone remembers that movie.