Preset Feature Feedback
What is the problem or goal you're trying to solve or accomplish?
Some customers work with confidential geospatial data, including purchased or proprietary sets of latitude/longitude points or polygon coordinates. These coordinates cannot be redistributed or exposed to dashboard viewers.
However, in Preset today, all map visualizations require raw coordinates to be sent to the frontend, meaning users can see the real coordinates in:
network payloads
API responses
chart JSON metadata
Customers want a way to use maps in Preset without exposing real coordinates to end users.
How are you solving it currently?
There is no built-in mechanism in Preset or Superset to hide or transform coordinates while still enabling map rendering.
Current workarounds include:
Avoiding scatterplot or point-level maps entirely
Aggregating locations manually into H3 / S2 / grid IDs outside of Preset
Simplifying or obfuscating geometries before loading them
Using region-level maps instead of point-level maps
Decrypting coordinates inside SQL (which still exposes raw values in the frontend)
None of these options provide a direct, secure, platform-supported way to render maps without exposing coordinates.
What is your recommended solution?
The customer requests (or is open to) a native Preset feature that would allow:
A way to render map visualizations without exposing the underlying coordinates, such as:
converting coordinates to internal IDs before frontend transmission
server-side “proxy rendering” of geospatial layers
providing a secure transformation service where coordinates are mapped to abstracted points
enabling map charts to use masked, rounded, or hashed coordinates while still rendering accurately
built-in support for privacy-safe geospatial layers (e.g., tile layers, centroid substitution, secure H3 pipelines)
Essentially, the customer wants a method for:
“Use real geospatial data in visualizations, but never send raw coordinates to end users.”
