Sure. It is probably a somewhat weird use of a gis toolkit, however, since we need to have really fast random access to the data model (DataStore). The application is a (soft) real-time monitoring and decision support tool which monitors a large geographically distributed network of processing nodes (in addition to moving vehicles), each of which sends status updates "quite often".
So unfortunately we will not be using any of the database functionality of GeoTools, as that would be too slow. We had a prototype using ArcSDE with Oracle, but it was way too slow for our use. Actually the flexibility of the GeoTools DataStore API was the main reason we switched to it, as that would allow us to implement a custom DataStore for performance. So we have implemented a DataStore which holds everything in memory, like the MemoryDataStore, but using the JTS QuadTree for spatial indexing. Yes, I realize everyone else who is using GIS for a serious product is storing the data in a database :) We don't need the robustness and security of a database though, since data loss is not a problem. This being a GUI application we are using a lot of the components in the render and swing modules of GeoTools. We are using the StreamingRenderer for rendering, and ZoomPane is the base class of our "map" component. To enable user-driven selection of features (e.g. selection by drawing a rectangle or polygon), we have extended the MapContext and MapLayer interfaces. Also, we need to have generalization of certain features to reduce clutter and improve rendering performance. Exactly how to do this we have not yet decided. Generalization without selection is quite easy, as that is just to use the minimum and maximum scale denominators in the style, but we need to have user-selectable generalized features somehow. Anyways, if we can clean up our DataStore and GUI components, then maybe this code would be interesting for other people who are using GeoTools in strange and unusual ways. Sorry for not being able to work on your database modules though :) Regards, Erik Loevlie Jody Garnett wrote: > Very cool; from our standpoint it is *very* important to get you and > your team happy; and contributing to GeoTools. Could you tell me a bit > more about aspects of the library you are using? If you are going to > be with us for a while it would be worth your while to become involved > - especially if you are thinking of any of the unsupported modules > (like oracle). > > GeoTools has been considered unstable for most of its life (this > feature model thing has really held us back). From my standpoint > GeoTools is almost done; after this SimpleFeature thing there is only > Style and MapContext to clean up and document. > > All the best, > Jody > PS. Jump on the #geotools IRC channel and say hi to people if you get > a chance. >> Saul Farber, Jody Garnett: >> >> Thanks for the info. I am indeed trying to do project planning around >> GeoTools. Currently we are trying to decide when to start porting our >> application from 2.3.2 to the milestone builds of version 2.4 >> (currently 2.4-M4 I believe). I think we will wait for the release >> candidate before porting. >> >> We are two full-time developers working on this application, and the >> development will continue in its current phase for about a year. Once >> the application is released, the lifespan is actually very long. The >> predecessor has been in use for about 10 years. So I do expect you >> will see one or two jira-issues and such from us in the near and >> distant future :) We will probably donate some code as well, once we >> have cleaned it up (and if you guys want it). >> >> Regards, >> Erik Loevlie >> >> >> Jody Garnett wrote: >>> Erik Løvlie wrote: >>>> Hi, does anybody know or have some vague idea of when 2.4 is due to >>>> be released? >>>> >>> Justin is working on it, if you would like to help (or see the >>> issues standing in the way of the release) visit the 2.4.x page: >>> - http://docs.codehaus.org/display/GEOTOOLS/2.4.x >>> >>> We generally use the wiki to communicate status information. >>>> Also: there is a version 2.4 and a version 2.5, which one is the >>>> target for active development? >>>> >>> Both, >>> - 2.4 is near the end of its cycle (the next release will be a >>> release candidate with no more functionality changes expected before >>> 2.4.0). >>> - 2.5 is focused on switching over to a SimpleFeature interface >>> (this is the end of a three year long effort that has taken place >>> mostly on branches) >>> >>> For the last road map: >>> - http://docs.codehaus.org/display/GEOTOOLS/2007+Q2 >>> >>> Hunt around on the wiki for a bit and ask if you have any more >>> questions. If you are trying to do project planning around GeoTools >>> please talk to us early and and often, we will often bend over >>> backwards to help (especially if you helping out with developers or >>> testing). You may also consider one of the organizations listed on >>> this page: >>> - http://docs.codehaus.org/display/GEOTDOC/09+Communication+and+Support >>> >>> Cheers, >>> Jody >>> >>> >> > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
