Skip to content

Organize the data needed for the dashboards #268

@paco-barreras

Description

@paco-barreras

Some of the data can live in the nomad/data folder , some other data might instead need code that generates it.

Be careful of:

  • No large files (>2Mb) in the repository
  • Projections (mercator, vs lat/long vs garden-city blocks)
  • How does the actual dashboard import data?

What trajectories are needed for our demos?

We have some buttons that say "Different trajectory" or even "Generate trajectory". We might want to pregenerate 10 interesting trajectories and loop through them. That is, the destination_diary object.

Does the dashboard also allow you to tune the "sparsity" of the trajectory?

The animation itself

Are we passing images? a gif? or the input for viz.py methods (trajectory table + cluster labels + parameters).

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions