Most municipalities already have their assets written down somewhere — a spreadsheet, a GIS layer, an old asset system. Nobody should retype that by hand. Send us what you have and we move it into mapzaa for you, and you check the result before anything is final.
If it can be exported, it can be moved. These are the formats we see most; if yours is not among them, send it anyway.
The most common starting point, and a perfectly good one. One row per asset is all it takes; the columns become categories, statuses and fields.
An export from ArcGIS, QGIS or any other GIS, as Shapefile, GeoPackage, GeoJSON or KML. The attribute table becomes your fields and the geometry becomes the pin.
Almost every system can export a list of what it holds, even when it hides the button well. Send us that export — or tell us which system it is, and we will help you get one out of it.
Three steps, and the second repeats until you are satisfied. Your current system keeps running the whole time.
Email an export, or just a sample of one to start with. Tell us which columns matter and which are left over from a system nobody has used in years.
We map your data onto categories and fields and load it for you to look at, on the map and in the table. Tell us what is wrong and we load it again, until it is right.
When you are happy, the final import goes in — from a fresh export if the old system was still in use. From then on mapzaa is the register, and the old one can be retired when you are ready.
A move is also a good moment to decide what the register should hold. A few things change on the way in.
mapzaa records where a thing stands. A line — a stretch of fence, a cycle path — or an area such as a park becomes one point, usually at its middle, or stays behind if it does not belong in an asset register. We ask before we decide.
Every asset gets a mapzaa code of its own, but the ID it had before can be kept in a field beside it. The search box matches on field values, so an old work order or a sticker on a post still finds the asset.
Columns you have not made up your mind about can come along anyway, kept on each asset as a one-off field. Nothing is dropped because it did not fit on the first day; turn it into a proper field later, once you know you want it.
Each asset can hold its own photos, up to twelve. Drawings and other documents are not stored in mapzaa: if your records point to them, the link can be kept in a field, so the file is still one click away.
The whole register exports as CSV at any time, straight from the assets table. We would rather keep you because the register works than because it is hard to take out.
An export, a sample, or just a description of where your assets are recorded today. We will tell you what moving it takes before anything is moved.
Email [email protected] — we usually reply the same day. Or read how the register works in the documentation first.
Your message wasn't sent: your browser didn't say which page the form came from. Reload the page and try again, or write to [email protected].
Your message wasn't sent: too many messages have come from here in a short time. Try again in an hour, or write to [email protected].
Your message wasn't sent: that email address doesn't look right. Check it and send it again.
Your message wasn't sent. Fill in your name and email address — and, for a question, the message itself — then send it again.
Your message wasn't sent: it can hold at most two links. Remove some and send it again.
Your message couldn't be delivered just now. Try again in a minute, or write to [email protected].
Sending…