History log of /6.6.0/geocouch/gc-couchdb/include/couch_spatial.hrl (Results 1 - 7 of 7)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 5926e04f 10-Jun-2016 Volker Mische <vmx@couchbase.com>

Remove plane_bounds query parameter

The `plane_bounds` query parameter was a bad idea and it also doesn't
make much sense in the multidimensional context. Hence it's removed.

Ch

Remove plane_bounds query parameter

The `plane_bounds` query parameter was a bad idea and it also doesn't
make much sense in the multidimensional context. Hence it's removed.

Change-Id: Ib8942264efe6db34f7d17b4c77fff4835fe4678f

show more ...


# 8f6d728c 10-Jun-2016 Volker Mische <vmx@couchbase.com>

MB-12251: Improve query parsing errors

Add more end-user friendly error messages when the query parameter
are invalid. This commit also adds tests.

This is a port of f4753a3f35c

MB-12251: Improve query parsing errors

Add more end-user friendly error messages when the query parameter
are invalid. This commit also adds tests.

This is a port of f4753a3f35ca34863c32cac9d63a29be6fe1db59 to the
Apache CouchDB compatible version for GeoCouch (without tests).

Change-Id: I88b829eca0211007f536d89aeb84f06b97c8aa28

show more ...


Revision tags: 2.1.1r, 2.1.0r
# 283da2dc 13-Mar-2013 Volker Mische <vmx@couchbase.com>

MB-7904: Use byte size instead of number of nodes

The R-tree now uses the byte size of the nodes to determine
how many children a node can hold. Previously it was determined
by a min

MB-7904: Use byte size instead of number of nodes

The R-tree now uses the byte size of the nodes to determine
how many children a node can hold. Previously it was determined
by a minimum and a maximum number of nodes.

This step was taken to make the R-tree work more like the
B-tree code.

Change-Id: Ifc4f08110a9ebe11385e0bbb63a53b34de732691
Reviewed-on: http://review.couchbase.org/25138
Tested-by: buildbot <build@couchbase.com>
Reviewed-by: Filipe David Borba Manana <fdmanana@gmail.com>

show more ...


Revision tags: 2.0.1-linux
# c29f02c5 15-Jan-2013 Volker Mische <vmx@couchbase.com>

MB-100: Default fill_min/fill_max to `nil`

fill_min/fill_max in the #vtree{} record are `nil` by default
and will set by the corresponding API (Couchbase or Apache CouchDB).

Cha

MB-100: Default fill_min/fill_max to `nil`

fill_min/fill_max in the #vtree{} record are `nil` by default
and will set by the corresponding API (Couchbase or Apache CouchDB).

Change-Id: I11814f6982f5792c3f07f73a4770811e6cc294af
Reviewed-on: http://review.couchbase.org/25135
Tested-by: buildbot <build@couchbase.com>
Reviewed-by: Filipe David Borba Manana <fdmanana@gmail.com>

show more ...


Revision tags: 2.0.2r
# 3d063833 04-Dec-2012 Volker Mische <vmx@couchbase.com>

MB-7013: Add support for multidimensional indexes/queries

You can now create and query multidimensional indexes. Those
indexes can contain a geometry, but don't need to. The only
dif

MB-7013: Add support for multidimensional indexes/queries

You can now create and query multidimensional indexes. Those
indexes can contain a geometry, but don't need to. The only
difference is, that you now emit an array of ranges.

If you want to emit a geometry, then it needs to be the first
element in the array. An example would be:

emit([{"type": "Point", coordinates: [0, 0]}, [100, 350]]);

This would build a 3-dimensional index, two dimensions for the
geometry, one for the second range. In case the additional ranges
are simply points (have no dimension), you can also emit a simple
value:

emit([{"type": "Point", coordinates: [0, 0]}, 254]);

As mentioned before, you don't need to emit a geometry. But
make sure that all values you emit are numeric:

emit([30, 40], 254, [0, 1], 9]);

To query this multidimensional index, two new parameters are
introduced: `start_range` and `end_range`. Both take an
array as input, the `start_range` contains the lower values,
the `end_range` the upper ones.

If you want to have an open range, just put in `null` as a value.
If `start_range` and `end_range` contains `null` for a certain
dimension, it's like a wildcard, it will match all values.

Example:

<spatial-endpoint>>?start_range=[10,70,null]&end_range=[20,null,200]

Change-Id: I94661acc4b6638ef4306c5bb31a4cedf8104aa73
Reviewed-on: http://review.couchbase.org/25132
Tested-by: buildbot <build@couchbase.com>
Reviewed-by: Filipe David Borba Manana <fdmanana@gmail.com>

show more ...


# 70c86024 03-Dec-2012 Volker Mische <vmx@couchbase.com>

MB-7013: Make the new vtree work with Apache CouchDB

This commits makes the new vtree work with Apache CouchDB 1.3.x.
All GeoCouch JavaScript tests pass. You should be able to use it

MB-7013: Make the new vtree work with Apache CouchDB

This commits makes the new vtree work with Apache CouchDB 1.3.x.
All GeoCouch JavaScript tests pass. You should be able to use it
as a replacement for your current installation.

Change-Id: I6e42fc8149c447a294a52955a8b576b80ba00c74
Reviewed-on: http://review.couchbase.org/22994
Tested-by: buildbot <build@couchbase.com>
Reviewed-by: Filipe David Borba Manana <fdmanana@gmail.com>

show more ...


# e4df0e62 08-Nov-2012 Volker Mische <vmx@couchbase.com>

MB-7013: Add the APIs for Apache CouchDB 1.3.x

I just copied over the source from the old code base as a start.
Next commits will make it actually work. This also includes the
JavaSc

MB-7013: Add the APIs for Apache CouchDB 1.3.x

I just copied over the source from the old code base as a start.
Next commits will make it actually work. This also includes the
JavaScript tests.

Change-Id: Ie858efc1cb88a73f94c25937afff815502923f71
Reviewed-on: http://review.couchbase.org/22993
Tested-by: buildbot <build@couchbase.com>
Reviewed-by: Filipe David Borba Manana <fdmanana@gmail.com>

show more ...