# GIS for Municipalities: How to Build a City Information System and Which Layer to Start With

> How to set up GIS for municipalities: start with the water network, keep the map current from the field and link it to billing. A 7-step plan and pitfalls.

Source: https://digitalbridge.com.tr/en/blog/gis-for-municipalities.html
Publisher: Digital Bridge Teknoloji (https://digitalbridge.com.tr)
Topic: Data & Analytics
Published: 2026-09-30 · Updated: 2026-10-22

GIS for municipalities ([geographic information system](https://digitalbridge.com.tr/en/glossary.html#gis), also called a city information system) is the software that keeps a council's pipes, valves, roads, streetlights, parcels and customer connections on one map with their attributes. It answers questions such as "which households lose water if we close this valve?" in minutes, moving fault, leakage and planning decisions from guesswork to measurement.

## Key takeaways

- Municipal GIS brings pipe, valve, road, streetlight, parcel and customer data onto one map, giving every department the same record.
- The safest start is the single layer where decisions rely most on guesswork; in most municipalities that is the water network.
- According to Türkiye's Ministry of Agriculture and Forestry, average network water loss was 31.6% in 2024; the 2028 limit for metropolitan councils is 25%.
- The map stays current only if field crews record changes on site with a GPS-enabled mobile app that also works offline.
- Linked to billing, automatic meter reading and document systems, GIS makes the same customer and parcel one record everywhere.

## Where does municipal map data sit today?

In most municipalities, spatial data is not in one place. Planning holds CAD drawings, the water department has a network design a contractor drew years ago, roads are tracked in a spreadsheet and the parks team keeps its tree inventory in a folder.

When a main bursts, the crew often relies on a technician's memory of where the pipe runs. When that technician retires, the knowledge leaves the council with them.

The root cause of this fragmentation is usually procurement. The mapping application comes from one vendor, the billing system from another and the document system from a third, each bought in a separate tender in a different year. The same parcel, customer and street end up with a different record in every system, and data moves between departments as email attachments. That is why many councils that say "we have a GIS" actually have a map archive that was loaded once and never updated.

## What does an out-of-date map cost a council? The water loss example

The clearest return on municipal GIS shows up in the water network, because losses are measurable and, in Türkiye, tied to a legal target.

> According to the [Ministry of Agriculture and Forestry's Water Efficiency portal](https://www.suverimliligi.gov.tr/home/KentselSuVerimliligi), the average water loss rate in Türkiye's drinking water networks fell from 39% in 2015 to 31.6% in 2024. Metropolitan and provincial municipalities must bring it down to at most 25% by 2028.

The water loss target comes from Türkiye's 2014 Regulation on the Control of Water Losses in Drinking Water Supply and Distribution Systems. Under the [ministry's announcement on the implementation timetable](https://www.tarimorman.gov.tr/Duyuru/1461/Icme-Suyu-Sistemlerinde-Su-Kayiplarinin-Azaltilmasina-Yonelik-Is-Termin-Plani-Genelgesi-Yururluge-Girmistir), other municipalities must reach 30% by 2028 and 25% by 2033. The ministry also notes that developed countries run at 8–24% and that the real goal should be around 10%; the measures it recommends include district metered areas (DMAs) with pressure management, [remote monitoring](https://digitalbridge.com.tr/en/blog/remote-monitoring-iot-platform.html) and minimum night flow analysis.

None of the ministry's recommended measures can be set up without a map of the network. To define a DMA you need to know which valves to close, which customers fall in which zone and which main feeds each meter. We cover which attributes and field workflow the water layer needs in [the water network GIS inventory guide](https://digitalbridge.com.tr/en/blog/gis-for-water-utilities.html).

The global picture is similar: a [2018 World Bank assessment](https://blogs.worldbank.org/en/ppps/what-do-private-companies-look-performance-based-non-revenue-water-project) puts [non-revenue water](https://digitalbridge.com.tr/en/glossary.html#non-revenue-water), meaning water produced but never billed, at 126 billion cubic metres a year, worth nearly $40 billion in annual losses. Hunting for leaks on an out-of-date network map, digging in the wrong spot and issuing estimated bills are the local version of that cost.

## How do you set up GIS for municipalities? A step-by-step plan

The seven-step sequence below is the opposite of projects that begin with "let's map the whole municipality" and end with a system no department uses. It starts small, gets used in the field, then grows.

1. **Start with one pain point.** Water network, street lighting or green space inventory: whichever area relies most on guesswork becomes the first layer. Write the goal so it can be measured, such as "find the valve to close within five minutes of a burst".
2. **Collect what you already have.** CAD drawings, base maps, zoning plans and spreadsheets are imported, and different coordinate systems (such as ED50 and ITRF96) are converted to one. Missing or contradictory records are flagged in a "to verify" layer rather than thrown away. In rural districts, a [satellite imagery layer for farmland](https://digitalbridge.com.tr/en/blog/satellite-imagery-agriculture-monitoring.html) can be added to the base map as well.
3. **Define the asset model and attributes.** A pipe needs diameter, material, installation year, connected valves and maintenance history; a streetlight needs fixture type, wattage and feeder panel. Without a clear model, every team adds its own fields and the data fragments again.
4. **Set up field updates.** A map only stays current if the crew fixing a fault records the change on site. The [field crew's mobile app](https://digitalbridge.com.tr/en/blog/field-service-management-guide.html) needs GPS capture, photos and offline working, with data syncing once a connection is available. The crews' daily rounds can then be planned on the same map with [route optimisation](https://digitalbridge.com.tr/en/blog/route-optimisation.html).
5. **Connect other systems.** Customer numbers must match the billing system, meter readings must come from [automatic meter reading (AMR)](https://digitalbridge.com.tr/en/blog/automatic-meter-reading-guide.html), and fault records from the call centre or document system. GIS becomes far more valuable through these links. Where faults, consumption and billing need reporting together by zone, GIS layers are loaded by asset or zone code into a [data warehouse](https://digitalbridge.com.tr/en/blog/data-warehouse-etl-guide.html).
6. **Grant access by department.** Contractors and other departments see only the layers opened to them, and every change is logged.
7. **Measure, then expand.** Move to the second layer once the first one hits its response-time and loss targets.

### Which layer should municipal GIS start with?

| First layer | Problem it solves | System to connect | First metric |
|---|---|---|---|
| Water network (pipes, valves, hydrants) | Burst response, DMAs, leakage | Meter reading, billing | Valve-finding time, loss by zone |
| Street lighting and electrical | Faulty poles, maintenance planning | Call centre, fault forms | Time to close a fault |
| Roads and pavements | Excavation permits, clashing works | Permit and document system | Number of clashing excavations |
| Green space and trees | Pruning, irrigation, maintenance contracts | Contractor tracking | Adherence to maintenance plan |

## What are the most common mistakes in city information system projects?

**Treating the map as a one-off job.** If the inventory is drawn by a contractor and handed over with no field update process, the city information system stops being trusted within a couple of years. Part of the budget has to go to the mobile update workflow.

**Locking into desktop licences.** A desktop GIS used on a few specialists' computers is a system that field crews and other departments cannot touch. A web-based, mobile-ready setup turns GIS from a specialist tool into something the whole council uses.

**Storing lines instead of attributes.** Knowing where a pipe runs is not enough; its age and material decide which mains get replaced first.

**Overlooking personal data.** Once customer names and addresses are linked to the map, you are processing personal data under KVKK, Türkiye's Personal Data Protection Law (broadly comparable to the GDPR); our [KVKK compliance steps](https://digitalbridge.com.tr/en/blog/kvkk-compliance-steps.html) article sets out the obligations. Who can see which layer and how long records are kept should be defined from day one.

**Leaving standards for later.** Municipal data will sooner or later be shared with other bodies; in Türkiye, the Ministry of Environment, Urbanisation and Climate Change's national geographic information system (TUCBS) work and the spatial address register (MAKS) are two examples. If layer names, coordinate system and attribute structure use open formats from the start (GeoJSON, Shapefile, WMS/WFS services), sharing does not become a new conversion project. For contractors, too, unless the [technical specification](https://digitalbridge.com.tr/en/blog/writing-technical-specifications.html) states the layer structure and coordinate system for deliverables, every contractor delivers differently and the clean-up falls to the council.

**Not measuring success.** "GIS is installed" is not an outcome. A few [well-chosen KPIs](https://digitalbridge.com.tr/en/blog/how-to-set-kpis.html), such as fault response time, field-verified record rate and the number of users who open the map at least once a week, show whether the system is actually used. Tracked by neighbourhood and district on a map-based [management dashboard](https://digitalbridge.com.tr/en/blog/bi-dashboard-kpis.html), those figures also become the strongest case for expansion in the next budget round.

## Which data sources and applications work alongside municipal GIS?

Municipal GIS is not a standalone map; it is the shared base where imagery, meter and network data meet. Our [drone NDVI analysis guide](https://digitalbridge.com.tr/en/blog/drone-ndvi-analysis.html) explains how drone imagery and orthophotos are added to a GIS as base layers and what outputs they can produce. For methods of measuring network losses, see our article on [water loss analysis](https://digitalbridge.com.tr/en/blog/water-loss-analysis.html).

Calculating spoil and stockpile volumes from the same drone imagery is covered in [drone stockpile volume measurement](https://digitalbridge.com.tr/en/blog/drone-stockpile-volume-measurement.html), and forecasting harvests on farmland in [drone crop yield estimation](https://digitalbridge.com.tr/en/blog/drone-crop-yield-estimation.html).

GIS logic applies equally to electricity and gas distribution networks. We explain how network assets combine with metering and SCADA (supervisory control and data acquisition) data in our [energy utility digital transformation guide](https://digitalbridge.com.tr/en/blog/energy-utility-digital-transformation.html).

Keeping network topology accurate on the map also pays off in loss analysis: once you know which transformer supplies which customers, [electricity theft detection](https://digitalbridge.com.tr/en/blog/electricity-theft-detection-analytics.html) can work transformer by transformer.

A city information system is one part of a council's wider transformation. The steps that connect applications, records and field crews are in our guide to [digital transformation in municipalities](https://digitalbridge.com.tr/en/blog/digital-transformation-municipalities.html), and examples of bringing sensor and meter data onto the map are in our article on [smart city applications](https://digitalbridge.com.tr/en/blog/smart-city-applications.html).

## How does Digital Bridge build municipal GIS?

At Digital Bridge we do not resell an off-the-shelf GIS licence; we build the application around your council's workflows, asset types and access structure. A typical municipal GIS project runs like this:

- **Needs and data inventory.** We map which department holds which spatial data in which format, then choose the first layer and a measurable goal with you. Scope, phases and cost are then set out in a written proposal.
- **Data migration and clean-up.** We move your CAD, base map and zoning data into a [web-based geographic information system](https://digitalbridge.com.tr/en/data-analytics/geographic-information-systems-gis.html), unify coordinate systems and flag contradictory records.
- **Mobile field app.** Crews add and update records with GPS, attach photos and keep working offline outside coverage. Where needed we extend this through [custom mobile app development](https://digitalbridge.com.tr/en/software-solutions/mobile-app-development.html).
- **Connecting systems.** We link GIS to billing, [automatic meter reading (AMR)](https://digitalbridge.com.tr/en/industrial-products/osos-meter-reading.html) and the document system, so the same customer and parcel are the same record everywhere. Our [solutions for public sector and municipalities](https://digitalbridge.com.tr/en/industry-solutions/public-sector-municipalities.html) describe the full connected setup.
- **Imagery base layers.** We add orthophotos and [drone data processing](https://digitalbridge.com.tr/en/data-analytics/drone-data-processing.html) outputs to the map, so the same area can be compared across dates side by side.
- **Tender support.** If GIS is being procured through a public tender, we help prepare a needs-based technical specification and review contractor deliverables, without being a bidder in that procurement.

Because the same team builds both the software and the field devices, integration between meters, data collectors and the map stays under one point of responsibility. Based in Adana since 2013, we work with clients in every province of Türkiye, remotely and on site. For neighbouring topics from data warehousing to management dashboards, see [our full Data & Analytics guide](https://digitalbridge.com.tr/en/blog/topic/veri.html).

## Where should a municipal GIS project begin?

Start with a short internal exercise: which service drew the most complaints or faults in the last three months, who holds the map of its assets, and when was it last updated? The answers point to your first layer. Then [get in touch](https://digitalbridge.com.tr/en/contact.html) and we will review your existing data together and draw up a measurable goal and phased plan for that first layer.

## Frequently Asked Questions

### Is a municipal GIS the same as a city information system?

In practice, yes. A city information system is how a municipality applies GIS: it brings zoning, infrastructure, roads, green spaces and customer data onto one map. What matters is not the name but whether departments share the same, current data. If the same parcel or customer appears as a different record in each department, the system is not doing the job of a city information system, whatever it is called.

### Can we use our old CAD drawings and map sheets?

You can, and you should. CAD projects, base maps and zoning data are imported, and different coordinate systems (such as ED50 and ITRF96) are converted to one. Missing or contradictory records are not deleted; they are flagged in a separate layer and corrected as field crews verify them on site. That way, years of earlier investment in the data are not wasted.

### Do we need to cover the whole municipality from the start?

No. Starting with one layer where decisions depend most on guesswork, usually the water network, is safer. Give that first layer a measurable goal, such as "find the valve to close within five minutes of a burst". Street lighting, roads or green space are added once the first layer is in daily use and meeting its goal.

### How does municipal GIS help reduce water loss?

Municipal GIS provides the base that every water loss measure depends on. To set up a district metered area (DMA), the map must show which valves to close, which customers fall in which zone and which main feeds each meter. According to Türkiye's Ministry of Agriculture and Forestry, average water loss was 31.6% in 2024, and metropolitan and provincial municipalities must cut it to at most 25% by 2028.

### Can field crews enter data where there is no mobile signal?

Yes. The mobile app is built to work offline: crews capture records with GPS location, photos and fault notes even outside coverage, and the data syncs with the central map once a connection is available. This is the single most important step in keeping the map current, because the update is made by the crew that fixes the fault.

### What should we do about personal data once customer records are on the map?

Customer names and addresses are personal data under KVKK, Türkiye's data protection law. Define which roles can see which layers, who may export data and how long records are kept, and keep an audit log of access and changes. Contractors and other departments should see only the layers their work requires, with customer details hidden wherever they are not needed.

### What drives the cost of a municipal GIS project?

The main cost drivers are the scope of the first layer and the number of assets in it, how clean your existing CAD and map data is, whether a mobile field app is needed, and how many integrations are required with billing, meter reading or document systems. A phased project that starts with one layer ties the budget to a first measurable result, and scope and cost are then set out in a written proposal.