Google Earth Reverse Engineering
github.com
Google Earth Reverse Engineering
1–10 of 38 posts
Re: Google Earth Reverse Engineering
#2This is amazing. Would it be practical to download an entire town or small city?
Re: Google Earth Reverse Engineering
#3I'm so glad that this has been made, I tried working on something like this a while ago but gave up after struggling for a bit. At the time I was surprised it didn't exist yet.
I'm wondering though if Google'll eventually patch things so this doesn't work, or if they're not too bothered by people grabbing data like this.
Re: Google Earth Reverse Engineering
#4this is sick. how did you figure out the numeric schemes and even have the idea to look where you did?
Re: Google Earth Reverse Engineering
#5I hope this gets mirrored somewhere else, because I don't trust GitHub to not cave in to legal demands despite RE being legal regardless of EULA in parts of the world, and the extra attention this gets may otherwise kill it.
Re: Google Earth Reverse Engineering
#6"Reverse engineering" seems a bit pointless when Google has open sourced the code for Google Earth Enterprise:
https://github.com/google/earthenterprise
(Update: The client was not open sourced, just the server.)
However, this doesn't give you carte blanche to use Google's own imagery:
Re: Google Earth Reverse Engineering
#7I hope this gets mirrored somewhere else, because I don't trust GitHub to not cave in to legal demands despite RE being legal regardless of EULA in parts of the world, and the extra attention this gets may otherwise kill it.
From what I've seen, GitHub will only respond to a DMCA request for takedown, and Google very rarely files those (I think I saw one in the GitHub DMCA notice repo for an entire internal published source repo once, could be misremembering). Google doesn't usually fight with lawyers instead of tech (e.g. making scraping more difficult).
Not saying you shouldn't fork or fear, but GitHub and Google are generally good actors compared to others.
Re: Google Earth Reverse Engineering
#8This is amazing. Would it be practical to download an entire town or small city?
Can be done, although high LOD takes a while and the current implementation might eat up all memory. You can run it in parallel though. Shard by octants :)
Re: Google Earth Reverse Engineering
#9"Reverse engineering" seems a bit pointless when Google has open sourced the code for Google Earth Enterprise: https://github.com/google/earthenterprise (Update: The client was not open sourced, just the server.) However, this doesn't give you carte blanche to use Google's own imagery: https://maps.google.com/help/terms_maps.html
I wonder why the latest release is over 800MB compressed... I doubt that includes the actual imagery either.
Re: Google Earth Reverse Engineering
#10"Reverse engineering" seems a bit pointless when Google has open sourced the code for Google Earth Enterprise: https://github.com/google/earthenterprise (Update: The client was not open sourced, just the server.) However, this doesn't give you carte blanche to use Google's own imagery: https://maps.google.com/help/terms_maps.html
That project seems to use some other kind of API. It does not handle real octree/3d data AFAIK. I've only seen quadtree and terrain elevation stuff there.