Christopher, Thanks for the update.
You wrote: "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?" I haven't done a code review yet, but it sounds more logical to start with just simple feature layers as the input. It sounds like you'll have to do that anyways to support "optional layers containing breaklines and boundaries" with the .bil files. I always favor a modular approach if possible. I wouldn't worry about testing "massive data sets" just yet. When we get something working on a small dataset we can tackle larger data sets. :] Besides, I'll bet we can track down some vector input for JTin from somwhere. We can import a DXF of some polylines from one of my topo surveys if we have to. Still, your work has been excellent so far and I will trust your judgement on how to proceed. Let's see what the other guys think. The Sunburned Surveyor P.S. - This e-mail reminded me about the code review. I will try to squeeze this in tonight after dinner. On Tue, Jul 1, 2008 at 4:05 PM, Christopher <[EMAIL PROTECTED]> wrote: > 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 > > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
