Skip to main content

Satellite Tracking: Initial Succeess


New Tracking AppN2YO site


As I mentioned yesterday, I'm playing around with building a satellite tracking application. I'm helping with a special event station to help raise awareness for the Friends of Science East's effort to restore Tesla's last lab, Wardenclyffe, in Shoreham, NY. After a few very minor issues, the first satellite is being tracked! First, the satellites in the AMSAT Keplerian data are named in a different fashion than they are on N2YO's site, (the site I'm using to verify my results). So, LO-19 in Amsats Keplerian data table:

LO-19
1 20442U 90005G 11187.94329143 -.00000024 00000-0 64087-5 0 01550
2 20442 098.3466 141.1781 0012855 097.5464 262.7179 14.32152423120621

is designated as Oscar19 (LUSAT) on the N2Y0 site.

At first, I thought there just weren't actually any amateur satellites in the Amsat data, but soon realized the different naming after performing a 'Search By Satellite Name' on N2YO's site. I'll try to get a table that lists the associated names into one of these blog posts.

After looking into the naming issue, it only took a few minutes to disect the baseline code, (because it is very clear and well written as mentioned before), and feed it the Keplerian data for Oscar19.

And a few seconds later, there was Oscar19 on my screen just tracking along! Using N2YO's site as a reference, Oscar19 is showing up in about the right place as can be seen in the pictures above.

Now, I'm off to understand the time progression code and to add buildings to the map.

Buildings were no problem. Using the Google Earth API docs for layers, it took one line of code to add the buildings of Manhattan!

I ran into what I thought might be the first problem while perusing buildings. It's difficult to know where to look for the satellite without a good old 2D representation of it's position, (or by zooming way out), and it would be handy to have a 2D inlay of where the horizon is at the current position to know if the satellite was behind the horizon.

The time progression code for the satellite animation has an ingenious member called g_speed. By setting this to 1, you can see the satellite move in real time. By setting it to more than one, you speed up time and watch the satellite track for the entire day in just a few seconds.

Each satellite has a Icon member which is responsible for drawing the satellite on the screen. I'll be adding a LineString geometry member to the satellite that will store the locations on the satellite track and draw the line corresponding to the track as it progresses.

And it worked! As of this writing, one satellite is being tracked with it's trail streaming out behind it. I've sped time up 20 using the g_speed variable. You can see the current demo at:

http://copaseticflows.appspot.com/examhelp/sattrack.html

You'll probably need to rotate the earth a bit to find the satellite at first, but it's there!

Or watch a brief movie of it here.

Comments

Popular posts from this blog

More Cowbell! Record Production using Google Forms and Charts

First, the what : This article shows how to embed a new Google Form into any web page. To demonstrate ths, a chart and form that allow blog readers to control the recording levels of each instrument in Blue Oyster Cult's "(Don't Fear) The Reaper" is used. HTML code from the Google version of the form included on this page is shown and the parts that need to be modified are highlighted. Next, the why : Google recently released an e-mail form feature that allows users of Google Documents to create an e-mail a form that automatically places each user's input into an associated spreadsheet. As it turns out, with a little bit of work, the forms that are created by Google Docs can be embedded into any web page. Now, The Goods: Click on the instrument you want turned up, click the submit button and then refresh the page. Through the magic of Google Forms as soon as you click on submit and refresh this web page, the data chart will update immediately. Turn up the:

Cool Math Tricks: Deriving the Divergence, (Del or Nabla) into New (Cylindrical) Coordinate Systems

Now available as a Kindle ebook for 99 cents ! Get a spiffy ebook, and fund more physics The following is a pretty lengthy procedure, but converting the divergence, (nabla, del) operator between coordinate systems comes up pretty often. While there are tables for converting between common coordinate systems , there seem to be fewer explanations of the procedure for deriving the conversion, so here goes! What do we actually want? To convert the Cartesian nabla to the nabla for another coordinate system, say… cylindrical coordinates. What we’ll need: 1. The Cartesian Nabla: 2. A set of equations relating the Cartesian coordinates to cylindrical coordinates: 3. A set of equations relating the Cartesian basis vectors to the basis vectors of the new coordinate system: How to do it: Use the chain rule for differentiation to convert the derivatives with respect to the Cartesian variables to derivatives with respect to the cylindrical variables. The chain

The Valentine's Day Magnetic Monopole

There's an assymetry to the form of the two Maxwell's equations shown in picture 1.  While the divergence of the electric field is proportional to the electric charge density at a given point, the divergence of the magnetic field is equal to zero.  This is typically explained in the following way.  While we know that electrons, the fundamental electric charge carriers exist, evidence seems to indicate that magnetic monopoles, the particles that would carry magnetic 'charge', either don't exist, or, the energies required to create them are so high that they are exceedingly rare.  That doesn't stop us from looking for them though! Keeping with the theme of Fairbank[1] and his academic progeny over the semester break, today's post is about the discovery of a magnetic monopole candidate event by one of the Fairbank's graduate students, Blas Cabrera[2].  Cabrera was utilizing a loop type of magnetic monopole detector.  Its operation is in concept very sim