Howard Butler wrote:
>> "... providing the index's dimension * 2 coordinate pairs representing
>> the mink and maxk coordinates in each dimension defining the bounds of
>> the query window."
>>
> Care to come up with some text that's not so confusing? I'll incorporate it
> before the next release.
How about this... a little repetitive but I find it clearer.
Original:
:param coordinates: sequence or array
This may be an object that satisfies the numpy array
protocol, providing the index's dimension * 2 coordinate
pairs representing the mink and maxk coordinates in
each dimension defining the bounds of the query window.
Proposed change:
:param coordinates: sequence or array
Dimension * 2 coordinate pairs, representing the min
and max coordinates in each dimension of the item to be
deleted from the index. Their ordering will depend on the
index's :attr:`interleaved` data member.
These are not the coordinates of a space containing the
item, but those of the item itself. Together with the
id parameter, they determine which item will be deleted.
This may be an object that satisfies the numpy array protocol.
> Excellent. Can you describe what you're using Rtree for? I'm really
> interested in how people are using it, and for what kind of data.
The Graphserver project (public transit route planning) is using Rtree
to find nodes in road and public transit systems that are close to one
another. I am experimenting with different strategies for deciding which
street is closest to a transit stop and creating new nodes when necessary.
Thanks again,
Andrew
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community
