./geography/spatialindex, Robust spatial indexing methods

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 1.9.3, Package name: spatialindex-1.9.3, Maintainer: pkgsrc-users

The purpose of this library is to provide:
* An extensible framework that will support robust spatial indexing methods.
* Support for sophisticated spatial queries. Range, point location, nearest
neighbor and k-nearest neighbor as well as parametric queries (defined by
spatial constraints) should be easy to deploy and run.
* Easy to use interfaces for inserting, deleting and updating information.
* Wide variety of customization capabilities. Basic index and storage
characteristics like the page size, node capacity, minimum fan-out, splitting
algorithm, etc. should be easy to customize.
* Index persistence. Internal memory and external memory structures should be
supported. Clustered and non-clustered indices should be easy to be persisted.


Required to build:
[pkgtools/cwrappers]

Master sites:

Filesize: 508.61 KB

Version history: (Expand)


CVS history: (Expand)


   2023-02-16 00:17:32 by Thomas Klausner | Files touched by this commit (4) | Package updated
Log message:
spatialindex: update to 1.9.3.

Changes:

4 years of development, convert to CMake, no useful changelog found.
   2021-10-26 12:45:18 by Nia Alarie | Files touched by this commit (108)
Log message:
geography: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes
   2021-10-07 16:09:33 by Nia Alarie | Files touched by this commit (108)
Log message:
geography: Remove SHA1 hashes for distfiles
   2015-11-27 18:51:58 by Adam Ciarcinski | Files touched by this commit (5)
Log message:
The purpose of this library is to provide:
* An extensible framework that will support robust spatial indexing methods.
* Support for sophisticated spatial queries. Range, point location, nearest
  neighbor and k-nearest neighbor as well as parametric queries (defined by
  spatial constraints) should be easy to deploy and run.
* Easy to use interfaces for inserting, deleting and updating information.
* Wide variety of customization capabilities. Basic index and storage
  characteristics like the page size, node capacity, minimum fan-out, splitting
  algorithm, etc. should be easy to customize.
* Index persistence. Internal memory and external memory structures should be
  supported. Clustered and non-clustered indices should be easy to be persisted.