earthenterprise
earthenterprise copied to clipboard
google
Custom Imagery layer and kh.google.com 3D buildings layer
Activating an imagery layer on a globe causes 3D buildings "kh.google.com" layer to be disabled. Displays instead the older version of 3D buildings.
Hi, @rentonxp.
This may be a problem with the earth client you're using. Can you provide reproduction steps, and versions of software you're using? E.g., what steps do you take to build your globe? What version of Fusion, Earth Server, Earth Client are you using? What platform are you running the Client and Server on?
Hello, I'm running fusion/server (centos 7) version 5.2.4-0.alpha.201809061452, EC 7.3.2.5493 (32-bit) with windows 7. Reproduction steps :
- Building imagery resource
- Building imagery project
- Building new Earth (3D) database including my imagery project only
- Publishing my database to my Enterprise Server
- Opening EC 7.3.2.5493 (32-bit) on win 7
- Connecting to Google Earth server http://kh.google.com:80/
- Activating 3D Buildings layer
- Connecting to my globe
- Activating imagery layer on my globe
Thx
If I understand correctly what you're doing from your description, it's not something that you can do with Enterprise Client.
You can be connected to only one globe at a time, so, if you connect to your globe, you're no longer connected to kh.google.com. (Does that URL even work?)
You can build a KML layer in your globe to refer to layer served from another server (if it supports an output compatible with KML).
The open source Fusion and Server don't seem to provide support for building and serving 3D modes in a globe.
Connecting my GEC to more than 1 globe is working fine. When my globe contains only vector layers, 3D buildings display properly. A globe with Image layers seem to cause this problem.
Screenshot 1 (kh.google.com + vector globe)
https://owncloud.sdmis.fr/index.php/s/bdcpzIapVoUjnV7
Screenshot 2 (kh.google.com + imagery globe)
https://owncloud.sdmis.fr/index.php/s/yk2Wo5xndmvuQOg
I've followed your reproduction steps with client 7.3.2 on Linux and I'm not able to replicate the issue. It's possible that it's Windows specific. I'll give that a try as well but it will take a little more work to set up.
