A new local government
On 1 November 1989 New Zealand’s local-government map changed abruptly. Hundreds of local bodies, including cities, boroughs, counties, catchment boards and other authorities, were reorganised into 86 regional and territorial authorities. The new councils inherited staff, maps, rating systems, engineering plans, property records, drainage information, environmental files and the unfinished business of their predecessors. They also inherited the practical problem that many of those records described the same places in different ways.
Council GIS work had begun before the reorganisation. Some local authorities had already been using computer mapping, and later surveys recorded implementations dating from before 1988. The new structure did, however, concentrate a wider range of functions inside larger organisations at the same time that digital mapping was becoming easier to buy and run. Property, planning, engineering and environmental information that had previously sat in separate agencies or departments increasingly had to be managed together.
The Resource Management Act 1991 added another spatial workload when it came into force on 1 October that year. Territorial authorities needed land-use and district-planning information, while regional councils worked across water, air, coast, catchments and other environmental functions. Many of the records involved boundaries, networks, sites or monitoring locations. A council could continue to produce paper maps for those functions, but the underlying information was becoming more useful when it could be maintained once and reused across several jobs.
The same reuse could begin with material that was barely digital at all. In May 2006 of Geotech Consulting sent two hand-drawn sheets of possible fault traces around Renwick. The traces had been interpreted from old RNZAF aerial photographs, newer council aerials and field observations, and were intended to be digitised into the council GIS. The consultant offered either to redraw them in CorelDraw and supply DWF files for transfer, or to let council staff digitise the sheets in-house. He also insisted that the approximate locations and interpretive nature of the traces be carried into the final output. The correspondence says the work had been requested by council officer . It is a small but revealing handoff: field interpretation became pencil lines, pencil lines became digital geometry, and the uncertainty could not sensibly be cleaned away by the software.
The early 1990s were therefore less a story of councils discovering maps than of councils reorganising information that was already geographic. Rates referred to properties. Consents referred to sites. Roads, water pipes and drains formed networks. District plans divided land into zones. Rivers and catchments crossed property and council boundaries. GIS arrived in local government at a point when the organisation itself was being asked to behave more like an integrated information system.
Topoclimate South assembled soil and climate information across roughly 800,000 hectares of Southland and South Otago between 1998 and 2001. About 900 automated dataloggers measured local conditions for mapping at 1:50,000, including accumulated heat expressed as growing-degree days. and , affiliated with the Topoclimate South Project, and from Geography co-authored a contemporary account of the work in 2000. Manaaki Whenua’s later history identifies Hutchinson as the project lead. worked with southern district and city councils, community partners and researchers to give landowners information for decisions about crops and land-use diversification. Soil and climate map series were distributed in 2002. The project helped stimulate growOTAGO, which extended a similar regional approach into Otago.
published growOTAGO in 2004 with NIWA, AgResearch, Manaaki Whenua, universities and other partners. The product included 92 climate maps, soil mapping and topographic and aerial context, distributed on four CDs and later through an online map service. and are among the research contributors identified in the technical histories. developed the website and CD presentation. The combination made regional land-resource information usable beyond the offices that had assembled it: farmers and advisers could compare soil and climate conditions when considering an existing activity or a possible new one.
Sources · 4
- Hutchinson, Richards and Risk, Aspects of accumulated heat patterns (growing-degree days) and pasture growth in Southland
- Manaaki Whenua, A history of New Zealand soil survey, 1990s restructuring and Topoclimate South/growOTAGO sections
- National Library of New Zealand catalogue record, GrowOtago: climate and soil maps
- Otago Regional Council GrowOtago map-service metadata
Adoption accelerates
Contemporary research from the provides a better national picture than a list of individual council purchases. and surveyed local-authority GIS use in 1992, and and compared the situation in July 1993 with February 1992. By 1995 and were examining how local-government GIS had developed since the 1989 restructuring. Their interest had already moved beyond whether a council owned GIS software to how deeply the technology was being used inside the organisation.
Marr and Benwell’s 1996 study described the council systems then in use. Their survey achieved a 74.4 per cent response rate, and 70 per cent of the responding organisations said they had GIS. They also reported that the majority of implementations had occurred in the previous three years, while some dated from before 1988. Adoption grew rapidly in the early 1990s, though councils followed different timetables.
The research also records a change in who managed GIS. Earlier systems were often associated with a planning, engineering or other specialist function. Marr and Benwell found a marked increase in responsibility moving towards information-services departments as councils tried to manage GIS as a corporate resource. That shift did not remove planners, engineers or GIS specialists from the work. It changed the organisational home of the databases, software, networks and support needed by several business units.
Their exploratory maturity model compared councils by their uses of GIS, the departments involved and the age of each implementation. The strongest indicators were the number of uses supported by GIS, the number of departments using it and the age of the implementation. A council with one GIS operator producing maps for one department sat at a different stage from a council where property, planning, engineering and environmental staff were all using the same spatial resources. GIS maturity depended on its use across departments as well as the maps produced.
GIS use varied across council departments. A 1997 New Zealand paper cited the finding that 70 per cent of local-government authorities had GIS but noted that only 20 per cent were actually using it for land-use mapping, although 45.5 per cent had intended to do so. The gap is a useful check on the adoption statistics. By the middle of the decade GIS was common in councils, but coverage of individual functions remained uneven.
Regional land-resource data, 1993–1994
Regional GIS depended on work to prepare the information held in it. and ’s 1993 report correlated land-use-capability units into a single classification for the area and supplied information for a GIS database. In 1994, Harmsworth and documented Gisborne–East Cape land-resource data for GIS, including rock, landform, land-system and soil information.
These reports show the regional data work behind the software installations. Scientists had to reconcile classifications and document fields so the records could be used consistently. Council GIS development therefore included both the systems operated within councils and the geographic information prepared with research organisations. The land-resource work connected regional planning needs with the national inventory discussed in Chapters 5 and 7.
The parcel becomes a key
Council GIS could use a parcel as a spatial link between rates, valuation, addresses, planning and consent records. Each system retained its own identifiers and update rules.
Those records served different purposes and used different levels of detail. Rating systems might rely on valuation numbers, cadastral data represented legal parcels, address files located places and planning systems used zones or sites that did not always match a parcel. Integration depended on stable identifiers and clear responsibility for updates.
The links could go stale. A subdivision might reach the cadastre before the council’s other systems, while addresses, rates and planning records changed on their own schedules. GIS teams had to maintain those relationships as well as the map layers.
Christchurch organised GIS as a council service. A 2003 study described the City Council's GeoData Services unit as a stand-alone operation that had been running for about three years, supplying and collating geographic information for other divisions. Asset management was a central job, but the list was broad: soils, waterways, zoning, sewage pipes, vacant residential land and the locations of building consents. Council financial material from 2001–02 records the expenditure. Environmental Services carried a specific GeoData Services overhead, aerial photographs were sold as an information product, and a related efficiency proposal identified a ten-person Product Delivery Team. That was an internal information service with customers, budgets and routine data maintenance, broader than a cartography desk.
Linking corporate records exposed inconsistencies between systems. In a 2005 analysis for the city's growth work, records from the Valuation Hub were linked through the council's GIS cadastral layer so floor area and rating information could be analysed by zone. At the beginning of November, 799 of 9,918 parcels in the Business and Central City zones did not link between the valuation system and the current cadastre. Some additional valuation records had no total floor area recorded at all. The two production systems disagreed about the same land records. Christchurch staff had to analyse the city while knowing that the database join itself was incomplete.
records show staff time shifting away from electronic Liquid Waste Plan conversion after GeoData Services was established. By October 2000 and April 2002, council maps were credited to GeoData Services and carried .dgn project filenames. In 2001 represented Christchurch as the local-government Data Modeller on the Crown emergency-services core-data project, working with ’s , who advised on UML and ISO/TC211 standards. The 2004 council annual report named , and among the staff who developed council-designed software that won an Intergraph award.
The regional council was solving a different set of problems. In 2003 used GIS as a geographic database for regional management, including bus-stop locations and attributes alongside wells and other natural and physical resource information. The wetland-data lineage included surveys from the 1980s and 1990s, a GIS database and a 1999 report. In 2003 the information was supplied to the and checked against satellite imagery from 1999 to 2003; coastal wetland work then combined field survey, aerial photographs and GIS entry. joined the regional council in 1997, working mainly in GIS analysis before moving into software development and GIS integration.
Selwyn supplies a useful smaller-district comparison. Its April 2006 Wastewater Activity Management Plan names as Asset Manager Water and states that MapInfo was used for spatial representation of wastewater assets. During Selwyn’s rapid growth, staff used desktop GIS for routine infrastructure asset management.
Waimate gives the small-council version of the same history. By June 2006 was the council's GIS Administrator. During the 12 June snowstorm he collected twelve additional snow-depth observations from callers around the district, data that NIWA then used in its regional reconstruction of the event. In March 2007 he was on the MapInfo-L mailing list answering a MapInfo Professional 8.0 problem under his Waimate title. A year later he described another practical job: create a marker point every metre down a pipe, join an Excel table to those points by distance using SQL, convert decimal distances to whole numbers and accept a little positional error to the nearest metre. It is an unusually good record of what a small council GIS job could involve: property and asset systems one day, local event data the next, followed by making imperfect data and desktop software work well enough to get the job done.
Hare described Waimate’s earlier work in a later account. He says he took the council GIS role around 2000, replacing , implemented the Bizeasset asset-management system created by , and engaged as a contractor to install MapInfo web browsers such as Encounter. He also remembers the less glamorous corporate work that sat around those systems: District Plan mapping, matching land parcels to rating information, LIM mapping and asset management. He wrote this recollection in 2025. His account describes how the council’s earlier systems led into its MapInfo work in 2006–08.
Northland shows a different corporate GIS problem: several organisations could be working on the same regional issue without holding their information in equally usable forms. The Whole of Northland biodiversity project, developed from 2005 and reported in 2007, began assembling a regional GIS database from council, conservation and community information. The report records different approaches to data collection and different levels of GIS capacity. Some district information had to be entered from NZMS260 grid references, and it notes that two district councils had limited GIS capacity without securely identifying which two in that statement. A 2008 follow-up for documented the work. of Wildland Consultants is named for the GIS work, had 613 covenant sites that could be compared with regional natural-area mapping, and other protection or management records were incomplete, erroneous or not spatial at all. Regional GIS integration therefore required converting and qualifying information before it could be compared across organisations.
Gisborne provides a particularly strong council-and-science example. From September 1995 Landcare Research and soil-conservation staff worked on the second-edition Gisborne-East Coast land-resource inventory. By October 1998 the 1:50,000 field sheets had been compiled and checked, and by mid-February 1999 the work had become a digital spatial database containing 7,790 mapped polygons and 104 land-use-capability units. The database was available through Landcare Research and held its own copy. More unusually, the remapped region was deliberately aligned with the council's administrative boundary so district-wide analysis no longer required staff to work across three older NZLRI regions and three classifications. The technical report also records land-use capability being used in district planning and credits a close working relationship with council soil-conservation staff. Here the council boundary shaped the compilation and maintenance of the GIS itself. It helped define how the national scientific database was rebuilt for practical local use. The report credits , , M. J. Page, , G. R. Harmsworth and M. McLeod as authors.
gives a much smaller but unusually concrete view of maintenance. Its 2004 Annual Report records a NZ$200,000 budget to update aerial photographs in the council's GIS system. The work did not proceed that financial year because of other commitments and less suitable prevailing conditions, so the budget was carried into 2004/05. By 2004, was budgeting for a substantial imagery refresh to keep its operational GIS current. Completing the work depended on aircraft availability and suitable flying conditions.
’s later records describe further GIS work. A project by and , undertaken in 2009, mapped the Alpine Fault through Buller, Grey and Westland using GIS, QMAP, fault mapping, RTK-GPS topography, sketch maps, aerial photographs, orthophotos and field checking. The project converted those sources into fault traces, attribute tables and planning-oriented Fault Avoidance Zones, generally at about 1:10,000. At Franz Josef, the report compared an Otago-derived trace with a dashed fault line already used by the regional council.
With those links maintained, staff could select a property and retrieve rates, planning or consent details from the systems that remained authoritative for each record. GIS supplied the geographic route between them.
Networks meet the ledger
Roads, water, wastewater and stormwater created another route into corporate GIS. Councils owned long networks of assets that had traditionally been recorded on engineering plans, as-built drawings, registers and maintenance files. By the 1990s financial and audit requirements were forcing local authorities to identify those assets more systematically, assess their value and condition, and prepare asset-management plans. Location was part of that record because a pipe or road segment could not be managed if the council did not know which physical asset the database entry referred to.
Nelson combined aerial capture with engineering records and field checks to build its asset GIS. The council now says GIS information on city properties had been available since 1993, while its later asset-management history dates GIS implementation and photogrammetric capture to 1994. The aerial capture supplied contours, buildings, road markings, kerbs, channels and visible fittings, but it could not tell the council everything about buried pipes. Staff checked coordinates and went back through engineering plans and field books for alignments, materials and ages. Where buried fittings could not economically be located, a best estimate went into GIS and the accuracy limitation was flagged. New assets then arrived through as-built plans and regular engineering updates. Photogrammetric capture and historical engineering records supplied different parts of the asset information.
left a different migration trail. Its current GIS metadata says kerb-line data had been acquired since 1987 and loaded into an older system called City Mapping. In 1996 those data were completely recaptured from aerial stereopairs for a new GIS. Later metadata places the maintained data in ArcSDE and records recurring aerial-refly updates.
A 1995 Esri user-conference paper by described ArcInfo as already being used by more than half of New Zealand city and district councils and linked GIS directly with infrastructure valuation. The broader connection between asset management and spatial information is supported by subsequent Audit Office reporting.
shows what that connection looked like at the working end of local government. In 2000 its GIS Manager, , described a MapBasic application that linked MapInfo to the Confirm asset-management system through DDE. When it began throwing a fatal internal error after users had installed or run Access 97, Roundill took the problem to the international MapInfo mailing list because the error was not documented and the council had run out of obvious places to look. His messages also show him swapping MapBasic solutions for data conversion, object creation and synchronised map windows. It was less a story of buying a finished corporate GIS than of keeping several pieces of software talking to one another with scripts, DLLs and whatever clues could be found from other practitioners.
The Audit Office later described councils collecting key information about their infrastructure, developing asset-management plans and improving the links between the general ledger, fixed-asset register, asset-management plan and long-term financial strategy. By the 2000–01 financial year all local authorities had received unqualified audit opinions in relation to reporting infrastructural assets. GIS sat inside that larger information environment where the geometry of a network could be connected to the identifiers and attributes used for maintenance, valuation and planning.
The network map therefore changed function. A water-main line no longer existed only to show where the pipe was thought to run. It could be linked to diameter, material, installation date, condition, break history, replacement cost or maintenance work. A road segment could connect geometry with surface, classification, condition and financial records. The map became one view of an asset register whose other parts might live in dedicated engineering, asset-management or financial systems.
That integration also made poor data harder to ignore. A missing pipe, duplicate asset identifier or road segment with no reliable length could affect mapping, engineering and valuation at the same time. Corporate GIS created more ways to find inconsistencies because several systems were now expected to refer to the same physical object. Cleaning the data was rarely a single conversion exercise. It became continuing maintenance.
Dunedin’s lifelines work also identifies the council staff doing the mapping. The December 1998 Dunedin City Lifelines Project report names , Senior GIS Analyst, and , GIS Analyst, in City Consultants at . The report acknowledged the group’s GIS mapping as essential to the project. Garrett and Nicol produced mapping for infrastructure and hazard assessment.
Wellington hazard data, 1996
In April 1996, , working with Kingston Morrison and Victoria University of Wellington, reported on combined earthquake hazard mapping for . Existing digital layers in Arc-Info format covered ground shaking, liquefaction, slope failure, active faults and tsunami inundation. The project translated those data into TECHBASE and used a 10-metre grid to calculate a combined hazard index.
The calculations considered representative infrastructure, including utilities. They assumed a uniform distribution of assets to compare relative hazard between areas. The maps therefore supported regional assessment rather than locating each actual pipe or cable. Council hazard data, consulting work and university participation supplied a further strand of New Zealand GIS practice in the same period as national mapping programmes.
Sources · 2
- Ian R Brown Associates with Kingston Morrison and Victoria University, Preparation of comprehensive earthquake hazard maps, April 1996, WRC/RP-T-96/22, pp.1 and 16
- Ian R Brown Associates with Kingston Morrison and Victoria University, Preparation of comprehensive earthquake hazard maps, April 1996, WRC/RP-T-96/22, pp.1 and 16
A corporate system
By the mid-1990s, the phrase corporate GIS was appearing because councils were trying to move beyond isolated applications. Departments could share spatial information while retaining separate applications and databases. The corporate model managed common spatial data and services across the organisation.
The GIS team’s work broadened accordingly. Staff still produced maps and carried out analysis, but they also maintained shared layers, managed links to business systems, defined update procedures, supported users and dealt with coordinate and data-conversion problems. Information-services staff became more involved because the GIS increasingly depended on corporate networks, servers, database platforms and backup arrangements. Marr and Benwell’s surveys captured this movement of responsibility while it was happening.
The change created a practical tension between central control and distributed use. A council wanted one authoritative road centreline, one maintained property framework and one current set of planning zones, but planners, engineers and property staff wanted to use those records in their own work. Desktop GIS made copies easy to create, as Chapter 22 described. Corporate GIS tried to keep the master information central while allowing more people to query or analyse it.
Duplicate copies of data continued to require management. Departments could still build their own layers, contractors could return files in different formats and project directories could accumulate old extracts. The corporate model provided a place to decide which version should be treated as current. It also created a clearer route for correcting an error once and propagating the change to several users rather than relying on everyone to repair their own copy.
Planning as data
Planning records were particularly suited to this arrangement because councils already maintained maps that divided land according to regulatory rules. District schemes and later district plans contained zones, designations, hazards and other mapped provisions. GIS allowed those boundaries to be stored as maintained features that could be queried beside properties and other council records rather than redrawn for each map edition.
The link to property made planning information more useful inside ordinary council work. A planner could identify which rules applied to a site, while property and building staff could see the same zoning or hazard information beside their own records. Engineering staff could compare proposed development with roads or services. The planning layer remained a regulatory dataset with its own legal status, but it could participate in a wider corporate information environment.
Regional councils had a different emphasis. Their work involved catchments, rivers, groundwater, air, coast, land resources, hazards and monitoring networks across large areas. GIS provided a way to maintain those scientific and regulatory records alongside administrative and property references, but the national surveys caution against assuming that every intended use was immediately operational. The technology spread faster than some of the business processes built around it.
One Hawke's Bay report shows exactly how GIS sat inside this work. In April 2006 's Heretaunga Steady-State Ground-Water Model drew data from council systems called WellStor, Daisy and Hilltop, along with compliance pumping records. The acknowledgements name the people behind the inputs: for water levels, for wells, for compliance pumping, for groundwater consent allocations, for surface water, and for the graphical-information-system contribution. GIS was not the groundwater model itself. It was part of the assembly that made separate monitoring, consent and well records usable together. Two years later, Hall took part in the regional practitioner forum as the council's GIS Coordinator.
Regional, city and district councils had different statutory responsibilities and therefore different GIS priorities. A district or city council might build its corporate GIS around property and infrastructure because those records drove rates, planning and services. A regional council could depend more heavily on catchments, environmental monitoring and resource-management information. Both were moving towards shared organisational systems, but they were not solving the same set of problems.
The people behind the database
Much of the work happened below the level recorded in annual reports. Legacy engineering plans had to be digitised. Property references had to be reconciled. Old coordinate systems and local survey frameworks had to be understood. Network geometry needed topology and asset identifiers. Planning maps had to be converted while retaining the distinctions embedded in their legends and rules.
GIS staff did some of this work directly, but council systems depended on a broader group. Rates and property teams maintained accounts and valuation references. Engineers and asset managers supplied network and condition information. Planners maintained regulatory records. Survey, road-naming and addressing staff updated reference information. Database administrators and information-services staff maintained the systems that allowed those records to be joined and distributed.
Contractors and software suppliers also carried a share of the conversion and integration work. A council could buy software relatively quickly; converting decades of local records into reliable corporate data was slower. The cost of implementation therefore extended well beyond the licence. Staff time, capture, validation, database design, interfaces and training could continue for years after the initial purchase.
Council GIS teams worked across cadastral data, utilities, asset registers, planning, environmental layers, map publishing and departmental support. Staff configured systems, reconciled records, built applications and kept information current alongside daily council services.
’s MapInfo-L correspondence identifies as GIS / IT Support in 1999 and IT/GIS Manager in 2000. He described MapInfo Professional 5.5, substantial MapBasic coding, Windows NT 4.0 and plotting to an HP DesignJet 750C. A separate council cemetery plan, drawn in 2000, modified in 2001 and current to November 2002, states that it was produced on the council’s CAD/GIS system using AutoCAD 2000 and MapInfo Professional 5.5, with cadastral information derived from the LINZ Digital Cadastral Database. Together the records show routine council map production supported by code, plotting and cadastral data.
An August 2000 MapInfo-L message from , ’s IT Officer, describes a MapInfo 6 Hotlink workflow. From a map layer, 78 mapped objects opened separate MapInfo workspaces. Simon also records a mixed desktop environment running Windows 2000 and Windows 95/98. The correspondence documents operational desktop GIS at Hurunui by that date without establishing when the council first used GIS.
’s Significant Natural Areas survey ran from 2005 to 2016. The council-hosted 2016 report says confirmed areas were delineated in the council’s electronic mapping system, GIS, and that the information fed into property and LIM records. It names and as District Council GIS staff. The report does not establish their individual start dates or identify a software vendor for the 2005 workflow.
Some of those staff and collaborators can now be recovered by name. Northland Regional Council’s Janelle Palmer developed a web afforestation viewer for hill-country erosion work. Far North District Council planner Rachael Pull and consultant Logan Ashmore later presented the GIS foundations for the council’s open-space programme. Boffa Miskell GIS specialist Hayley Hume-Merry combined desktop capture, iPad field verification and dashboards in Wellington City Council’s character-area review. Other 2017 conference cases name Ashley Dunstan and Jimmy Millar in Hastings District Council’s Havelock North water-contamination GIS response, Sean Audain on Wellington’s smart-city geospatial work, and Anya Duxfield on web GIS for Far North district-planning engagement.
Sources · 9
- Gore District Council, Gore Cemetery Plot Layout and Site Plan, drawing 1608-02
- Tony Shepherd, MapInfo-L correspondence, 11 August 1999
- Tony Shepherd, MapInfo-L technical correspondence, 21–26 August 2000
- Jolanda Simon, ‘Hotlink tool in MI v6’, MapInfo-L technical correspondence, 22 August 2000
- Timaru District Council, Significant Natural Areas survey report, July 2016
- Northland Regional Council, Hill Country Erosion Fund final report
- Eagle Technology, 2020 Virtual User Conference Series
- Boffa Miskell, Engagement innovations win awards
- New Zealand Esri User Conference programme, 2017
Auckland works across boundaries
By 1999, several Auckland councils had established GIS systems and needed to use information across council boundaries. The eight territorial authorities and the identified GIS as an area in which they could work together. They were using different GIS platforms, so collaboration did not begin with choosing one common software environment.
The group instead concentrated on shared information. The Office of the Auditor-General later documented how a GIS Working Group created a Standards Working Group to compare the aerial-photography specifications being used by the councils. The resulting Auckland Area Orthophotography Standard was finalised in February 2003. Acquisition standards had become a regional coordination task for council GIS; Chapter 20 describes the imagery programme.
The councils had all invested in spatial information about the areas they administered, while the Regional Council needed information across the whole metropolitan region. Roads, planning, environment and imagery crossed organisational boundaries whether or not the databases did. Agreement on a shared orthophotography specification allowed several systems to use a common input without requiring the councils to replace their existing GIS platforms.
This was corporate GIS extending beyond a single corporation. The same principles applied at regional scale: agree what the shared resource represented, define enough common standards for it to be reused, then allow different organisations and systems to work from the result. The technology was heterogeneous, but the data had to line up.
Maps from all over council
The archival record from Palmerston North gives a more ordinary view of how widely mapping had spread. Archives Central holds a map series covering approximately 1990 to 2005. Its description says maps were made by all units of council for current and future planning and specifically names City Corporate, Future Planning, GIS and Civil Defence among the sources.
The individual records include base maps, district-planning maps, demographic material, ecological assessment, civil-defence maps and items explicitly catalogued as GIS maps. The council produced maps for several departments and functions.
Corporate GIS also produced paper sheets. Councillors, field staff, planners, engineers and the public continued to use printed maps even as the databases became digital. A corporate system changed how the information was maintained and reused. It did not make every output electronic overnight.
By the early 2000s this was common enough that the map itself was no longer the best measure of GIS maturity. The more revealing questions concerned who could use the data, how many business functions depended on it, whether the same information fed several outputs and whether changes were maintained centrally. Those were the kinds of variables Marr and Benwell had begun measuring in the previous decade.
Napier develops MAPiT
’s 11 July 2003 Brisbane User Forum presentation, “A Napier Encounter!”, identifies him as GIS Administrator in ’s Planning Department. It traces MAPiT through three generations: MapXtreme 2 with static HTML; MapXtreme 3 with MapInfo Encounter and Java applets; and MapXtreme 4 with Encounter 3, XML/XSLT and an image viewer. The internal environment included 109 Encounter users and links to SQL Server, Hansen IMS and a Unix corporate system. MAPiT served the intranet, the public front counter and an internet site.
Upper Hutt puts property online
put property information online through XPLORER in February 2003. The service brought property and rating details, property values and aerial photographs into a browser; previously, residents commonly visited the council for a paper property-information packet.
The e-government case recorded about 26,000 map downloads a month and fewer in-person property enquiries after launch. Staff could direct people to the website for routine property information.
Behind the viewer, property and rating records had to be linked to spatial features, while aerial photographs and other layers were stored and published. Updates still depended on council systems and staff maintaining the underlying data.
In 2013 Upper Hutt upgraded XPLORER for mobile access using HTML5. The council described property and rating details, underground services and district-planning information, including use by contractors checking records in the field.
Chapter 30 follows the wider spread of browser GIS in New Zealand.
Tauranga expands internal mapping
’s June 2022 meeting record says moved from Land Information Officer to the GIS team in 2004. He developed and managed the internal SmartZoom viewer, managed SmartViewer and internal mapping, and supplied GIS support to emergency management.
Control and responsibility
Wider use created questions about who could change the data. A planner might need to edit a zoning layer while a customer-services user needed only to view it. Engineers could update asset information through controlled workflows while the public saw a selected subset. Corporate GIS therefore required permissions and update responsibilities that were unnecessary when one specialist operator controlled a standalone system.
It also required decisions about which system owned each attribute. The GIS might be authoritative for the geometry of a council-maintained feature while a rating, consent or asset-management system remained authoritative for business attributes. Integration worked best when those responsibilities were explicit. Otherwise the same value could be maintained in two places and drift apart.
By the 2000s, councils linked GIS to databases for rates, consents, assets and customer services. GIS staff maintained the geometry and the links between records; other staff used the information through the business systems and viewers they used each day.
Marr and Benwell’s 1996 study described this move towards corporate GIS, with spatial information serving organisation-wide information and decision processes. A decade later, council property viewers and shared regional data programmes put that approach into practice.
Continuing council development
Councils took different paths into corporate GIS. Size, responsibilities, budgets and existing data shaped whether the work sat with a specialist team, one or two staff, an outside supplier or a regional partnership. Cities, districts and regional councils also had different information needs.
Departments shared information while retaining separate systems. Old datasets survived, business systems were replaced at different times and network records remained incomplete in some places. The Audit Office continued to report weaknesses in asset information after GIS had become common. A council could have an advanced spatial system and still be uncertain about the age or condition of underground infrastructure.
The software environment remained mixed. ArcInfo and ArcView were widely used, while MapInfo and GeoMedia had established council markets. Different products served different tasks, with shared, maintained information connecting the work across departments.
By the 2000s and early 2010s, GIS was a standard council information service in much of New Zealand. Property, planning and asset data were being made available through more than one application. Internal viewers widened staff access; public services exposed selected records outside the council. Regional programmes shared information that crossed council boundaries.
Council GIS increasingly connected maintained spatial data to departmental databases, staff viewers and selected public services. Shared regional projects extended those links across council boundaries. Chapter 24 follows the corresponding expansion of GIS across central government.
’s 1996 pedestrian-crossing mapping project for is part of ’s business history, described in Chapter 12.
Council maps become a public data source
A 2026 Ngā Poutama Matawhenua session used Bay of Plenty Regional Council’s BayMaps as a case study in finding and reusing local-government GIS information. The session treated council viewers and datasets as working inputs for iwi, hapū and community projects rather than as finished maps to be viewed passively. LINZ’s career profiles reinforce the same transition from inside the council: Amit Kokje described geospatial platform and support work at Auckland Council, Rebecca McMorran combined transport analysis with GIS at Wellington City Council, and Jana Kaeppler described web mapping, cemetery information, 3D work and core data management at Mackenzie District Council. These examples provide named practitioner links without turning the chapter into a staff directory.
Sources · 1
Chapter source notes
1. The institutional reset is supported by official local-government history for the 1 November 1989 reorganisation. The chapter uses restructuring as context and does not claim it caused GIS adoption.
2. The Resource Management Act 1991 date and commencement are drawn from the legislation. The chapter treats the Act as one source of demand for integrated land, planning, regulatory and environmental information and does not state that it mandated GIS.
3. Andrew Marr and George Benwell’s GIS maturity and integration research is the principal national adoption evidence. Their survey reported a 74.4 per cent response rate and GIS in 70 per cent of responding organisations, with most implementations occurring during the previous three years and some predating 1988. The 70 per cent figure remains explicitly a percentage of respondents.
4. Marr and Benwell also support the organisational interpretation of corporate GIS, including their measures of number of uses, departments and implementation age, and the increasing role of information-services departments in managing GIS as a corporate resource. Their maturity model is research, not an official standard.
5. Charles A. Hansen’s 1995 Esri user-conference paper is used as contemporary evidence linking ArcInfo use in councils with infrastructural-asset valuation. Its statement that ArcInfo was used by more than half of New Zealand cities and district councils is treated as a contemporary conference/vendor statement rather than independent market-share research.
6. Office of the Auditor-General reporting supports the broader asset-management setting: councils collecting infrastructural-asset information, developing asset-management plans, valuing assets and linking this material with financial and long-term planning requirements.
7. Auckland cross-council coordination is supported by the documented collaboration of eight territorial authorities and the Auckland Regional Council from 1999, despite different GIS platforms, and the GIS/standards work that produced the Auckland Area Orthophotography Standard finalised in February 2003. Chapter 20 retains the orthophotography history; Chapter 23 uses this only as corporate coordination evidence.
8. Upper Hutt City Council’s XPLORER case is supported by the e-government record documenting online property information from February 2003, property/rates information, values, aerial photography, approximately 26,000 map downloads per month and reduced in-person enquiries. Later 2013 material is used only for the functionality documented at that later date. XPLORER is not called New Zealand’s first public web GIS.
9. Archives Central’s Palmerston North record set PNCC 00086 supports the bounded archival statement that council map records from approximately 1990–2005 included City Corporate, Future Planning, GIS and Civil Defence. No software or database architecture is inferred from the catalogue.
Sources: Manaaki Whenua ICM, Garth Harmsworth bibliography: 1993 Bay of Plenty and 1994 Gisborne–East Cape GIS data reports (https://icm.landcareresearch.co.nz/about/people/garth_harmsworth.asp).
Contemporary report, pp.1, 6–16. TECHBASE use does not establish New Zealand software authorship.