Endpoint · computePOSTapi.geoprimitives.dev /v1/pip
Answer which of your points fall inside which of your polygons, in one call.
Read more
Answer which of your points fall inside which of your polygons, in one call. Use it to tag events with the district, catchment or territory they belong to, to filter a point set down to a study area, or to join two datasets that share nothing but geography. The answer comes back twice, as a dense 0/1 matrix and as a per-point list of polygon indices, so neither shape needs rebuilding on your side, and polygon ids are echoed as column labels so the matrix joins straight back to your records. Rings must be closed and coordinates must be EPSG:4326: run POST /v1/geojson/repair first if they are not, and POST /v1/transform if they are not in degrees. Costs scale with polygon detail, not just polygon count, so POST /v1/geometry/simplify on the polygons is often the cheapest way under the caps. The matrix is dense: every point is tested against every polygon, one row per point and one column per polygon, 1 for inside and 0 for outside. A point exactly on an edge or vertex counts as inside unless "ignoreBoundary" is set. Two caps, both on products rather than on either side: at most 250000 point-polygon pairs, and at most 25000000 point-vertex tests, since a ray cast walks every edge. Input is EPSG:4326, longitude then latitude. Limits: 250000 points, 2000 polygons, 100000 polygon positions, and a 1 MiB request body.Overview
Grade?
UNRATED
0 of 30 paid calls toward a letter
Price
$0.01 per call
Paid calls
none yet
delivery unknown until someone pays
More info
Seller?
URL
https://api.geoprimitives.dev/v1/pip
Seen
first 34 days ago · last 14 days ago
51 free handshakes
Payment
Pays through
— never asked
Offered on?
— never asked
Listed on?
Base
About
- ?Description
- Answer which of your points fall inside which of your polygons, in one call. Use it to tag events with the district, catchment or territory they belong to, to filter a point set down to a study area, or to join two datasets that share nothing but geography. The answer comes back twice, as a dense 0/1 matrix and as a per-point list of polygon indices, so neither shape needs rebuilding on your side, and polygon ids are echoed as column labels so the matrix joins straight back to your records. Rings must be closed and coordinates must be EPSG:4326: run POST /v1/geojson/repair first if they are not, and POST /v1/transform if they are not in degrees. Costs scale with polygon detail, not just polygon count, so POST /v1/geometry/simplify on the polygons is often the cheapest way under the caps. The matrix is dense: every point is tested against every polygon, one row per point and one column per polygon, 1 for inside and 0 for outside. A point exactly on an edge or vertex counts as inside unless "ignoreBoundary" is set. Two caps, both on products rather than on either side: at most 250000 point-polygon pairs, and at most 25000000 point-vertex tests, since a ray cast walks every edge. Input is EPSG:4326, longitude then latitude. Limits: 250000 points, 2000 polygons, 100000 polygon positions, and a 1 MiB request body.
- URL
- https://api.geoprimitives.dev/v1/pip
- Method
- POST
- Class
- compute
- ?Checkable to
- L1
- Endpoint id
- cap_01M1A59RVRPYC77WXGX0N8DFPZ
- ?Badge
Reads live. UNRATED until paid calls earn a letter.
- Markdown
- [](https://teppi.xyz/endpoint/cap_01M1A59RVRPYC77WXGX0N8DFPZ)
- HTML
- <a href="https://teppi.xyz/endpoint/cap_01M1A59RVRPYC77WXGX0N8DFPZ"><img src="https://api.teppi.xyz/badge/cap_01M1A59RVRPYC77WXGX0N8DFPZ.svg" alt="Teppi delivery record"></a>
- Image
- https://api.teppi.xyz/badge/cap_01M1A59RVRPYC77WXGX0N8DFPZ.svg
Verify it yourself
npx teppi-check https://api.geoprimitives.dev/v1/pipcurl -s https://api.teppi.xyz/v1/trust/cap_01M1A59RVRPYC77WXGX0N8DFPZ