1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
---
jupytext:
text_representation:
extension: .mystnb
format_name: myst
format_version: 0.13
jupytext_version: 1.14.0
kernelspec:
display_name: Python 3
language: python
name: python3
---
# Visualize orbital data with Cesium
Poliastro allows users to easily convert orbital data to CZML, a JSON format primarily used in applications running Cesium.
+++
## Dependencies
You will only need poliastro (obviously) and czml3, a library for easily creating and using CZML packets:
``pip install poliastro czml3``
+++
## Our first example: The Molniya orbit
We'll start off by using one of the readily usable poliastro examples. Of course, you can use any poliastro ``Orbit`` object:
```{code-cell}
from poliastro.czml.extract_czml import CZMLExtractor
```
```{code-cell}
from poliastro.examples import molniya
```
To initialize the extractor, you'll only need the starting and ending epoch of the time period you wish to visualize and the number of sample points. The larger the sample point size, the more accurate the trajectory and the bigger your packets. Finding that sweet spot between reasonable package size and visual accuracy depends on the specific orbit. Generally, you'll need a bigger sample for faster satellites. You could also "break" your orbit into different parts and define the sample size individually (for example, this could be useful when the satellite accelerates within a certain time interval).
For this specific example, we're only interested in a single orbital period:
```{code-cell}
start_epoch = molniya.epoch
end_epoch = molniya.epoch + molniya.period
N = 80
```
```{code-cell}
extractor = CZMLExtractor(start_epoch, end_epoch, N)
```
To add an orbit you can simply call ``add_orbit`` and pass your ``Orbit`` along with an optional precision parameter (``rtol``). However, there are also many optional parameters you can pass to the extractor to specify the visual characteristics of your trajectory:
### Id parameters:
``id_name``: The orbit id name
``id_description``: The orbit's description
### Path parameters:
``path_width``: The trajectorie's width. It's defined in pixels and defaults to ``1.0``
``path_show``: Whether the trajectorie's path is visible (true by default)
``path_color``: The trajectorie's color, a simple list with the rgba values (e.g. ``[45, 30, 50, 255]``)
### Label parameters:
``label_text``: The label text; the text that appears besides the orbit.
``label_show``: Whether the label is visible (true by default)
``label_fill_color``: The fill color of the label, a simple list with the rgba values
``label_outline_color``: The fill color of the label, a simple list with the rgba values
``label_font``: The font properties (CSS syntax)
### Groundtrack parameters:
``show_groundtrack``: Whether the groundtrack is visible (true by default)
``groundtrack_lead_time``: The time the animation is ahead of the real-time groundtrack
``groundtrack_trail_time``: The time the animation is behind the real-time groundtrack
``groundtrack_width``: The groundtrack width
``groundtrack_color``: The groundtrack color. By default, it is set to the trajectory's color
```{code-cell}
extractor.add_orbit(
molniya,
id_name="MolniyaOrbit",
path_width=2,
label_text="Molniya",
label_fill_color=[125, 80, 120, 255],
)
```
You can now export the extractor packets by simply calling ``extractor.packets`` and load it to the Cesium app as described [here](https://github.com/poliastro/cesium-app):
```{raw-cell}
>>> extractor.packets
[{
"id": "document",
"version": "1.0",
"name": "document_packet",
"clock": {
"interval": "2000-01-01T12:00:00Z/2000-01-01T23:59:35Z",
"currentTime": "2000-01-01T12:00:00Z",
"multiplier": 60,
"range": "LOOP_STOP",
"step": "SYSTEM_CLOCK_MULTIPLIER"
}
}, [...]
```
## Landing on Mars
You can customize the attractor of your orbit by defining any valid ellipsoid with the help of poliastro's ``Body`` class. For your convenience, poliastro offers a pre-defined list of all the major planetary bodies of the solar system so you can simply import them:
```{code-cell}
from poliastro.bodies import Mars
```
Of course, when defining a new attractor you want to be able to identify something other than it's shape. For this reason, the extractor allows you to easily set the UV map by simply providing a valid URL:
```{code-cell}
mars_uv = "https://upload.wikimedia.org/wikipedia/commons/f/fd/Mars_2020_LandingSites_Final_8-full.jpg"
```
```{code-cell}
extractor = CZMLExtractor(
start_epoch, end_epoch, N, attractor=Mars, pr_map=mars_uv
)
```
```{code-cell}
extractor.packets
```
## Return to Flatland
Instead of a 3D globe you may want to visualize your orbit as a 2D projection instead. In this case you can simply set ``scene3D`` to ``false`` and Cesium will automatically render the scene's orthographic projection. This can be of use when plotting animated groundtracks as we'll see in the next section:
```{code-cell}
extractor = CZMLExtractor(start_epoch, end_epoch, N, scene3D=False)
```
```{code-cell}
extractor.packets
```
## Ground track plotting
Another useful feature the extractor offers, is the ability to plot the ground track of an orbit. You can set the groundtrack by setting the aforementioned ``groundtrack_show`` parameter to true. Note that this also works in 2D view:
```{code-cell}
extractor = CZMLExtractor(start_epoch, end_epoch, N)
```
```{code-cell}
extractor.add_orbit(
molniya,
groundtrack_show=True,
groundtrack_lead_time=20,
groundtrack_trail_time=20,
)
```
```{raw-cell}
>>> extractor.packets
[...]
{
"id": "groundtrack0",
"availability": "2000-01-01T12:00:00Z/2000-01-01T23:59:35Z",
"position": {
"epoch": "2000-01-01T12:00:00Z",
"interpolationAlgorithm": "LAGRANGE",
"interpolationDegree": 5,
"referenceFrame": "INERTIAL",
"cartesian": [
0.0,
6280728.255793354,
-495875.9998745186, [...]
```
|
