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
Originally posted by Xio1996 January 22, 2024
Hi Everyone,
I am using the Remote Control Plugin (/api/objects/info?format=map) to return data on the selected object in Stellarium. The object is then added to an AstroPlanner plan. I'm having trouble getting the objects size/orientation information returned.
As an example I selected NGC 6740 (galaxy) and requested the data in JSON format. The size information for the major axis is returned in several formats.
However, Stellarium displays not only the major axis but also the minor axis and orientation angle. I know that if I call the 'info' command on the Remote Control Plugin, without a format parameter, then I will get back the displayed html code.
Size: +0°01'11.58" x +0°00'41.52" Orientation angle: 40°
Is it possible to get this information (if available) in the JSON/map format?
Many thanks for your help.
Pete
The text was updated successfully, but these errors were encountered:
Discussed in #3604
Originally posted by Xio1996 January 22, 2024
Hi Everyone,
I am using the Remote Control Plugin (/api/objects/info?format=map) to return data on the selected object in Stellarium. The object is then added to an AstroPlanner plan. I'm having trouble getting the objects size/orientation information returned.
As an example I selected NGC 6740 (galaxy) and requested the data in JSON format. The size information for the major axis is returned in several formats.
However, Stellarium displays not only the major axis but also the minor axis and orientation angle. I know that if I call the 'info' command on the Remote Control Plugin, without a format parameter, then I will get back the displayed html code.
Size: +0°01'11.58" x +0°00'41.52"
Orientation angle: 40°
Is it possible to get this information (if available) in the JSON/map format?
Many thanks for your help.
Pete
The text was updated successfully, but these errors were encountered: