Advanced Filtering¶

This guide details the configuration for Spatial and Attribute filtering within Data Access Rules.

Spatial Filtering¶

Spatial filtering restricts access to a defined geometric area. It is configured via the ruleLimits object in a rule definition.

Configuration Schema¶

Filter Types¶

• INTERSECT (Default): Returns complete features if they spatially interact with the allowedArea.
  • Performance: Fast. Uses database spatial indexes.
  • Use Case: Standard row-level security.
• CLIP: Geometrically crops features to the allowedArea.
  • Performance: Slower. Requires CPU-intensive geometry intersection calculations per feature.
  • Use Case: Strict security where users must not see geometry outside the boundary.

JSON Example¶

{
  "access": "LIMIT",
  "ruleLimits": {
    "allowedArea": "POLYGON((-105 40, -104 40, -104 41, -105 41, -105 40))",
    "spatialFilterType": "CLIP"
  }
}

Attribute Filtering¶

Attribute filtering hides specific columns from the output. It is configured via the layerDetails object.

Configuration Schema¶

Note: Use either includedAttributes OR excludedAttributes, not both.

JSON Example (Exclude Mode)¶

{
  "access": "LIMIT",
  "layerDetails": {
    "attributes": {
      "accessType": "READONLY",
      "excludedAttributes": ["social_security_number", "salary"]
    }
  }
}

Additional Constraints¶

Coordinate Reference System (CRS)¶

Restricts the output CRS users can request (e.g., to prevent reprojection load).

{
  "access": "LIMIT",
  "ruleLimits": {
    "allowedCRS": ["EPSG:4326", "EPSG:3857"]
  }
}

Catalog Mode¶

Controls how restricted layers appear in the capabilities document.

{
  "access": "LIMIT",
  "layerDetails": {
    "catalogMode": "HIDE"
  }
}