Географическая Карта Моделирования Бизнес процесса. Гео карта Google esrth. Kmlсправочник

Название	Kmlсправочник
Анкор	Географическая Карта Моделирования Бизнес процесса
Дата	29.08.2022
Размер	7.61 Mb.
Формат файла
Имя файла	Гео карта Google esrth.docx
Тип	Справочник #655453
страница	17 из 18

1 ... 10 11 12 13 14 15 16 17 18

http://www.example.com/audio/trumpets.mp3

0

Contains an element specifying a sound file to play, in MP3, M4A, or AAC format. It does not contain a duration. The sound file plays in parallel to the rest of the tour, meaning that the next tour primitive takes place immediately after the tour primitive is reached. If another sound file is cued before the first has finished playing, the files are mixed. The element specifies to delay the start of the sound for a given number of seconds before playing the file.

pause

Contains a single element, allowing the tour to be paused until a user takes action to continue the tour.

The camera remains still, at the last-defined gx:AbstractView, for the number of seconds specified before playing the next gx:TourPrimitive. Note that a wait does not pause the tour timeline - currently-playing sound files and animated updates will continue to play while the camera is waiting.

Extends

This element is an extension of the OGC KML 2.2 standard and is supported in Google Earth 5.2 and later. Learn more

Syntax

clampToGround

...

...

...

...

...

Description

A track describes how an object moves through the world over a given time period. This feature allows you to create one visible object in Google Earth (either a Point icon or a Model) that encodes multiple positions for the same object for multiple times. In Google Earth, the time slider allows the user to move the view through time, which animates the position of the object.

A gx:MultiTrack element is used to collect multiple tracks into one conceptual unit with one associated icon (or Model) that moves along the track. This feature is useful if you have multiple tracks for the same real-world object. The
Boolean element of a
specifies whether to interpolate between the tracks in a multi-track. If this value is 0, then the point or Model stops at the end of one track and jumps to the start of the next one. (For example, if you want a single placemark to represent your travels on two days, and your GPS unit was turned off for four hours during this period, you would want to show a discontinuity between the points where the unit was turned off and then on again.) If the value for is 1, the values between the end of the first track and the beginning of the next track are interpolated so that the track appears as one continuous path.

See the Google Earth User Guide for information on how to import GPS data into Google Earth.

Why are tracks useful?

Earlier versions of KML (pre–Google Earth 5.2) allow you to associate a time element with any Feature (placemark, ground overlay, etc.). However, you could only associate one time element with a given Feature. Tracks are a more efficient mechanism for associating time data with visible Features, since you create only one Feature, which can be associated with multiple time elements as the object moves through space.

In addition, the track element is more powerful than the earlier mechanism (described in the Time and Animation chapter of the KML Developer's Guide) because provides a mechanism for interpolating the position of the object at any time along its track. With this new feature, Google Earth displays a graph of elevation and speed profiles (plus custom data, if present) for the object over time.

"Sparse" Data

When some data values are missing for positions on the track, empty () or () tags can be provided to balance the arrays. An empty or tag indicates that no such data exists for a given data point, and the value should be interpolated between the nearest two well-specified data points. This behavior also applies to ExtendedData for a track. Any element except can be empty and will be interpolated between the nearest two well-specified elements.

Elements Specific to Track

Specifies how altitude components in the element are interpreted. Possible values are

clampToGround - (default) Indicates to ignore an altitude specification (for example, in the tag).

relativeToGround - Sets the altitude of the element relative to the actual ground elevation of a particular location. For example, if the ground elevation of a location is exactly at sea level and the altitude for a point is set to 9 meters, then the elevation for the icon of a point placemark elevation is 9 meters with this mode. However, if the same coordinate is set over a location where the ground elevation is 10 meters above sea level, then the elevation of the coordinate is 19 meters.

absolute - Sets the altitude of the coordinate relative to sea level, regardless of the actual elevation of the terrain beneath the element. For example, if you set the altitude of a coordinate to 10 meters with an absolute altitude mode, the icon of a point placemark will appear to be at ground level if the terrain beneath is also 10 meters above sea level. If the terrain is 3 meters above sea level, the placemark will appear elevated above the terrain by 7 meters.

A KML extension in the Google extension namespace, allowing altitudes relative to the sea floor. Values are:

relativeToSeaFloor - Interprets the altitude as a value in meters above the sea floor. If the point is above land rather than sea, the altitude will be interpreted as being above the ground.

clampToSeaFloor - The altitude specification is ignored, and the point will be positioned on the sea floor. If the point is on land rather than at sea, the point will be positioned on the ground.

A time value that corresponds to a position (specified in a element). The number of elements in a must be equal to the number of elements (and elements, if included).

A coordinate value consisting of three values for longitude, latitude, and altitude, with no comma separators. For example:

-122.207881 37.371915 156.000000

Note that the syntax for the element is different from the syntax for the element, which uses commas to separate the longitude, latitude, and altitude components. The number of elements specified should equal the number of time () and position () elements. You can specify an empty element for a missing value if necessary.

This value is used to specify an additional heading, tilt, and roll value to the icon or model for each time/position within the track. The three floating point values are listed without comma separators and represent degrees of rotation. If is not specified, then Google Earth infers the heading, tilt, and roll of the object from its track. The number of elements specified should equal the number of time () and position () elements. You can specify an empty element for a missing value if necessary.

Currently, icons support only heading, but models support all three values.

Here is an example of setting this value:

45.54676 66.2342 77.0

If specified, the Model replaces the Point icon used to indicate the current position on the track. When a is specified within a , here is how the child elements of function:

The element is ignored.

The element is ignored.

The value is combined with the orientation of the track as follows. First, the rotation is applied, which brings the model from its local (x, y, z) coordinate system to a right-side-up, north-facing orientation. Next, a rotation is applied that corresponds to the interpolation of the values that affect the heading, tilt, and roll of the model as it moves along the track. If no angles are specified, the heading and tilt are inferred from the movement of the model.

Tip: If you are unsure of how to specify the orientation, omit the element from the and watch how Google Earth positions the model as it moves along the track. If you notice that the front of the model is facing sideways, modify the
1 ... 10 11 12 13 14 15 16 17 18