Path to this page:
./
geography/spatialindex,
Robust spatial indexing methods
Branch: CURRENT,
Version: 2.0.0,
Package name: spatialindex-2.0.0,
Maintainer: gdtThe 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: 492.982 KB
Version history: (Expand)
- (2026-05-18) Updated to version: spatialindex-2.0.0
- (2025-10-24) Package has been reborn
- (2025-10-24) Package deleted from pkgsrc
- (2025-07-15) Package has been reborn
- (2025-07-15) Package deleted from pkgsrc
- (2023-02-16) Updated to version: spatialindex-1.9.3
CVS history: (Expand)
| 2026-05-18 17:36:44 by Greg Troxel | Files touched by this commit (4) |
Log message:
geography/spatialindex: Update to 2.0.0
packaging NEWS:
Note that 2.0.0 is not the latest release. As described on qgis
lists, 2.1.0 changed how nearest neighbor queries with custom
functions work and it does not seem possible to use them correctly.
Thus pkgsrc is avoiding 2.1.0, as recommended by qgis.
Not mentioned in upstream NEWS:
shlib version changed from 6.1.1 to 7.0.0
upstream NEWS content;
2.0.0 has been released on 07 JUNE 2024. There are no significant
major enhancements or refactorings that should change any
behaviors. It had been a long time (almost 5 years!) since a release
and 2.0.0 was the next version number...
Changes of Note
Added Ball Shape for point neighborhood queries by @Plaba in #232
libspatialindex no longer emits debugging lint to stderr 0e26d16
Build configuration
Fix MinGW build by @SpaceIm in #185
Allow building static libs by @SpaceIm in #183
cmake targets by @hobu in #186
CMakeLists.txt: fix CMAKE_BUILD_TYPE by @ffontaine in #188
.gitignore: remove mostly autconf/automake components, add build by \
@mwtoews in #192
CMake: modern formatting and features by @mwtoews in #196
CMake: deprecate SIDX_BUILD_TESTS with CTest's BUILD_TESTING option by \
@mwtoews in #197
CMake: fix find_package(libspatialindex) by @mwtoews in #199
pkg-config: restore functionality (via CMake), change Cflags by @mwtoews \
in #201
Export target namespace as 'libspatialindex' in CMake Targets #205 by \
@hobu in #207
Fix building static libs by @m-kuhn in #223
Modernize CMake configuration by @hobu in #240
Release package building by @hobu in #242
|
| 2025-09-16 02:56:01 by Greg Troxel | Files touched by this commit (1) |
Log message:
geography/spatialindex: Add upstream bug report URL
|
| 2025-09-16 02:43:35 by Greg Troxel | Files touched by this commit (1) |
Log message:
geography/spatialindex: Take MAINTAINERship and warn against upgrades
Versions >= 2.1 are buggy, causing incorrect results in qgis.
|
2023-02-16 00:17:32 by Thomas Klausner | Files touched by this commit (4) |  |
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.
|