[Data-modeling] Spacecaft: Orbit use cases

[Danny Hillis]

Here are three use cases for spacecraft orbits the we should be able  
to support:

In order to point an antenna at a geostationary communication  
satellite, you need to know its longitude. (besides the orbit, you  
also need to know what it is communicating, what region it serves, etc.)

In order select a source for imagery, you need to know an  
observational satellite's orbit classification, period, inclination,   
repeat cycle, swath width, and equatorial crossing time.  (Besides the  
orbit you also need to know things like sensor type(s), lifetime,  
operator it, etc.)

In order to plot a history of human expansion into space, you need to  
know what satellites were put into orbit when, around which planets.  
(You also need to know who built it, what space mission it was part  
of, etc.)
-danny


On May 4, 2008, at 11:35 PM, Danny Hillis wrote:

> I think your search of existing databases is exactly the right
> starting point. We should really only add a property if we understand
> a specific use case for it.
> The use cases also help suggest which domain the should handle the
> problem. For example, the properties needed to see an artificial
> satellite in a telescope should be handled by the Astronomy Domain,
> but those for determining who built it should be in Spacecraft.
>
> I will post some specific use cases for spacecraft orbits under a
> separate discussion topic.
> -Danny
>
>
> On May 4, 2008, at 7:04 PM, Ed Laurent wrote:
>
> > I've only been able to find smatterings of artificial satellite
> > metadata to use as references. There are lots of links for imagery
> > metadata, and some for sensor characteristics, but I couldn't find
> > any standard metadata formats that described the platforms and their
> > orbits. The data are out there in bits and pieces but I couldn't
> > find a presentation, even in combination, that was comprehensive
> > enough to serve as a foundation for modeling all satellites.
> >
> > I then started reviewing the physics of orbital characteristics...
> > that seemed like overkill. Believe it or not, I'm trying to keep the
> > models as as simple and intuitive as possible but I also don't want
> > to limit their flexibility for user input and applications.
> >
> > I decided to email a NASA program manager I know to ask if they have
> > metadata standards for orbits, platforms, payloads, sensors, etc.
> > that can be released to the public. I'll follow up with his  
> response.
> >
> > -Ed
> >
> > _______________________________________________
> > Data-modeling mailing list
> > Data-modeling at freebase.com
> > http://lists.freebase.com/mailman/listinfo/data-modeling
>
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling