Skip to content

Built Controls For Dynamic Point Size #368

Description

@lhawkman27

Summary/Description

We need to build out controls for the the dynamic point size scaling This will replace the pointSize block in our current JSON Blob control. Note: Dynamic Point Size can either be a single value (for global pointSize) or a config block {}

  • Value column selector.
  • min/max size.
  • lower/upper bounds.
Either be this:

"pointSize": 8

or this:

"pointSize": {
    "valueColumn": "incident_size",
    "startSize": 4,
    "endSize": 30,
    "lowerBound": null,
    "upperBound": null
  }

valueColumn: column dropdown selection
startSize control: number text entry or dropdown with a limit of 30
endSize control number text entry or dropdown with a limit of 30
lowerBound control: number text entry
upperBound control: number text entry

Motivation/Context

The JSON blob has been useful as a fast prototyping surface, but it is now carrying too much product behavior: category coloring, metric coloring, point sizing, legends, text overlay, styling, defaults, maybe more. That makes it hard for users, hard to validate, and easy for MVT/non-MVT behavior to drift.

Acceptance

  • Point layers and MVT point sublayers can consume the same size config.
  • Update docs

Wiki Page:
https://github.com/raft-tech/GeoSet/wiki/GeoSet-Map-Layer#geojson-config

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreCatchall for tasks that are more like chores than real workenhancementNew feature or request

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions