Put an asset register
on the map.
Prepare tabular records, check coordinates and inspect a spatial result before making it available to a team.
Follow the sampleSpatial data workflows
Bring your data
together.
Put it to work.
Connect files, business records and spatial data. Prepare, validate and publish useful results through visual workflows, with a lightweight spatial engine underneath.
A five-step sample tour. No account required.
FIELD NOTES / 001Illustrative asset workflow
Six records. One useful layer.Asset register → location check → map
06source records
05valid locations
01needs review
From source to useful result.
- Connect
- Prepare
- Validate
- Publish
- Repeat
Built around the work
A clearer path
through messy data.
Start with a job to do. Bring the records into focus, make the preparation visible, and inspect what comes out.
Put an asset register
Understand records
in their place.
Explore geometry alongside attributes. Use declared time and elevation where your layer needs them.
See data inspectionGive applications
a spatial foundation.
Work with SQL and spatial interfaces on a SQLite-based engine. Use the browser to inspect the data behind your application.
Explore the engineAn open look at the process
Every step has
something to show.
Follow six illustrative asset records from a file to a reviewed result. One missing coordinate shows why validation belongs in the flow.
Interactive walkthrough · sample content · no job is executed
01 / Know your source
Start with the records
you already have.
This example starts with a CSV asset register: an ID, a name and two coordinate fields. Look at the sample before deciding how to use it.
Download the six-row sampleFictional assets near Melbourne. All six rows are shown.
asset-register.csv6 rows / 4 fields
| Asset | Name | Longitude | Latitude |
|---|---|---|---|
| A-01 | North pump | 144.961 | -37.810 |
| A-02 | Garden valve | 144.968 | -37.808 |
| A-03 | East sensor | 144.974 | -37.813 |
| A-04 | River gauge | 144.969 | -37.820 |
| A-05 | West meter | 144.961 | -37.817 |
| A-06 | Depot pump | 144.965 | Missing |
Source sample · original values retained
02 / Make meaning explicit
Turn coordinates
into useful locations.
Keep the asset ID and name. Interpret longitude as X and latitude as Y, using WGS 84 coordinates. A missing value remains an issue to review.
These are the example’s preparation settings.
Create map pointsSample configuration
- Keep fields
- Asset ID, name
- X / longitude
- longitude → decimal
- Y / latitude
- latitude → decimal
- Coordinate system
- WGS 84 / EPSG:4326
- Missing coordinates
- Separate for review
Coordinates need the right meaning, not just the right type.
03 / Inspect the exceptions
Five locations ready.
One record to resolve.
A-06 has no latitude. It cannot become a valid point. In this example, the reviewed result includes five records and keeps the exception visible.
Reviewing an issue does not repair the source.
Quality reviewAll 6 sample rows
5valid coordinates
1missing latitude
RECORD A-06
Depot pump needs a latitude.
Correct it in the source or exclude this record from the spatial result. It is not silently placed at zero.
Expected sample output: 5 points + 1 exception
04 / Review before making changes
A preview is a decision.
Publishing is an action.
Check the destination, included records and access before writing a result. In the workspace, publishing a supported workflow result creates a table.
Nothing in this tour is saved or published to a database.
Publication reviewIllustrative checklist
- Proposed table
- reviewed_assets
- Included
- A-01 through A-05
- Excluded
- A-06 · missing latitude
- Source
- Unchanged
- Access
- Review in your workspace
Saving a table and enabling public access are separate decisions.
05 / Keep the preparation
Keep a recipe
for the next dataset.
Use the workspace to build a workflow and inspect its results. Check the save and run options available in the builder you are using.
Open workflowsFrom tour to workspaceWhat to expect
- Sign in and choose your database.
- Import your source or choose an existing table.
- Configure the steps and inspect a bounded preview.
- Review the destination before publishing a supported result.
The guided workflow supports portable workflow files. Unattended scheduling depends on the runtime; this tour does not demonstrate it.
Step 1 of 5 · Connect
Inside the product
Look closely.
Then move forward.
Inspect records, schema and spatial data. Keep sample limits visible so the preview tells you what it actually represents.
Know which way the data flows
Bring data in.
Make results useful.
Importing a file, reading a workflow source and connecting a GIS client are different jobs. Start with the path your data needs.
IN / TABULAR DATA
Files and existing tables
- CSV & ExcelImport to a database table, then select it in a workflow.
- Native tablesRead records from your selected Lyhnidos database.
IN / SPATIAL DATA
Geometry with context
- GeoJSONImport spatial features through map Studio.
- Coordinate fieldsCreate points from tabular longitude and latitude values.
OUT / CLIENTS & APPLICATIONS
Your data in other tools
- OGC API Features & ArcGISUse spatial service URLs with the access your database allows.
- HTTP API & SQLBuild applications and query your records programmatically.
Connect an application
Capabilities vary by source, workflow step and deployment. The tour demonstrates one preparation pattern; it does not imply complete FME format or transformer compatibility.
Lightweight foundation. Spatial depth.
Less infrastructure
between you
and your data.
A SQLite-based spatial engine brings geometry and records together. Start in the browser, then use SQL and spatial interfaces when your application needs them.
Open SQL workspaceAsk spatial questions in SQL.
Work with geometry and ordinary attributes in the same database. Inspect schema and layer metadata alongside your data.
Declare what a layer means.
Use declared elevation models and time fields for layers that need them. Capabilities depend on the geometry and interface you use.
Know the limits of each run.
A sample preview is not a full dataset run. Check source size, processing support and plan limits before moving a large workload.
Review plans and limitsThe workspace around your data
Know what changed.
Choose who gets access.
Bring preparation and inspection into the same platform as database management. Review the scope of an action before you commit it.
Keep source and result distinct.
Inspect previews and publication destinations. Creating a result table is a deliberate step.
Manage access deliberately.
Use account sign-in, workspace roles and scoped API keys. Review database publication before enabling public access.
Understand the plan.
Compare database, storage and query allowances. Check the current pricing page for the limits that apply.
Compare plansStart with a useful result