On May 3, 2011, at 11:35 AM, Brian Case wrote:

> i was curious as to the current state of oam

The codebase is coming along, but slowly. The imagery index is live, thanks to 
Christopher Schmidt, and Michal Migurski has written an extension to his 
Tilestache code that generates tiles using our infrastructure. I plan to write 
something similar for TileCache shortly.

The archive server and processing tools haven't been developed very far yet. 
Right now, the way to get imagery into OAM is to process it manually, put the 
processed versions into an HTTP/1.1-accessible directory somewhere, and then 
run the oam-post script from the OAM code base to read the metadata and import 
it into the index.

Some immediate to-dos:

  * extend the API to optimize querying and add scale-dependent filtering (I'm 
planning to do this today)
  * optimize the tile rendering
  * improve the UI on the imagery index
  * start working on a toolchain to allow uploading georeferenced imagery to an 
archive server, where it gets processed and added to the index automatically?

> what servers are mirroring data?

Right now the primary layers in OAM are NAIP, OnEarth, and Blue Marble, all of 
which, I believe are hosted on hyperquad at Telescience for now. Chris and I 
have been given access to a server at NPS that I'm still setting up. We've had 
some offers of hosting from elsewhere, but I haven't had time to take advantage 
of them.

> has anyone else done any imagery?


Brian, in what state are your processing scripts? Are they much more advanced 
than what we've got in the OAM repo now?

I guess the code base is at the point now where we would benefit from 
additional contributors, and from the participation of people willing to do 
image curation. Everyone who's interested in participating at this still *very* 
alpha stage should pipe up now or otherwise get in touch.

SDE
_______________________________________________
talk mailing list
[email protected]
http://host134.hostmonster.com/mailman/listinfo/talk_openaerialmap.org

Reply via email to