I thought FSX was the original location. I wasn't going to step on Stovall's toes, but since you posted this, I'll go ahead and slide it over.Why was this moved to FSX discussion? This is about MSFS - the new one.
I thought FSX was the original location. I wasn't going to step on Stovall's toes, but since you posted this, I'll go ahead and slide it over.
Thanks Tom for the help with proper forum. You are doing a great job over at MSFS 2020.I thought FSX was the original location. I wasn't going to step on Stovall's toes, but since you posted this, I'll go ahead and slide it over.
Just verified this;
https://www.google.com/intl/en_ca/help/terms_maps/
And I don't see anything prohibiting the use of Google Maps for the specific of creating sceneries from their data.
Quite to the contrary, sub-section b. of section 1. reads;
"License. As long as you follow these Terms, the Google Terms of Service give you a license to use Google Maps/Google Earth, including features that allow you to:
(...)
create KML files and map layers (...)"
The scenery process is basically a map layering for the purpose of modeling ground objects.
Intellectual property was not my field of expertise (criminal and penal law was), but I see no infrigment. Adding the mention that Google Maps or Google Earth was used in the making in the documentation won't hurt...
I guess I was mistaken about what I thought I'd seen concerning Google's policy. Hopefully someone can find a way to get some of these massive packages condensed to a more manageable size. There's one out there that enhances Toronto, but having it loaded makes the sim take twice as long to load a flight - at least on my rig.
but they may react if they see a possibility to make money
the done it with their map services already this is why nearly any VA is now using open street map