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 basic spatial calculations using the Web Mercator projection. Distances and areas are estimated on the 2D projected plane, introducing distortion at larger scales or high latitudes. | Fast, lightweight calculations — such as general mapping use cases. |
| GeoJSON.io (WGS84) | Uses the GeoJSON method for computing area based on WGS84 spherical geometry. Assumes Earth is a sphere. | Working with GeoJSON-based data or when needing consistency with common open-source GIS tools. |
| Spherical (WGS84) | Applies Haversine formula–based calculations on a WGS84 sphere, offering improved precision over planar methods. Appropriate for larger shapes or long-distance calculations. | More accurate geographic area and distance measurements without requiring complex geodetic libraries. |
| Custom JavaScript | Enables custom implementation of calculation logic using JavaScript. Supports integrating third-party spatial libraries or bespoke algorithms. | Advanced use cases needing specialized spatial analysis or high-precision requirements. |
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.