At Earth Retreat share-a-thon, Sarah and Lin had old FORTRAN tracker code that produced some incorrect locations; their issue may not be uncommon.
We could leverage the iSat code to provide a new service to the satellite community. We could pull out the SGP4 location calculation code (that we've been planning to do anyway) and run it on a server as a "web service" -- a URL to be used by other web applications, rather than human users. Other developers could connect to it and request current location and velocity of a satellite by name or ID and get it back in real time. This could be used by folks like Sarah and Lin, other mission trackers, or even the public. It should be not too hard, either.
Pull out SGP4 code and run it in NodeJS on GAE or WESTPrime.
At Earth Retreat share-a-thon, Sarah and Lin had old FORTRAN tracker code that produced some incorrect locations; their issue may not be uncommon.
We could leverage the iSat code to provide a new service to the satellite community. We could pull out the SGP4 location calculation code (that we've been planning to do anyway) and run it on a server as a "web service" -- a URL to be used by other web applications, rather than human users. Other developers could connect to it and request current location and velocity of a satellite by name or ID and get it back in real time. This could be used by folks like Sarah and Lin, other mission trackers, or even the public. It should be not too hard, either.
Pull out SGP4 code and run it in NodeJS on GAE or WESTPrime.