Folders that are maps
Assets and locations as points, lines or areas on OpenStreetMap or HERE. Folders nest: the municipality, the plant and its floor plan.
Choose which cookies you accept. You can change this at any time from “Cookie settings” in the footer of every page. Cookie policy
They make the website work, remember this choice, keep your conversation with the assistant if you use it, and protect the forms from bots. They cannot be turned off.
During your visit we remember the campaign source you arrived with and the page you landed on, so we know which campaigns and pages bring us requests. Cloudflare Web Analytics counts visits without cookies and does not depend on this option.
Used to measure our campaigns on Google Ads, LinkedIn and Meta. None is active on the website today.
Integration · Maps
Streetlights, storm drains, trees, containers or network sections, each in its place on the map, with its history, plans and work orders. The inventory goes in and out in the open formats your GIS technician already uses.
What it solves
A city or an urban services company does not manage equipment in a building: it manages assets spread across a whole municipality. That inventory lives in a GIS or in a GeoJSON file, and the work order lives somewhere else.
With the GIS inventory, each attendo asset has its place on the map, with aerial imagery or the land registry underneath, and the inventory is imported from the GIS and returned to it in its own formats. It is the same asset as always, with its history, plans and documents.
What it does
Asset location folders can be a floor plan or a map. On the map, everything uses open formats.
Assets and locations as points, lines or areas on OpenStreetMap or HERE. Folders nest: the municipality, the plant and its floor plan.
Up to 20 layers per map, such as aerial imagery or the land registry, with their opacity and order.
Up to 5,000 features at a time, also in ETRS89 UTM. Each feature is matched to its asset by code or by name.
The map’s inventory is exported as standard GeoJSON, with the name, type and code of each feature.
Instead of a file, the import reads the layer your GIS publishes.
The inventory is published as read-only OGC API Features, filtered by each person’s portfolio.
The customer portal shows the maps of their organization, read-only and with their assets.
What travels
Whatever is imported goes through a preview first. Nothing is created until you confirm.
| Data | Direction | When |
|---|---|---|
| Features from a GeoJSON file | Directionfrom your GIS to attendo | WhenWhen you confirm the import |
| Features from a WFS or OGC API Features service | Directionfrom your GIS to attendo | WhenOn import |
| WMS and WMTS layers | Directionfrom map service to attendo | WhenWhen the map opens |
| Inventory as GeoJSON | Directionfrom attendo to your GIS | WhenOn export |
| Inventory as OGC API Features | Directionfrom attendo to your GIS | WhenWhen the GIS tool requests it |
Getting started
The asset map, GeoJSON and WMS and WMTS layers need no credentials. Reading a WFS or OGC API Features service and publishing the inventory for QGIS, ArcGIS or GDAL are set up with you.
Status Available
Typical effort. The map and the import are a morning’s work with the file ready. Reading from QGIS or another tool is planned during implementation.
You create the customer’s folder with a map view and frame it by searching for the address.
You add aerial imagery, the land registry or whatever layers you want underneath.
You import the GeoJSON file or the WFS service, review the preview and confirm.
If your GIS technician wants to read the inventory from QGIS, we connect it with you.
Honesty
GeoJSON is the exchange format. A CAD drawing is exported to PDF or an image first.
It does not do buffers, intersections or topological editing of networks.
Publishing is read-only: the inventory is changed in attendo.
It only reads services with a public HTTPS address.
The field app does not show map folders.
Keep going
All integrations Every connection, with its real status.
Frequently asked questions
No. The map comes with OpenStreetMap and the exchange uses open formats. HERE only if you already have it.
Yes. You export the layer to GeoJSON and import it into the folder, up to 5,000 features at a time. If the layer is published as WFS or OGC API Features, it is imported from the service.
Yes, as a WMS or WMTS layer on the map, with its opacity.
Yes, as a read-only OGC API Features layer. It is set up with your GIS technician.
Yes, the folders of their organization, read-only and with their assets.
Request a demo
With a sample GeoJSON file, we will show you your assets on the map, with their history and work orders.
Would you rather talk first?