SU2016 Terrain geo-location
-
Just installed SU2016 after SU2015.
I manipulate terrains from GE.
After quite a while of debugging, I eventually found that SU2016 had quite blithely, with neither a "if you please" nor a "may I?", changed the actual names of my two layers which were named "Google Earth Terrain" and "Google Earth Snapshot" (replacing the text "Google Earth" by "Location").My script simply fell over.
It did not know anything about this surreptitious, may I say "ILLEGAL", change of attributes of the entities that were previously created in SU2015, contained in a file that I had saved and considered "safe" and complete.So, rather than complain to the "authorities", I would just like give a "heads-up" to others on this forum who might be interested... (does anybody from Sketchup actually read this forum...?)
I have now added a chunk of code to detect whether I have layers named "Location Terrain" or not and therefore act accordingly... not really a nice wake-up call
As I said - "heads-up" for "Google Earth", sorry, "Location" users...
-
Sorry to hear about your script and the extra work to get it compliant again.
The change was mentioned in the release notes, for those who care to read it.
If I recall correctly there was an announcement from Google somewhere in the recent past that Google Earth will reach end-of-life soon, they're moving all to Google Maps.
Thus the change actually makes perfect sense in my mind.
-
@juju said:
Sorry to hear about your script and the extra work to get it compliant again.
The change was mentioned in the release notes, for those who care to read it.
If I recall correctly there was an announcement from Google somewhere in the recent past that Google Earth will reach end-of-life soon, they're moving all to Google Maps.
Thus the change actually makes perfect sense in my mind.
I understand the change when a new terrain is loaded - SU wants/needs to distance itself from the Google Earth / Google Maps world.
All of this is fine... and understandable and documented
I read the documentation, but never did I understand that a previously saved file would be changed "under the covers".I open a skp file in SU2016, created in SU2015, and lo & behold the layer that I had in the SU2015 version no longer exists in the SU2016 version!
Which means SU can blithely change saved object names without warning!OK, so I fixed my script, but if anybody thinks that an object name change, without warning, when opening an older skp file is acceptable, then I'm worried.
If SU had raised an error saying that my layer name no longer was acceptable or had been changed, then this issue would have been easier to handle...Not a Google Earth issue, really, just the fundamental concept of a software upgrade changing a user's saved data... that's all folks
-
I see what you're saying, deffo's not cool to change existing documents layering, but it probably is somehow linked. Send them a complaint e-mail, hopefully they can adjust the behavior so as to not change previously created documents' layering names.
Advertisement