SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

 
 

geoapi rpm build for : Other. For other distributions click geoapi.

Name : geoapi
Version : 2.3 Vendor : jPackage project
Release : 0.M1.1.jpp6 Date : 2010-10-14 19:16:19
Group : Development/Libraries Source RPM : geoapi-2.3-0.M1.1.jpp6.src.rpm
Size : 0.52 MB
Packager : Ralph Apel < r_apel_r-apel_de>
Summary : Java APIs por geospatial applications
Description :
GeoAPI provides a set of Java language programming
interfaces for geospatial applications.
The interfaces developed by the GeoAPI project include many
of the data structures and manipulation methods needed for
geographic information system applications. In a series of
independent packages, GeoAPI defines a core set of
interfaces for metadata handling, for geodetic referencing,
projection and conversion, for the handling of georeferenced
imagery, for the construction and manipulation of vector
geometry and tological data structures, and for the
description and use of geospatial \'feature\' entities. Beyond
this core, GeoAPI further defines interfaces for data access
and storage including sophisticated filter queries, and for
display.

The GeoAPI interfaces closely follow the abstract model and
concrete specifications published collaboratively by the
International Organization for Standardization (ISO) in its
19100 series of documents and the Open Geospatial Consortium
(OGC) in its abstract and implementation specifications.
GeoAPI provides an interpretation and adaptation of these
standards to match the expectations of Java programmers.
These standards provide GeoAPI with the richness which comes
from the expertise of the specification writers. Clients
benefit from the potential for inter-operability which comes
from using a well defined, standardized data model.
Implementors benefit from having a pre-defined set of well
considered, formal boundaries to modularize their development
work.

The GeoAPI interfaces provide a layer which separates client
code, which would call the API, from library code, which
implements the API. These interfaces are not an implementation.
This follows a similar pattern to the well known JDBC API which
provides a standardized interface to databases. Clients can use
the JDBC API without concern for the particular implementation
which they will use. Various groups have implemented different
subsets of GeoAPI, see the list of known implementations for
details.

RPM found in directory: /packages/linux-pbone/archive/www.jpackage.org/jpackage/6.0/generic/devel/RPMS

Content of RPM  Changelog  Provides Requires

Download
ftp.icm.edu.pl  geoapi-2.3-0.M1.1.jpp6.noarch.rpm
     

Provides :
geoapi

Requires :
rpmlib(CompressedFileNames) <= 3.0.4-1
/bin/sh
jpackage-utils => 0:1.7.5
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
java => 1.6.0
jsr275


Content of RPM :
/etc/maven/fragments/geoapi
/usr/share/java/geoapi
/usr/share/java/geoapi/conformance-2.3.jar
/usr/share/java/geoapi/conformance.jar
/usr/share/java/geoapi/examples-2.3.jar
/usr/share/java/geoapi/examples.jar
/usr/share/java/geoapi/geoapi-2.3.jar
/usr/share/java/geoapi/geoapi-pending-2.3.jar
/usr/share/java/geoapi/geoapi-pending.jar
/usr/share/java/geoapi/geoapi.jar
/usr/share/java/geoapi/tools-2.3.jar
/usr/share/java/geoapi/tools.jar
/usr/share/maven2/poms/JPP.geoapi-conformance.pom
/usr/share/maven2/poms/JPP.geoapi-examples.pom
/usr/share/maven2/poms/JPP.geoapi-geoapi-pending.pom
/usr/share/maven2/poms/JPP.geoapi-geoapi.pom
/usr/share/maven2/poms/JPP.geoapi-parent.pom
/usr/share/maven2/poms/JPP.geoapi-tools.pom

 
ICM