Maps · head to head
PositionStack vs WhiteboxTools

PositionStack
Maps
Free, developer-friendly geocoding API for forward and reverse geocoding with global coverage
- From
- On request
- Rated
- -

WhiteboxTools
Maps
Open source geospatial analysis engine with several hundred raster, LiDAR and hydrological tools
- From
- Free
- Rated
- -
The short version
- Only WhiteboxTools has a free tier, so it costs nothing to try first.
- Each has a real cost: PositionStack the free plan allows only 100 requests per month; WhiteboxTools there is no vendor and no commercial support contract, so an organisation whose regulatory or client obligations require an answerable supplier cannot use it for that work no matter how good the algorithms are.
- They diverge on capability: PositionStack covers Core Functionality, WhiteboxTools covers Hydrological analysis.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which PositionStack and WhiteboxTools actually diverge.
| Attribute | PositionStack | WhiteboxTools |
|---|---|---|
| Starting price | On request | Free |
| Pricing model | Unknown | Open source, no licence fee |
| Free tier | No | Yes |
| Platforms | Web | Windows, macOS, Linux |
Identical on both: user rating (Not yet rated), category (Maps).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in PositionStack
- Core Functionality
- User Interface
Only in WhiteboxTools
- Hydrological analysis
- LiDAR processing
- Terrain derivatives
- Raster analysis
- Image processing
- Python and R front ends
- QGIS plugin
- MIT licence
What people use each for
The jobs each tool is most often brought in to do.
PositionStack
- Forward geocoding addresses to coordinates via REST APInot WhiteboxTools
- Reverse geocoding coordinates to addressesnot WhiteboxTools
- Batch geocoding location data in a backend servicenot WhiteboxTools
WhiteboxTools
- A hydrologist who needs depression breaching rather than filling on a large DEM, because filling destroys the drainage structure the model depends onnot PositionStack
- A forestry or environmental team processing airborne LiDAR into canopy height and terrain models without buying a point cloud licence per analystnot PositionStack
- A GIS developer embedding terrain analysis into a commercial product, where the MIT licence avoids the copyleft obligations of GRASS or SAGAnot PositionStack
- A university teaching geomorphometry where every student needs the full toolset on their own laptop at zero costnot PositionStack
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
PositionStack
- The free plan allows only 100 requests per month
- The free plan is a personal licence, so commercial use requires a paid plan
- The free plan is rate limited, with an extended rate limit only from the Basic plan up
- Requests beyond the monthly quota are billed as overage, at $0.0003996 per request on Basic
- The lowest advertised rates require annual prepayment
- Enterprise volumes are priced by quote with no published rate
WhiteboxTools
- There is no vendor and no commercial support contract, so an organisation whose regulatory or client obligations require an answerable supplier cannot use it for that work no matter how good the algorithms are.
- Maintenance depends on a single academic research group and effectively on one professor, which is a real continuity risk for anything embedded in a production pipeline for a decade.
- It is command line first; the QGIS plugin and Python bindings help, but analysts who expect a graphical workflow with previews and undo find it unforgiving.
- Documentation is a reference manual rather than a set of worked workflows, so knowing which of 450 tools to chain for a given problem requires domain knowledge the software does not supply.
- Naming and behaviour overlap confusingly with the older Whitebox GAT, a separate GPL-licensed desktop GIS from the same group, and adopters regularly install or cite the wrong one.
Pricing, plan by plan
PositionStack
On requestNo published plan breakdown. See the PositionStack review.
WhiteboxTools
Free- WhiteboxTools open coreFree
- MIT licence
- Over 450 geospatial tools
- Python, R and QGIS front ends
Which should you pick?
Choose PositionStack if
- You need core functionality.
- You also want user interface.
Choose WhiteboxTools if
- You need hydrological analysis.
- You want to start without paying.
- You work on Windows, macOS, Linux.
- You also want lidar processing.
Questions people ask
- Is PositionStack or WhiteboxTools better?
- Neither clearly leads. PositionStack starts at On request and WhiteboxTools at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, PositionStack or WhiteboxTools?
- WhiteboxTools has a free tier; the other does not. Paid plans start at On request for PositionStack and Free for WhiteboxTools.
- Does PositionStack or WhiteboxTools run on more platforms?
- PositionStack runs on Web. WhiteboxTools runs on Windows, macOS, Linux.
- Can I use WhiteboxTools for free?
- Yes. WhiteboxTools has a free tier, so you can try it without paying. PositionStack starts at On request.
- What is PositionStack best used for?
- PositionStack is most often used for forward geocoding addresses to coordinates via rest api, reverse geocoding coordinates to addresses, batch geocoding location data in a backend service. Of those, forward geocoding addresses to coordinates via rest api and reverse geocoding coordinates to addresses are not what WhiteboxTools is typically brought in for.
- What can PositionStack do that WhiteboxTools cannot?
- PositionStack covers Core Functionality, User Interface. WhiteboxTools covers Hydrological analysis, LiDAR processing, Terrain derivatives, Raster analysis.
Answered from the vendors’ own pages
PositionStack: What annual billing discount does Positionstack offer?
Annual billing provides up to 15% discount compared to monthly billing total. For example, Basic annual is $8.99/month vs $9.99/month monthly, and Professional annual is $43.99/month vs $49.99/month monthly. Source: https://positionstack.com/pricing
SourceWhiteboxTools: Is WhiteboxTools free for commercial use?
Yes. It is MIT licensed, which permits commercial use and embedding without a copyleft obligation.
PositionStack: How do Positionstack overage notifications work?
Positionstack sends alerts at 75%, 90%, and 100% of your monthly request allowance. Overages are calculated at month-end and charged according to each tier's per-request rate (e.g., Business tier: $0.00013332/request). Source: https://positionstack.com/pricing
SourceWhiteboxTools: Is there paid support?
No general commercial support contract is offered. Support is GitHub issues and community forums. Budget internal expertise instead.
PositionStack: What payment methods does Positionstack accept?
Positionstack accepts Visa, MasterCard, Discover, American Express, Diner's Club for monthly billing. Enterprise customers may arrange bank transfers for their custom agreements. Source: https://positionstack.com/pricing
SourceWhiteboxTools: Who maintains it?
Professor John Lindsay and the Geomorphometry and Hydrogeomatics Research Group at the University of Guelph, Canada.
PositionStack: Can I downgrade or cancel my Positionstack plan?
Downgrades take effect at your billing cycle end. Cancellations require contacting customer service. Uptime guarantee is 99.9% average over 12 months. Source: https://positionstack.com/pricing
SourceWhiteboxTools: How is it different from Whitebox GAT?
Whitebox GAT is an older GPL-licensed desktop GIS from the same group. WhiteboxTools is the newer Rust command line engine with a permissive licence. They are not the same product.
WhiteboxTools: Can I use it from QGIS?
Yes, through a plugin, and also from Python and R.
Related pages
More on PositionStack
More on WhiteboxTools
Other head to heads
- PositionStack vs Mapbox
- PositionStack vs Google Maps Platform
- PositionStack vs HERE Technologies
- PositionStack vs Apple Maps
- PositionStack vs LocationIQ
- PositionStack vs Nominatim
- PositionStack vs Stadia Maps
- PositionStack vs Leaflet
- PositionStack vs CesiumJS
- PositionStack vs Global Mapper
- PositionStack vs Ride with GPS
- PositionStack vs Gaia GPS
- PositionStack vs Agisoft Metashape
- PositionStack vs Atlas.co
- PositionStack vs Correlator3D
- PositionStack vs Emlid Studio
- PositionStack vs ArcGIS Field Maps
- PositionStack vs Geographic Calculator
- PositionStack vs Potree
- PositionStack vs QGIS
- PositionStack vs Esri ArcGIS
- PositionStack vs SAGA GIS
- PositionStack vs GRASS GIS
- PositionStack vs Lonboard
- PositionStack vs Kepler.gl
- PositionStack vs OpenLayers
- PositionStack vs deck.gl
- PositionStack vs Mappedin
- PositionStack vs MapTiler
- PositionStack vs onX Maps
- PositionStack vs SW Maps
- WhiteboxTools vs Mapbox
- WhiteboxTools vs Google Maps Platform
- WhiteboxTools vs HERE Technologies
- WhiteboxTools vs Apple Maps
- WhiteboxTools vs LocationIQ
- WhiteboxTools vs Nominatim
- WhiteboxTools vs Stadia Maps
- WhiteboxTools vs Leaflet
- WhiteboxTools vs CesiumJS
- WhiteboxTools vs Global Mapper
- WhiteboxTools vs Ride with GPS
- WhiteboxTools vs Gaia GPS
- WhiteboxTools vs Agisoft Metashape
- WhiteboxTools vs Atlas.co
- WhiteboxTools vs Correlator3D
- WhiteboxTools vs Emlid Studio
- WhiteboxTools vs ArcGIS Field Maps
- WhiteboxTools vs Geographic Calculator
- WhiteboxTools vs Potree
- WhiteboxTools vs QGIS
- WhiteboxTools vs Esri ArcGIS
- WhiteboxTools vs SAGA GIS
- WhiteboxTools vs GRASS GIS
- WhiteboxTools vs Lonboard
- WhiteboxTools vs Kepler.gl
- WhiteboxTools vs OpenLayers
- WhiteboxTools vs deck.gl
- WhiteboxTools vs Mappedin
- WhiteboxTools vs MapTiler
- WhiteboxTools vs onX Maps
- WhiteboxTools vs SW Maps
