Skip to content

OpenGrid and Plenario misalignment #313

@tomschenkjr

Description

@tomschenkjr

While an attempt is made to align the functionality with the MongoDB service layer and Plenario, at times, some of the features created for OpenGrid are only compatible with MongoDB service layer. Often, that misalignment comes from inability to store local parameters on Plenario since it's a read-only system.

This outlines the features that do not fully function as intended on OpenGrid.io. Some of this may be because of architectural mismatch that is not compatible with Plenario. Some items may require a way to configure data on a dataset-by-dataset basis with configuration files.

Find Data

  • Bubble plots cannot be configured on a dataset-by-dataset basis. Right now, no variables are configured for bubbles on OpenGrid.io.

Graphing

  • While creating charts, OpenGrid.io cannot be configured for groupings on a dataset-by-dataset basis. Currently, OpenGrid.io uses ZIP code as the only grouping parameter.
  • While creating line and bar charts, OpenGrid.io cannot be configured to use dates configured on a dataset-by-dataset basis. In WindyGrid, the "date" variable is always the same and defined in the metadata. This is not true for Plenario, so OpenGrid.io does not know which date to graph.

Layers

  • The ability to add layers is very limited in OpenGrid.io. Right now, only weather data (from OpenWeatherMaps.org) is available as layers. OpenGrid's Layer feature does not integrate with Plenario's shape data API and cannot pull-in layers.

Lack of Autocomplete

  • Right now, it's not possible for drop-down values to be auto-populated in OpenGrid (see Advanced Search>Adding Rules #185), which causes users to guess which filter values are valid.

Pop-up Bubbles

  • Some of the pop-up windows are too long and run off the string.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions