Calculation Engine Options
Maptaskr Power Maps allows you to choose from several calculation engines to control how geographic area and distance calculations are performed within the map interface.
These engines affect how shapes are evaluated when using measurement tools, drawing shapes, or performing spatial analysis.
Calculation Options Available
| Engine Option | Description | Best For |
|---|---|---|
| Simple (Mercator) | Performs calculations in Web Mercator (EPSG:3857) screen space. Shapes retain the same visual size and form on the map, but areas and distances vary by latitude, becoming increasingly distorted toward the poles. | Fast, lightweight calculations where visual consistency on a flat map is more important than accuracy. |
| GeoJSON.io (WGS84) | Computes measurements using WGS84 latitude and longitude values. Latitudinal and longitudinal distances remain consistent, but shapes become increasingly squished toward the poles due to spherical assumptions. | GeoJSON workflows or when matching results from common open-source GIS tooling. |
| Spherical (WGS84) | Uses spherical Earth calculations (Haversine-based) on WGS84. Area and distance are preserved globally, but shapes appear to shrink visually as they approach the poles when rendered on a flat map. | Accurate geographic measurements, especially for large areas or globe-based views. |
| Custom JavaScript | Allows fully custom spatial logic via JavaScript, including third-party geospatial libraries or bespoke algorithms. | Advanced or highly specialized spatial analysis and precision-critical use cases. |
Select your calculation engine based on your specific needs:
- Use Simple (Mercator) for fast, visual approximations.
- Choose Geojson.io (WGS84) for web-standard GeoJSON compatibility.
- Select Spherical (WGS84) when you need better geographic accuracy.
- Use Custom Javascript for full control over spatial computation logic.
If you're unsure which engine is most appropriate for your scenario, we recommend starting with Spherical (WGS84) for balanced accuracy and performance.
Custom or Third-Party Calculation Logic
The Custom Javascript engine allows advanced users to define their own spatial calculation methods directly within the Maptaskr configuration. This includes both bespoke logic and integration with third-party geospatial libraries.
Examples of what you can implement:
- Geodesic or ellipsoidal area calculations using libraries like Turf.js
- Domain-specific spatial logic for regulatory, environmental, or engineering applications
- Custom measurement algorithms or rule-based logic tailored to your business process
- Integration with external APIs for live spatial computations
This option is ideal for teams that need high precision, regulatory compliance, or specialized analysis workflows beyond the standard engines.