You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/orbital/spacecraft-object.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,19 +12,19 @@ ms.author: hrshelar
12
12
13
13
# Spacecraft object
14
14
15
-
Learn about how you can represent your spacecraft details in Azure Orbital Ground Station (AOGS).
15
+
Learn about how you can represent your spacecraft details in Azure Orbital Ground Station.
16
16
17
17
## Spacecraft details
18
18
19
19
The spacecraft object captures three types of information:
20
20
21
21
-**Links** - RF details on center frequency, direction, and bandwidth for each link.
22
-
-**Ephemeris** - The latest TLE.
23
-
-**Licensing** - Authorizations held on a perlink per ground station basis.
22
+
-**Ephemeris** - The latest spacecraft TLE.
23
+
-**Licensing** - Authorizations held on a per-link, per-site basis.
24
24
25
-
## Links
25
+
###Links
26
26
27
-
Make sure to capture each link that you wish to use with Azure Orbital when you create the spacecraft object. The following details are required:
27
+
Make sure to capture each link that you wish to use with Azure Orbital Ground Station when you create the spacecraft object. The following details are required:
@@ -35,37 +35,37 @@ Make sure to capture each link that you wish to use with Azure Orbital when you
35
35
36
36
Dual polarization schemes are represented by two individual links with their respective LHCP and RHCP polarizations.
37
37
38
-
## Ephemeris
38
+
###Ephemeris
39
39
40
-
The spacecraft ephemeris is captured in Azure Orbital using the Two-Line Element or TLE.
40
+
The spacecraft ephemeris is captured in Azure Orbital Ground Station using the Two-Line Element, or TLE.
41
41
42
42
A TLE is associated with the spacecraft to determine contact opportunities at the time of scheduling. The TLE is also used to determine the path the antenna must follow during the contact as the spacecraft passes over the ground station during contact execution.
43
43
44
-
As TLEs are prone to expiration, the user must keep the TLE up-to-date using the [TLE update](update-tle.md) procedure.
44
+
As TLEs are prone to expiration, the user must keep the TLE up-to-date using the [TLE update](update-tle.md) procedure. A TLE that is more than two weeks old might result in an unsuccessful contact.
45
45
46
-
## Licensing
46
+
###Licensing
47
47
48
-
In order to uphold regulatory requirements across the world, the spacecraft object contains authorizations on a perlink and persite level that permits usage of the Azure Orbital ground station sites.
48
+
In order to uphold regulatory requirements across the world, the spacecraft object contains authorizations on a per-link and per-site level that permits usage of the Azure Orbital Ground Station sites.
49
49
50
-
The platform will deny scheduling or execution of contacts if the spacecraft object links aren't authorized. The platform will also deny contact if a profile contains links that aren't included in the spacecraft object authorized links.
50
+
The platform will deny scheduling or execution of contacts if the spacecraft object links are not authorized. The platform will also deny contact if a profile contains links that are not included in the spacecraft object authorized links.
51
51
52
-
For more information, see the Licensing (add link to: concepts-licensing.md when article is created) documentation.
52
+
For more information, see the [spacecraft authorization and ground station licensing](register-spacecraft.md) documentation.
53
53
54
54
## Create spacecraft resource
55
55
56
56
For more information on how to create a spacecraft resource, see the details listed in the [register a spacecraft](register-spacecraft.md) article.
57
57
58
58
## Managing spacecraft objects
59
59
60
-
Spacecraft objects can be created and deleted via the Portal and Azure Orbital APIs. Once the object is created, modification to the object is dependent on the authorization status.
60
+
Spacecraft objects can be created and deleted via the Portal and Azure Orbital Ground Station APIs. Once the object is created, modification to the object is dependent on the authorization status.
61
61
62
-
When the spacecraft is unauthorized, then the spacecraft object can be modified. The API is the best way to make changes as the Portal only lets you make TLE updates.
62
+
When the spacecraft is unauthorized, then the spacecraft object can be modified. The API is the best way to make changes to the spacecraft object as the Portal only allows TLE updates.
63
63
64
-
When the spacecraft is unauthorized, then TLE updates are the only modifications possible. Other fields such as links become immutable. The TLE updates are possible via the Portal and Orbital SDK.
64
+
Once the spacecraft is authorized, TLE updates are the only modifications possible. Other fields, such as links, become immutable. The TLE updates are possible via the Portal and Orbital API.
65
65
66
66
## Delete spacecraft resource
67
67
68
-
You can delete the spacecraft object via the Portal or through the API. See [How-to: Delete Contact](delete-contact.md)
68
+
You can delete the spacecraft object via the Portal or the API. See [How-to: Delete Contact](delete-contact.md).
0 commit comments