Maps · head to head
Nominatim vs WhiteboxTools

Nominatim
Maps
Open-source geocoding tool for OpenStreetMap data, providing address search and reverse geocoding capabilities
- 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: Nominatim the public API allows an absolute maximum of 1 request per second; 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: Nominatim 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 Nominatim and WhiteboxTools actually diverge.
| Attribute | Nominatim | WhiteboxTools |
|---|---|---|
| Starting price | On request | Free |
| Pricing model | freemium | 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 Nominatim
- 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.
Nominatim
- Geocoding and reverse geocoding servicesnot WhiteboxTools
- Address lookup and location searchnot WhiteboxTools
- OpenStreetMap-based geolocation datanot 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 Nominatim
- A forestry or environmental team processing airborne LiDAR into canopy height and terrain models without buying a point cloud licence per analystnot Nominatim
- A GIS developer embedding terrain analysis into a commercial product, where the MIT licence avoids the copyleft obligations of GRASS or SAGAnot Nominatim
- A university teaching geomorphometry where every student needs the full toolset on their own laptop at zero costnot Nominatim
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Nominatim
- The public API allows an absolute maximum of 1 request per second
- Bulk geocoding must run in a single thread and cannot be distributed across machines
- Scripts running longer than a day or on a schedule are limited to 4 requests per minute
- Autocomplete search against the public API is explicitly prohibited
- Systematic queries such as grid based reverse lookups and complete data downloads are prohibited
- Reselling geocoding results or acting as an API intermediary is prohibited
- Every request must send a valid HTTP Referer or User-Agent identifying the application, and default library headers are rejected
- Results must be cached client side, and repeated identical queries can lead to blocking
- Attribution to OpenStreetMap under ODbL must be displayed
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
Nominatim
On requestNo published plan breakdown. See the Nominatim review.
WhiteboxTools
Free- WhiteboxTools open coreFree
- MIT licence
- Over 450 geospatial tools
- Python, R and QGIS front ends
Which should you pick?
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 Nominatim or WhiteboxTools better?
- Neither clearly leads. Nominatim 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, Nominatim or WhiteboxTools?
- WhiteboxTools has a free tier; the other does not. Paid plans start at On request for Nominatim and Free for WhiteboxTools.
- Does Nominatim or WhiteboxTools run on more platforms?
- Nominatim 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. Nominatim starts at On request.
- What is Nominatim best used for?
- Nominatim is most often used for geocoding and reverse geocoding services, address lookup and location search, openstreetmap-based geolocation data. Of those, geocoding and reverse geocoding services and address lookup and location search are not what WhiteboxTools is typically brought in for.
- What can Nominatim do that WhiteboxTools cannot?
- Nominatim covers Core Functionality, User Interface. WhiteboxTools covers Hydrological analysis, LiDAR processing, Terrain derivatives, Raster analysis.
Answered from the vendors’ own pages
Nominatim: Is Nominatim free?
Nominatim is open source software built on OpenStreetMap data. It appears to be free to use, though commercial usage may require separate licensing or terms. Check the project repository or contact support for clarity on licensing.
SourceWhiteboxTools: Is WhiteboxTools free for commercial use?
Yes. It is MIT licensed, which permits commercial use and embedding without a copyleft obligation.
Nominatim: What is Nominatim's pricing model?
Nominatim does not publish a standard pricing model on its website. As open source software, it is available for free, but commercial or large-scale deployments may require reviewing their licensing terms or contacting project maintainers.
SourceWhiteboxTools: Is there paid support?
No general commercial support contract is offered. Support is GitHub issues and community forums. Budget internal expertise instead.
WhiteboxTools: Who maintains it?
Professor John Lindsay and the Geomorphometry and Hydrogeomatics Research Group at the University of Guelph, Canada.
WhiteboxTools: 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 WhiteboxTools
Other head to heads
- Nominatim vs Mapbox
- Nominatim vs Google Maps Platform
- Nominatim vs HERE Technologies
- Nominatim vs Apple Maps
- Nominatim vs LocationIQ
- Nominatim vs Geoapify
- Nominatim vs OpenRouteService
- Nominatim vs OSRM
- Nominatim vs PositionStack
- Nominatim vs Stadia Maps
- Nominatim vs GraphHopper
- Nominatim vs Leica Infinity
- Nominatim vs Lonboard
- Nominatim vs Mapillary
- Nominatim vs MapQuest
- Nominatim vs MAPS.ME
- Nominatim vs Google Maps
- Nominatim vs Potree
- Nominatim vs QGIS
- Nominatim vs Esri ArcGIS
- Nominatim vs SAGA GIS
- Nominatim vs GRASS GIS
- Nominatim vs Global Mapper
- Nominatim vs CesiumJS
- Nominatim vs Kepler.gl
- Nominatim vs OpenLayers
- Nominatim vs Leaflet
- Nominatim vs deck.gl
- Nominatim vs Mappedin
- Nominatim vs MapTiler
- Nominatim vs onX Maps
- Nominatim vs SW Maps
- Nominatim vs Agisoft Metashape
- WhiteboxTools vs Mapbox
- WhiteboxTools vs Google Maps Platform
- WhiteboxTools vs HERE Technologies
- WhiteboxTools vs Apple Maps
- WhiteboxTools vs LocationIQ
- WhiteboxTools vs Geoapify
- WhiteboxTools vs OpenRouteService
- WhiteboxTools vs OSRM
- WhiteboxTools vs PositionStack
- WhiteboxTools vs Stadia Maps
- WhiteboxTools vs GraphHopper
- WhiteboxTools vs Leica Infinity
- WhiteboxTools vs Lonboard
- WhiteboxTools vs Mapillary
- WhiteboxTools vs MapQuest
- WhiteboxTools vs MAPS.ME
- WhiteboxTools vs Google Maps
- WhiteboxTools vs Potree
- WhiteboxTools vs QGIS
- WhiteboxTools vs Esri ArcGIS
- WhiteboxTools vs SAGA GIS
- WhiteboxTools vs GRASS GIS
- WhiteboxTools vs Global Mapper
- WhiteboxTools vs CesiumJS
- WhiteboxTools vs Kepler.gl
- WhiteboxTools vs OpenLayers
- WhiteboxTools vs Leaflet
- WhiteboxTools vs deck.gl
- WhiteboxTools vs Mappedin
- WhiteboxTools vs MapTiler
- WhiteboxTools vs onX Maps
- WhiteboxTools vs SW Maps
- WhiteboxTools vs Agisoft Metashape
