The content presented in the Spatial Toolbox interface is automatically generated by obtaining and parsing the metadata attached using annotations provided by the underlying OMS3. Tabs in the right-hand side of the window allow access to data input, data output and the description for each fi eld of the selected component. The uDig Spatial Toolbox contains all the required tools for the management of raster maps (import, export, manipulation) and also provides the geomorphological analysis packages, necessary for the preparation of input data for JGrass-NewAge, derived from The Horton Machine (Rigon et al., 2006a,b). On the left-hand side of the window, folder-type icons identify available model components. Its interface allows the individual execution of models and components of JGrass-NewAge. The uDig spatial toolbox (uST) is depicted in Fig. The system is based on Java and it integrates seamlessly with the other tools that form the JGrass-NewAGE system. The Spatial Toolbox (see below) allows the execution of most of GRASS commands. It can manage the GRASS raster data format natively. Since version 1.2, uDig is compatible with the GRASS GIS (Neteler and Mitasova, 2007). It also uses the ImageIO-ext project ( providing access to raster formats supported by GDAL (. The core GIS functionalities, such as data reading, coordinate re- projection, rendering, etc., are provided in uDig by the GeoTools library, which allows convenient management of vector data. uDig contains not only elements for map visualization, but also tools for data manipulation, editing, map printing, and connection with remote databases and servers (Oracle, SDE, Postgres/PostGIS, Teradata, and others). It has a very fl exible plugin-in mechanism to add features and to customize the user interface, but most importantly it is supported by a very solid industrial foundation (the list of Eclipse members can be found at: showAllMembers.php). Its interface is built upon the Eclipse rich client platform, guar- anteeing a native look-and-feel in any of the operating systems. Hence it is capable of using geodata served via standards such as Web Feature Services (WFS), Web Map Services (WMS), Web Coverage Services (WCS), GeoRSS, and KML. uDig runs as a rich client under different platforms (Windows, Mac OS/X and Linux) it is web- service oriented. Eventhough the uDig project is not a key aspect of this paper it is useful to point out some of its main characteristics. The GIS interface is currently built on uDig 1.3.1 (uDig stands for User friendly Desktop Internet GIS) as shown in Fig. The next three subsections present the JGrass-NewAGE parts in more in detail. ![]() ![]() However, interoperability with R as external tool was already added to OMS as an experimental feature. 1, on the basis of the same tools developed for research, which is not possible using only the R language. ![]() Furthermore, we wanted to maintain the possibility of building entire operational systems, as the one depicted in Fig. uDig inherits the tools for the treatment of geographical entities from the GeoTools Toolkit ( R ( was also considered as an alternative, but discarded since it does not offer enough fl exibility and ef fi ciency for intensive computational Modelling, eventhough it is powerful for post processing of model results, graphics and automatic calibration tools. This ful fi lls the additional requirement of using a completely open-source tool chain for development, which may simplify its adoption by models developers. Eclipse was also chosen as IDE for compiling and developing models. Using uDig as a basis also implied the use of Eclipse as the Rich Client Platform (RCP) for part of the project. While we wait the team will continue working on the 1.4.0 release which will be our last release under the Refractions banner. If you would like a sneak peak, the documentation is online, including the What is New page. We have also enjoyed taking part in the LocationTech industry out reach including a recent video presentation on uDig by Jody Garnett and Frank Gasdorf. The completion of this review for the uDig project lowers risk for everyone involved and makes the project easier to deploy. One of the initial benefits is access to the Eclipse Foundation intellectual property services. While we are confident our codebase is in good shape, the review by the independent IP team is an important step for the uDig project. The costs associated with intellectual property services is a prohibitive constraint on the adoption of open source in general. The uDig team is busy filling in the paperwork to access LocationTech facilities, and will be migrating the codebase shortly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |