[JPP-Devel] JTIN progress update

[Christopher <inf...@ya...>]

JTIN progress update

I have the rendering pipeline working and have uploaded my sources to the svn repository. It is very crude, but it can open a binary .jtf tin file and display it. In order to get to this point, I had to get a rather large chunk of the JUMP codebase clear in my mind and code without the feedback of running code. Now that I have a pretty good handle on how to get things done within JUMP and have the benefit of instant feedback, things should go quicker.

This next week, I'm going to continue fleshing out the front end (see todo list below), then work on getting a functional back end together.

QUESTION: I need to decide what direction I'm initially going with the backend, i.e. what I'll use as a source for points and optionally lines that get turned into a tin. Right now I'm deciding between using simple feature layers in the workbench (one for points, one for breaklines, one for boundaries) or using a USGS .bil raster file plus optional layers containing breaklines and boundaries. Going the raster route would take a little more effort in initial coding, but would be easier to test (due to the massive datasets available) and would be more useful for OpenJUMP users in the future. Does anyone have any opinion on which tack I should take or if I should consider something completely different?

Front-end TODO list: (off the top of my head; unordered, non-comprehensive)
* expand the BasicTinStyle to allow user selected color, color bands, and/or hillshading (right now I'm setting the color of each triangular facet to a random color without any shading)
* clip non-visible portions of the tin (right now I'm rendering everything regardless of level of zoom)
* icon for the layer
* pop-up menu for the layer
* internationalization
* javadoc'ing

--Christopher