Splitting large datasets into smaller pieces is useful for display of KML in Google Earth. A single workspace creates both the KML Network link file and the tiled KML datasets. The first part of the workspace uses grid features and creates tile boundaries. The second part of the workspace reads the source data, styles it for KML and writes out to KML tiles.
This sample illustrates how to optimize large datasets for display in Google Earth using KML. The workspace illustrates:
If you attempt to display a large dataset into Google Earth it will likely freeze. You can workaround this by pre-processing the dataset into smaller pieces (tiles) and then serving them. This also means it's easier to keep the data up-to-date since you only have to update an individual tile - not the entire dataset. The approach used here involves requesting data for a smaller area as you zoom in using Google Earth.
“InteropolisDatabase.sdf” is read dynamically with the Autodesk MapGuide Enterprise SDF Reader. The CityGrid features specify the area of interest and create tile boundaries.
Source Interopolis Database data viewed with the Data Inspector
The workspace creates a series of KML & KMZ files:
Open the KML_Network_Link.kml file in Google Earth. You will see the CityGrid as an overview. Zoom in and Google Earth will start to display the detailed data in each tile. Zoom in a further to display the WaterMeters and Buildings. Pan around to send more requests and view additional data from the source dataset.
Viewing KML_Network_Link.kml in Google Earth zoomed out
KML_Network_Link.kml in Google Earth zoomed in to view details in each tile
No one has followed this yet.