Limits and what's not built yet
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Import size | 10 MB in total |
| Nodes on the Edit canvas | 200 placed nodes per map. Unplaced nodes don’t count. Visualise mode shows any number. |
| Nodes per page in the Nodes card’s lists | 200 |
| Rows per page in Table mode | 100 |
| Distinct values in a “one per value” import column | 24 for CSV, 12 for GraphML. More than that, and the column is kept as a property. |
| Distinct connection colours | 8, then they repeat |
| Entries in a colour legend | 8, then “+ N more” |
| Length of a map’s recipe | 20,000 characters |
| Invitation lifetime | 7 days |
| Deleted organisations | Data is permanently deleted after 30 days |
All data is stored in the EU.
Not built yet
Section titled “Not built yet”- Undo, redo and revision history. Edits save as you go and can’t be undone.
- Sharing maps outside your organisation, and public maps.
- Several people editing the same map at the same time with live updates.
- Creating or renaming an organisation in the app. Ask whoever runs your deployment.
- Setting a measure’s category in the app. Categories come from imports and the API.
- Importing a file of connections on its own, without its file of nodes.
- Exporting connections as CSV. CSV export is nodes only; use GraphML.
- Setting or resetting a password. Use an emailed sign-in link.
- Adding or deleting rows, or filtering, in Table mode.
- Setting up a reveal’s steps, or a mode’s forces, with designed controls. For now they’re set in the raw view parameters panel (Shift + Alt + P in Visualise) or through the API.
- API keys in the app. A public API exists for scripts (see Public API), but an admin has to create keys for you.