-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network link support #402
Comments
Even if we made the CMS so it would automagically update things from a user's system, without any interaction or maintenance or worry on their part, it wouldn't change the fact that it would be very nice to be able to use something like Geoserver. There are certainly opportunities already out there to use data that's not easily constructed into static KML. WMS and the behavior NetworkLinks are supposed to exhibit is a very straightforward solution to problems of overly complex data, for instance, where regionation happens automatically. |
Overview:
Tori from CBRE Atlanta was interested in the following use case:
We know this is not entirely far fetched as Google Earth does allow for remote assets, and whether or not this asset is stored on someone local computer. However, previous testing with @eggyknap using Geoserver showed us that the ability to update network links did not work quite as expected:
Of course, and this is more of a CMS issue:
Either way, if we can decide that there is a definitive way to improve this behavior then I think we should work towards it. For example, I can see a case of live updating KML layers via processing thru Geoserver rather than certain sites loading data with too much metadata and bogging down Earth's performance.
The text was updated successfully, but these errors were encountered: