Polaris Geometry Framework
From BluWiki
Contents |
Introduction
The open source community currently lacks a standard for describing 3D geometries and the operations and manipulations that can be performed upon those geometries. The Polaris Geometry Framework will provide that, and more. The framework will store its data using elements of the LocusXML standard, allowing it to be implemented in different programming languages.
The Name
Why is it called a framework, and not a library? A library provides classes for resuse. A framework provides these classes and the structure needed to integrate them into applications.
Why is the framework named Polaris? Polaris is another name for the North Star. The north star was used by explorers, navigators, astronomers, and cartogrophers throught history as a reliable indicator of true or astronomic north. (You can learn more about Polaris here: Polaris at Wikipedia) The Polaris Geometry library is designed primarily for geospatial applications. Therefore, the name seems appropriate.
Framework Features
What are the planned features for the Polaris Geometry Framework?
- 3D Geometry Definitions (Including 3D Solids)
- 3D Geometry Operations (3D Buffer, 3D Intersection Calculations...)
- Persistent Storage In XML Format
- No Limits On Coordinate Value Size
- Integrated Positional Precision Information and Positional Error Tracking
- 3D Topology and Data Validation Rules
- Tracking and Manipulation of Spatial Relationships
- 3D Spatial Index
Current Status
The standard for the Polaris Geometry Framework is currently being developed in conjunction with the first implementation of the standard, as part of the OpenJUMP-Ex OGD Implementation. (This implementation will be in Java.)
Polaris Geometry Framework Development
Learn more about development of the framework @ the Polaris Geometry Framework Development wiki page.
