Transparency alternatives to Geographic Calculator Cloud
Other GIS and mapping vendors we measure, sorted by how much we found at them and not at Geographic Calculator Cloud. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from Geographic Calculator Cloud on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Geographic Calculator Cloud has 12 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Geographic Calculator Cloud” is the one that closes them.
| Vendor | Score | Found there, not found at Geographic Calculator Cloud | Found at Geographic Calculator Cloud, not found there | |
|---|---|---|---|---|
| Mapboxmapbox.comSee also Transparency alternatives to Mapbox | 61/100 | 8 Subprocessor list, Status page with history, Public pricing, +5 | nothing | Compare |
| GIS Cloudgiscloud.comSee also Transparency alternatives to GIS Cloud | 55/100 | 6 Subprocessor list, Data location stated, Public pricing, +3 | nothing | Compare |
| Safe Software FMEsafe.comSee also Transparency alternatives to Safe Software FME | 52/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | nothing | Compare |
| Bentley Systemsbentley.comSee also Transparency alternatives to Bentley Systems | 43/100 | 6 Data processing agreement, Status page with history, Uptime SLA with a figure, +3 | nothing | Compare |
| Planetplanet.comSee also Transparency alternatives to Planet | 39/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Pointlypointly.aiSee also Transparency alternatives to Pointly | 39/100 | 5 Data location stated, Public pricing, HTTPS enforced with HSTS, +2 | nothing | Compare |
| LightBoxlightboxre.comSee also Transparency alternatives to LightBox | 48/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | nothing | Compare |
| MetaLocatormetalocator.comSee also Transparency alternatives to MetaLocator | 38/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | nothing | Compare |
| UP42up42.comSee also Transparency alternatives to UP42 | 38/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | nothing | Compare |
| CARTOcarto.comSee also Transparency alternatives to CARTO | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| eSpatialespatial.comSee also Transparency alternatives to eSpatial | 35/100 | 4 Data location stated, Public pricing, Certifications named, +1 | nothing | Compare |
| Skyfiskyfi.comSee also Transparency alternatives to Skyfi | 35/100 | 4 Data location stated, Public pricing, Certifications named, +1 | nothing | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.