Michael Wang
Michael Wang
Today the python computation API accepts raw structure of arrays input. Such as: https://github.com/rapidsai/cuspatial/blob/da1cb97a4df308b9d27566e4c9d9736ca06a9582/python/cuspatial/cuspatial/core/gis.py#L29 and https://github.com/rapidsai/cuspatial/blob/da1cb97a4df308b9d27566e4c9d9736ca06a9582/python/cuspatial/cuspatial/core/gis.py#L166-L173 The history of this input interface is that cuspatial was used to accelerate specific...
After #558 is merged, we should introduce python interface that's similar to the linestring distance interface introduced in #521.
This PR contributes to #231, and should supercede #251 .
Orginally ported from https://github.com/rapidsai/cuspatial/pull/558#discussion_r906307896 Considering the `st_distance` covers many geometry combinations, there needs to be a way to make each distance primitive easy to find by users. ## File Organizations...
According to [development doc](https://github.com/rapidsai/cuspatial/blob/branch-22.08/cpp/doc/libcuspatial_refactoring_guide.md#example-api), to be consistent with `std::transform` API, the method should return the output iterator to one past the last element being written to by the algorithm. Currently,...
In general, `polyline` and `linestring` both refers to a data structure that contains multiple points with the line segments that connect the points. `Linestring` is standardized in GIS systems through...
During #523 , I noticed many methods in cuSpatial are documented in one place, but the actual definition is in another. For example: **Location of incorrect documentation** `polyline_bounding_boxes` is under...
During reviewing https://github.com/rapidsai/cuspatial/pull/514, I realized that the documentation of `lonlat_to_cartesian` may be lacking, or the naming of the method is too general. AFAIK, converting lonlat to cartesian coordinates involves projections...
## Report incorrect documentation  User guide should be on the doc site's banner for visibility, the same as API reference and developer guide.