Data on Haiyz

The four surfaces¶

Everything you bring to Haiyz lands on one of four surfaces — four purposes, not four kinds of storage.

Data Items — /data/items. One piece of data with a version history: a file you uploaded, a layer you pointed at a live service, or a Hyz Layer being edited in place. Every other surface is built out of items. See Data Items.

Data Rooms — /data/rooms. A named bundle of items, pinned at a version, handed over as one thing. See Data Rooms.

Live sources — a layer inside someone else's portal, read where it lives instead of uploaded. A linked item still sits on /data/items with everything else, because what Haiyz pulls is stored as an ordinary version. See Linked and live sources.

Open Data — /data/open-data. The public catalog of open geospatial sources. Nothing in it is yours, and no account is needed to read it. See The Open Data catalog.

Which one do I want¶

What you are doing	Where it belongs
Keeping a file to use across the platform	A data item
Handing a fixed set of files to someone else	A data room
Reading a service someone else keeps current	A live source
Looking for data that is already public	Open Data
Giving a named set of people access to any of these	A group

Groups sit outside the Data section on purpose: one group can be granted a room, a dashboard or a map, so it is a sharing primitive, not a data surface.

The kind chip¶

Every data item wears a chip saying what shape it is. The chip is a filter as well as a label.

Chip	What it means
Layer	The file carries usable geometry, so it draws on a map.
Table	Rows with no geometry Haiyz could read — still queryable and chartable, just not a layer.
Live	A window onto a portal layer. A live row shows its source and sync state in place of a kind chip, because "Live" is the kind.
Editable	A Hyz Layer of the item has editing switched on, so its features change in place. It sits beside the Layer chip, not instead of it. See Editable layers.

Every shape, what it can do and what it cannot, is laid out in Kinds of data; the states an item moves through are in The life of a data item.

How data reaches the products¶

Nothing is re-uploaded to move between products:

• Item → Workspace → Map. Open an item in Hyz Workspace, work on it, then Publish to Hyz Maps. The map holds copies of the layers, so it survives a change to the item.
• Room → Map. A map can be built on one data room: every item becomes a layer pinned at the room's version, and Sync reconciles the map when the room changes.
• Item or map → Dashboard. A dashboard widget binds to an item, a map's layer or a field campaign — and on a live source it can answer from the portal rather than the stored snapshot.
• Open Data → Workspace. Browse Haiyz has an Open Data tab, so a public source becomes a layer without leaving the page.
• Item → Hyz Desktop → item. An editable Hyz Layer is checked out, edited offline and synced back: the same rows, not a copy. See Editing offline in Hyz Desktop.

How many items and rooms you may hold, and how much storage they take, is set by your plan — see Plans and limits.

Good to know¶

• An item is never moved by being used. A map, a room, a dashboard and a project reference it; deleting any of them leaves the item untouched.
• A data room is not a folder. The same item can be in several rooms, and removing it from one takes nothing from the others.
• Only a clean version is served. A version that has not passed the virus scan will not download, open, or become a layer.
• An editable layer changes without an upload. Its live rows are the truth, and a new file version is refused while editing is on. Editable or not says which data can be edited in place.
• Every object can say what depends on it. An item's page lists the maps, rooms, dashboards and workspaces using it, and so does the delete confirmation.