-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverage Maps #31
Comments
Hi @gleatd01 are you referring to the groundtracks plots? |
This would be related to groundtrack plots, an additional feature being the visibility of the orbital object. A great example is on page 23 of https://help.agi.com/stk/LinkedDocuments/OM_Coverage.pdf . You might very well have this implemented in your program and I just don't know how to use it. |
@gleatd01 Thank you for the link, I see what you mean now. Are you looking for a tool that could say output when the satellite makes a pass over some region defined by lat/lon bounds for the purpose of both Earth observation and comms link? Also I'm thinking this would also need elevation and azimuth angles from the ground calculations |
I would like to calculate when an object is in view. I already use skyfield for determining when a satellite is making a pass. I am more interested in just the total area seen by the satellite. When plotting multiple satellites I would then be able to see deadzones. So mainly altitude to earth used to calculate expected field of view, I think terrain mapping would be a bit too much. I believe this is a good example. https://www.analyzemath.com/Geometry_calculators/earth-coverage-by-satellites.html I really just plan to use your software or modify it to track 1 satellite and display a surface coverage map and generate a new image every 5 minutes. |
I'm thinking that this could be a function in orbit_calculations.py that takes in an array of position vectors, converts to IAU_EARTH reference frame, does the calculation in that last link you sent (with sensor half angle as input), and then uses that to make more representative groundtracks plots where the radius of the dot is the actual radius calculated. It can also be set to plot out an observation every X amount of seconds, so it is representative of how often the sensor is actually taking images. Thoughts? Also, I think you'll find these 2 videos interesting regarding this. Specifically, using sensor FOV data to create 3D visualizations of surface observations and instrument frustums: |
I believe what you propose would be excellent, essentially creating a spotlight on the globe in the appropriate area. Also great find with the youtube videos, I will be doing something very similar to https://www.youtube.com/watch?v=pMFP00awHZ0&list=PLinlYN8Y2w8dF_FI2baI5YXM476_7kekz&index=17 , however will be having a significantly wider angle for the FOV. Thank you for directing me to this. |
Do you plan to implement coverage maps into this?
The text was updated successfully, but these errors were encountered: