Points in Polygon Helper
Plot points and draw polygons to see which samples fall inside a study area.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, the test point 40.7832, −73.9666 falls inside a drawn four-corner parcel while 40.7580, −73.9855 falls outside it — two verdicts from one ray-casting pass each.
How to use Points in Polygon Helper
Cast a ray, count the crossings — odd is in, even is out:
The Points in Polygon Helper tests whether coordinate points lie inside a polygon — the point-in-polygon question behind geofencing, service areas and jurisdiction checks. Supply the polygon and the points and read an inside or outside verdict for each, computed by ray casting.
- 1Draw a polygon.
- 2Compare with plotted points from CSV tools.
What people use Points in Polygon Helper for
1. Geofence and service-area checks
Is this customer inside the delivery polygon? The verdict list is the operations answer — drawn zones from the Service Area Map family get audited here point by point.
2. Data cleaning
A spreadsheet of sites claims a county; test the coordinates against the county polygon and the impostors confess. At scale this is a GIS join; for a list, it is this page.
3. Jurisdiction and eligibility spot checks
School zones, tax districts, conservation areas — when the question is one point and one boundary, the helper answers without a GIS installation.
4. Learning spatial algorithms
Ray casting is the undergraduate classic: cast a horizontal ray, count edge crossings, odd means inside. Testing your own implementation against this page is the homework's honest mirror.
Worked examples
Against a four-corner test parcel (corners near 40.7663–40.8001 N, −73.9762 to −73.9570 W): the centre point 40.7832, −73.9666 is inside — any ray crosses once. Times Square's 40.7580, −73.9855 is outside — it sits south-west of every corner.
A point exactly on an edge is the algorithm's philosophy exam: floating-point geometry rarely lands exactly on, but surveyed points can. The helper reports boundary points as their own verdict rather than flipping a coin — check its note for the convention in force.
How the verdict is reached
Ray casting in four facts.
| Step | What happens |
|---|---|
| 1. Cast | A ray leaves the test point in a fixed direction (usually east) |
| 2. Count | Each polygon edge the ray crosses adds one |
| 3. Decide | Odd crossings → inside; even → outside |
| 4. Edges cases | Vertices and boundary points follow a stated convention — never luck |
The method works for any simple polygon, concave included — the parcel with a bite taken out is where naive bounding-box tests fail and ray casting earns its keep.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Points in Polygon Helper:
- When exporting polygons for reports, store the radius and unit in the feature properties (the exports here do). Future-you, reopening the file in a GIS, will otherwise have to re-derive what the circle meant.
- Decide geometric vs temporal reach before drawing anything: a 10 km circle and a 15-minute drive area answer different questions, and in car-dependent geography they barely overlap in shape. Circles for policy radii, isochrones for response promises.
Limits & appropriate use
Circles and polygons are geometric truths with semantic limits. A radius says nothing about rivers, one-way systems or response times; an area says nothing about what is inside it. The most expensive misuse is treating a geometric catchment as a service promise — which is why the isochrone tools exist as the temporal counterpart, and why the pages cross-link the two insistently. A second limit is resolution: drawn vertices capture the boundary you click, so curved shores want more clicks, and the perimeter grows (correctly) as you add them — the coastline paradox, politely present in every honest measurement tool.
Within geometry, the numbers are exact on the sphere: areas by spherical excess, boundaries by destination math, exports with their parameters embedded. The escalation ladder is short: cadastral precision needs licensed surveys; population-inside-shapes needs census blocks; drive-time promises need the routing engine. Used as the fast, auditable, shareable geometric layer that feeds those heavier instruments, this is exactly the right tool — and it says so.
- Cadastral/legal area → licensed survey with local datum practice.
- Population inside shapes → census blocks, not city-point sums.
- Response-time promises → isochrones plus operational buffers.
Data & methodology
The current polygon workspace calculates area and perimeter; it does not test a list of points for polygon containment.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- Perimeter
- The summed great-circle length of a drawn boundary.
- Spherical cap
- The true shape of a radius circle on a globe.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Radius & Area. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- The current polygon workspace calculates area and perimeter; it does not test a list of points for polygon containment.
- Before relying on the answer
- Check the centre, radius or drawn vertices and the selected units. A geometric footprint does not describe which roads or entrances are accessible.
- What the result cannot establish
- A radius is not a travel-time guarantee. For parcel boundaries or legal land area, use an authoritative survey.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
Batch PIP?
Visual check here — large joins belong in spatial databases.
Is a radius the same as driving distance?
No. A radius is a geometric circle around a centre point. Driving reach depends on the road network and usually has an irregular shape.
Can I use this for service-area planning?
Yes for first-pass planning. Use a drive-time or road-network tool when accessibility matters more than straight-line coverage.
Are map measurements legal survey measurements?
No. MapBench measurements are planning/reference outputs unless a page explicitly states otherwise. Use a licensed surveyor for legal boundaries.
What counts as the polygon?
A closed ring of coordinates in order — the boundary the points are tested against. Self-intersecting rings produce meaningless verdicts; keep the boundary simple, as with area measurement.
Points exactly on the boundary?
Reported under a stated boundary convention (commonly counted as inside for geofencing, or flagged separately). For legal boundary questions, only the survey decides — the helper flags the case rather than ruling on it.
Holes in the polygon?
A courtyard or exclusion zone is a hole ring: points inside the hole are outside the effective polygon. Supply the hole ring where the tool accepts one; otherwise test and invert manually.
Which coordinate order?
Latitude, longitude — this site's convention. Longitude-first lists are the classic silent failure: the polygon lands in the ocean and every verdict is 'outside', correctly and uselessly.
Curved Earth effects?
At parcel and city scales the planar test is exact enough; continental polygons deserve spherical point-in-polygon, which the geodesy tools discuss. Match the method to the polygon's size.
Thousands of points?
Lists here; databases and GIS spatial joins at industrial scale. The verdicts must agree — spot-check the industrial output against this page's first principles.
Multiple polygons (a district of zones)?
Test each polygon in turn; a point's membership is per-polygon, and overlaps are possible where zones overlap. The helper keeps the questions separate so the answers stay true.
Why not use a bounding box?
Boxes are the fast pre-filter, not the verdict: a concave polygon's box contains much outside ground. Ray casting is the verdict the box only advertises.
Related tools and resources
Draw the area: the Map Area Calculator; its boundary: the Perimeter Calculator; centres: the Center of Polygon.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our area & acreage hub
Points in Polygon Helper sits in the area & acreage cluster, alongside 26 other tools that answer neighbouring questions with different methods or datasets.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
How to Measure Land Area on a Map: Acres, Hectares and Square Feet — Learn how map-based area measurement works, how to trace a parcel more accurately, how acres and hectares relate, and when an online estimate is not enough.