back to home

opengeospatial / geoapi

GeoAPI provides a set of interfaces in programming languages (currently Java and Python) for geospatial applications. The GeoAPI interfaces closely follow OGC specifications, adaptated to match the expectations of programmers.

135 stars
42 forks
24 issues
JavaPythonHTML

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing opengeospatial/geoapi in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/opengeospatial/geoapi)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

GeoAPI interfaces for OGC/ISO conceptual models GeoAPI provides a set of Java and Python language programming interfaces for geospatial applications. The interfaces developed by the GeoAPI project include data structures and manipulation methods needed for geographic information system applications. The GeoAPI interfaces closely follow the abstract models 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 standards. The current release is GeoAPI 3.0.2, published as an Open Geospatial Consortium standard and available on Maven Central. Development branches on GitHub are "3.1" for GeoAPI 3.1 (backward compatible with GeoAPI 3.0) and "master" for GeoAPI 4.0. The main sub-directories are: • **geoapi** contains the normative interfaces proposed for next GeoAPI releases. • **geoapi-pending** contains experimental interfaces not yet targeted for a release. • **geoapi-conformance** contains a test suite for testing vendor implementations. • **src/main/metanorma** contains the GeoAPI specification. • Other directories are build tools or examples. See the wiki page for the roadmap and completion status. Development snapshots GeoAPI development branches require Java 18 and Maven 3 for building, but the compilation result can be run on Java 11. The GeoAPI 3.0 stable release requires only Java 8. • **OGC specification** is built in HTML format with .\ The output file will be created in the directory. • **Java interfaces** are built as a Java Archive File (JAR) with .\ The output file will be created in the directory. • **Python interfaces** are located in the sub-directory and do not need to be built.