--- Sunburned Surveyor <[EMAIL PROTECTED]>
wrote:
> I would also like both of our students to outline a
> basic plan for
> their first "module" by next Monday. This can be a
> very short
> document. (Only a couple of paragraphs are needed.)
> Please let me know
> what your module will accomplish and what classes
> and interfaces it
> will contain. I'll review the documents Monday and
> will provide any
> suggestions before our students get to work. I'll be
> looking to Nacho
> and other Portuguese speakers to help with Leandro!
>
> I will then plan on making my first code and
> documentation review on
> Friday, April 25th to check on our students
> progress.

Do you really mean April 25, i.e. this friday?

I will have a roadmap written up by this weekend then
posted to the list. Coding will proceed after that.
The TIN project is a very low level library that will
require good data structures and a clean API to be
useful in the long run, therefore, I'll want to get
feedback after I get the basic interfaces squared away
but before I start the real coding.

Here's a broad outline of what I'm planning on doing:

Stage 1. 
Get the most basic pipeline working: starting from a
collection of points and a collection of lines, make a
TIN object in memory that can be drawn with no
embellishment (no hillshades or elevation color bands
yet).

Stage 2.
Save the TIN to a file on disk and be able to read
that back into a TIN object.

Stage 3.
Expand the import side so that points and lines could
be read from a file. I would like to at least get an
import pipeline working for WKT based files and USGS
.bil elevation files.

Stage 4.
Get hillshades and color elevation bands to work in
the display of the TIN.

Stage 5.
Make a multi-resolution data structure in which you
could read in the full point set, then query the data
structure to get a TIN at the requested resolution.

(I'm sure by this point the summer will have ended,
but work will continue in the following direction)

Stage 6.
3D display of the TIN and overlays using java opengl
bindings.

Stage 7.
Get the multi-resolution data structure to be database
backed and queried through WMS.

Stage 8.
Viewshades.

Stage 9.
Watersheds.


Well, that's what's going through my head at the
moment (aside from finals which should be over with in
the next day or two depending on when I stop polishing
a paper I'm working on).

--Christopher DeMars


      
____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to