GeoTools GeoTools is a Java toolkit for geospatial applets, applications, and services.
Download

GeoTools Ranking & Summary

GeoTools Tags

Java Toolkit Java toolkit geospatial applets geospatial applications GeoTools

GeoTools Description

GeoTools is a Java toolkit for geospatial applets, applications, and services. Geotools is an open source Java GIS toolkit for developing standards compliant solutions. GeoTools project provides an implementation of Open Geospatial Consortium (OGC) specifications as they are developed.Geotools maintains an open development process, with public collaboration on new ideas . Project communication is open to all , and we welcome new contributions . Here are some key features of "GeoTools": Data Formats: · Geotools tries to support as many data formats as possible. · The DataStore interface is used to access vector data. DataStore: Data formats supported are: · Shapefile - an ESRI shapefile (R/W) · GML - Geography Markup Language (R) · PostGIS - geometric objects for PostgreSQL (R) · Oracle Spatial - Oracle's extension for spatial data (R) · ArcSDE - ESRI's middleware for spatial databases (R) · MySQL - support for the new geometry types · GeoMedia - an Intergraph format (R) · Tiger - Topologically Integrated Geographic Encoding and Referencing developed at the US Census Bureau (R) · VPF - Vector Product Format, a data interchange format (R) Features and Geometries: · Features are used to represent basic geographic elements in a vector system. These are composed of both geometries and attributes. · Java Topology Suite (JTS) is used as the current geometry model. This library is an implementation of the Simple Features Specification for SQL, http://www.opengis.org/docs/99-049.pdf. It also provides in memory spatial indexing support and robust topologic operations, though they are not used much at present in the codebase. · If you're willing to add some vector computation operations (for example, overlay) please step up: we need someone willing to work on an operation API and the associated implementations. See the Operations API page for more information. Grid coverages: · A grid coverage provides support for the raster data format, that is, a georeferenced grid of numbers that can be used to represent data ranging from satellite images, to digital elevation models, noise distribution and so on. See also the OpenGIS specification about grid coverages, http://www.opengis.org/docs/01-004.pdf. · Grid coverages are based on the JAI library which provides support for data management, presentation, image data format access, tiling support, a framework for raster data processing with lots of predefined operators. Coordinate Transformation: · The cts-coordtrans (CTS) module implements a subset of the OGC's Coordinate Transformation Services specification, http://www.opengis.org/docs/01-009.pdf. It provides an implementation for general positioning, coordinate reference systems, and coordinate transformations. · Types of transformations provided include datum shifts, map projections (Mercator, Transverse Mercator, Lambert Conformal Conic, Albers Equal Area Conic, Stereographic, Orthographic) and others. Renderers: Geotools has two renderer implementations: · LiteRenderer - a 'stateless' renderer, particularly useful in server-side environments. Main features: code simplicity and low memory footprint, but it's faster than J2D only for the first map rendering. · J2D - a 'stateful' renderer with optimizations for update rate, good for interactive client-side displays. It's way more complex but supports on the fly coordinate reprojection, fast update by intelligent data decimation and memory caching. Styling: · Allows for symbolizing (colour, line thickness, opacity, etc.) of datasets. This is closely modeled on, and fully supporting, the OpenGIS Styled Layer Descriptor specification, http://www.opengis.org/docs/02-070.pdf. These can be stored as XML documents. Filter Encodings: · Filters provide a way to specify a subset of features to operate on. This supports both attribute and spatial constraints and a method of storing these as XML documents. · This is an implementation of the Filter Encoding specification, http://www.opengis.org/docs/02-059.pdf Graph: · Allows the creation of graphs and networks based on MultiLineStrings or arbitray Geometries and Spatial Relationships. Graphs can be walked using the visitor pattern. Common walks, such as shortest route, are already available. Other walks may also be defined by the user. Validation: · This provides a method to validate features base on different constraints. Allows the definition of test suites based on validaiton plug-ins. Tests suites (and indeed validaiton plug-ins) are configured using xml files. · A working validation Processor is provided as a demo. Requirements: · Java 1.4.x · The Java Advanced Imaging Libraries (JAI) · The Java Advanced Imaging Image I/O Tools · The JAI and the JAI I/O Tools What's New in This Release: Sub-task: · - Remove old filters/expressions usage from xml-xsd · - Remove old filter usage from the validation module Bug: · - Trunk build broken by geoapi-2.2-SNAPSHOT · - net.opengis.ows10.DomainType.getValue() has wrong multiplicity. · - XSAnyURIBinding bound to java.net.URI causes parsing problems, it should be bound to java.lang.String · - net.opengis.wfs.FeatureTypeType.getOtherSRS() has wrong multiplicity · - CRS.toSRS doesn't work if the WKT or HSQL factory. · - V1.0.0 Commit sometimes fails to resolve schema when encoding xml commit Improvement: · - Allow Square Bracket in search condition · - JDBCFeatureSourceTest cannot work with DB2 Spatial Extender · - JDBCFeatureReader should ensure CRS is set for geometries returned · - Improve spatial filter performance with Prepared Geometries · - ability to not turn on/off feature bounds in encoded features · - Support FeatureType in FeatureTypeCache New Feature: · - Allow bindings to declare their contents should not be parsed further · - Allow third party objects to perform custom encoding in selected places · - WPSCapabilitiesType missing the xml:lang attribute · - Validating WPS caps responses using Parser fails · - Some WPS model objects are missing the xml:lang attribute · - WPSCapabilites.version does not get encoded · - WPS ProcessDescription.processVersion does not get encoded · - Reserve Areas of the Screen from the Labelling process Task: · - Make sure it's possible to compute bounds out of a view · - Change TXT by ECQL

GeoTools Related Software