master index kml for Region Based Network Links using Google Earth Plugin

57 views
Skip to first unread message

JeffJensen

unread,
Jun 19, 2008, 7:20:56 PM6/19/08
to KML Developer Support - Advanced Support for KML
Hello Mano and friends,

When using the Region Based Network Links with the Google Earth
Plugin, do I need to create a single kml file which has the super-
overlay (multi-level) index?

For example, say I have 3 kml files representing data in USA: 1)
State (course level), 2) County (medium level) and 3) City (detail/
fine level). Do I just create one master index kml file which has the
<Lod><LatLonAltBox> attributes for all 3 levels with Network Links
pointing to the State, County, City kml files (note this file doesn't
include any data, just the bounding box info to identify which Network
Link to activate)?

If yes, then this could be a large kml file if trying to make a master
index for all of USA.

If no, how do I load multiple kml files into Google Earth Plugin
(still end up with a large inital download)?

Thanks for the help,

Jeff Jensen

ManoM

unread,
Jun 20, 2008, 8:31:03 AM6/20/08
to KML Developer Support - Advanced Support for KML
Hi Jeff,

Both with Google Earth and the Google Earth API you have the option of
loading them as multiple NetworkLinks. Probably the best bet is to
break it up into a Region-Based NetworkLink (RBNL) hierarchy, where
movement into a particular Region triggers a NetworkLink which loads
some data and also NetworkLinks that will trigger at a smaller grained
level.

It is easier with the Earth API because you can programmatically force
the loading of each of the top-level NetworkLinks, whereas for Google
Earth you have to rely on the user to load the top levels.

You might find this a useful tool for creating your RBNL hierarchies:
http://code.google.com/p/regionator/

Mano

ManoM

unread,
Jun 20, 2008, 8:32:03 AM6/20/08
to KML Developer Support - Advanced Support for KML
Hi Jeff,

Both with Google Earth and the Google Earth API you have the option of
loading them as multiple NetworkLinks. Probably the best bet is to
break it up into a Region-Based NetworkLink (RBNL) hierarchy, where
movement into a particular Region triggers a NetworkLink which loads
some data and also NetworkLinks that will trigger at a smaller grained
level.

It is easier with the Earth API because you can programmatically force
the loading of each of the top-level NetworkLinks, whereas for Google
Earth you have to rely on the user to load the top levels.

You might find this a useful tool for creating your RBNL hierarchies:
http://code.google.com/p/regionator/

Mano


On Jun 19, 4:20 pm, JeffJensen wrote:
Reply all
Reply to author
Forward
0 new messages