Rectilinear grid point counts
Count local planar or WGS84 point coordinates in occupied rectangular cells with explicit half-open boundaries.
- 1Add input
- 2Adjust settings
- 3Get your result
Tool input and files are processed in this browser without being uploaded.
Before you start
Use CSV with x,y headers or a Point FeatureCollection. Declare planar units or WGS84 degrees, grid origin and positive steps. Download every occupied cell and count; no online map or CRS inference is used.
How to use this tool
- Supply points and declare coordinate space/units.
- Set origin and positive x/y steps; lower edges are included, upper edges excluded.
- Download all polygon cells and complete count JSON/CSV.
Supported inputs and limits
One30 MiB file or1 MiB pasted text;100,000 points,10,000 occupied cells. CSV has exactly x,y columns; JSON must contain only2D Point geometries and no CRS field.
Coordinates/origin have absolute value≤1e12; steps≥1e−9, indexes≤1e9. Inputs first parse as IEEE754 binary64. Canonical String(number) decimals use exact BigInt grid arithmetic; original overprecision is not preserved. Reject degenerate corners or WGS84 cells extending outside longitude/latitude bounds.
Worked example
Example input
Five points include−0.1,0.3 and0.29999999999999993 with step0.1.
Example options
{"stepX":0.1,"stepY":0.1,"units":"m"}Example output
5 counted points in5 cells;0.3 enters index3, the preceding decimal index2.
When something does not work
Correct malformed coordinates, duplicate JSON keys or headers. Reduce points/cells, choose valid steps or move the origin, then rerun.
Frequently asked questions
Are planar outputs standard WGS84 GeoJSON?
Planar output is a labelled local JSON FeatureCollection in declared input units. Only explicitly selected WGS84 degree grids use a .geojson filename; degrees are not equal-area or km² density.