From an empty account to a published map and a dashboard built on it, in about ten minutes.
Haiyz is one platform for spatial work: bring data in, work on it, publish it as a map, put a dashboard on top. This page walks that loop once, end to end.
Follow the six steps in order — each leaves behind what the next one uses.
/auth/login, and Haiyz emails you a one-time code — there is no password to
set, to remember, or to leak. Once you are in, join the community from your
account. Reading published content needs no membership; creating your own data
does./data/items and choose New. The page asks one
question first: are you uploading a file, or linking a live layer on a portal?
Take the upload door for now. Give the item a title and a web address, choose
who may see it, and save. What you get back is a data item with one
version inside it — every later upload adds another version rather than
overwriting this one./workspace. Under the
Data tab, browse Haiyz and add the item you just created; it draws on the
map as a layer. Now switch to Tools. The quickest first result is in the
Analysis panel: pick a target feature on the map, choose Buffer, give it a
distance in metres, and run it. Every tool result comes back as a new layer,
which is what lets you feed one tool into the next./maps. Every layer has a style editor —
colour, size, opacity, labels, popups, point icons, clustering, animated flow
lines. Or open Hyz AI symbology, describe the look you are after, and
review the proposed changes before you apply them. By default the assistant is
sent the schema only — field names and types. A switch adds three real rows,
identifier-like columns masked, which helps it get units and codes right./dashboards, choose New, then Hyz
AI. Pick your sources — data items, the map you just published, a field
campaign — describe the dashboard you need, and it drafts the pages, widgets
and bindings. You land in the builder with a draft; nothing is live until you
save it.A data item does not have to be GIS data. Anything Haiyz does not recognise as spatial is simply stored as it is, and skips geometry validation.
| Family | What it covers |
|---|---|
| Vector files | GeoJSON, a zipped Shapefile, GeoPackage, KML and KMZ |
| Tabular | CSV — with coordinate columns it is read as points |
| Raster | GeoTIFF |
| Everything else | Documents, archives, web assets — stored as uploaded |
Map layers are always GeoJSON at rest. When you publish, vector formats are converted for you and a CSV with coordinates becomes points; a raster cannot become a map layer, and the save says so rather than storing something the viewer cannot draw.
Every step above exists on every plan, but not at the same scale. How many data items, maps, dashboards, groups, data rooms, projects and workspaces you may keep — and how much storage you hold — is set per plan, and publishing to Hyz Maps in particular is a paid step rather than a free one. Tool runs are metered on their own separate allowance.
The model, and what happens when you reach a wall, is on Plans & limits. What each plan costs and includes is on Pricing.
/data/items, with its own versions and its own sharing.