StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9303459
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-02-15T23:50:00.510
FavoriteCount
0
LastActivityDate
2012-02-15T23:50:00.510
LastEditDate
LastEditorUserId
0
OwnerUserId
274618
ParentId
9274196
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I have dealt with dealing 10,000s of placemarks and other kml objects in the earth plugin and the best way I find is manage the data in a javascript object. dealing with them in standard kml would often crash things. parse the kml before hand into something that you can handle as an object start with: <pre><code>var myModels = {}; </code></pre> for adding the first item if the id is 'foo' or a numeric do something like: <pre><code>myModels['foo'] = { description: 'some description for foo', longitude: 100.12345, latitude: 45.4567 linkUrl: 'http://mydomain.com/mymodels/foo.dae', kmlObject: null}; </code></pre> now looking at the code from: <a href="http://code.google.com/apis/ajax/playground/?exp=earth#creating_3d_models" rel="nofollow">http://code.google.com/apis/ajax/playground/?exp=earth#creating_3d_models</a> you will have something similar to: <pre><code>var placemark = ge.createPlacemark(''); placemark.setName('model'); var model = ge.createModel(''); ....... placemark.setGeometry(model); </code></pre> now go: <pre><code>myModals['foo'].kmlObject = placemark; </code></pre> this will give you a quick reference to the model if you need to change it or remove it with just <pre><code>myModels['foo'].kmlObject </code></pre> no need to traverse the tree again. one thing I found to be faster was to define kml client side and use parseKml to load it rather then create individual objects and add them. also you can build in logic to only add the dae model that are within the area the user is looking at to loop through all the items <pre><code>var i, iModel; for (i in myModels){ iModel = myModels[i]; if(myModels[m].kmlObject == null){ 'add if statement to check if the models long/lats are in current view with ' iModel.longitude, iModel.latitude } } </code></pre> also rather than add everything in one operation, add 10-20 model in a single batch and use setTimeout to start another batch operation a second later and leverage .executeBatch <a href="https://developers.google.com/earth/documentation/reference/google_earth_namespace#ab26414915202d39cad12bcd5bd99e739" rel="nofollow">https://developers.google.com/earth/documentation/reference/google_earth_namespace#ab26414915202d39cad12bcd5bd99e739</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I optimize the loading time of Google Earth Web Plugin if I have a very large KML file?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBerwyn
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do I optimize the loading time of Google Earth Web Plugin if I have a very large KML file?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.