Slightly different angle to the question:
When we develop new layers or maps, you can bet that one place that layer or feature might be fact-checked is in Google Earth. If your map/layer doesn't fit positionally with what the customer sees in Google Earth/Maps, then there's something wrong with your data/map. Who gets the benefit of the doubt on that one? Of course this view is more centered around layer developement, but the implications for cartographic work are strong. I can think of several occasions in the past year where customers wanted to know the positional accuracy of our map features against Google Earth. IMO we aren't necessarily reliant on GE as a direct data source, but we are becoming more bound to it as a resource/reference tool, because our customers are using it. My 2 cents. Any thoughts on this angle? Sorry if I pulled the topic in a slightly different direction. Hopefully it's worth it.
Here's my 2 cents: many of my clients often send me Google Earth image captures to quickly let me know where their project is. I then gather images and other gis base layers from sources I trust/know (government sources mostly) to generate the maps that they want. So, yes, I guess I'm bound to Google Earth in that sense. I am also getting requests to convert project boundary shapefiles or geodatabases to KML so that my clients can create their on-demand maps on their own. So, I finally made the leap and installed Google Earth on my machine so that I would at least know what everyone was talking about! I've used Google Map quite a bit before but not Google Earth. Anyway, for better or worse, as others have noted, GE is here and becoming the standard as it is so accessible to everyone. Doesn't mean we have to like it...


Sign In
Create Account

United States
Back to top
Canada
India








