How to Build a Streetlight Inventory Database with a Map

A streetlight inventory database is only as useful as it is accurate and accessible — and a list of fixture IDs in a spreadsheet that only one person can open fails both tests.

Public works departments that manage hundreds or thousands of streetlight fixtures need an inventory that combines structured data — fixture type, installation year, warranty status, ownership — with spatial location so every record is tied to a point on the map. When those two things are separate, you answer the question "where is fixture SL-4821?" by looking it up in a spreadsheet and then searching an address in a separate GIS tool. When they're unified, you click the fixture on the map and the full record opens immediately.

Atlas gives you a browser-based platform where your streetlight inventory database and your live map are the same thing — every fixture is both a geographic point and a structured data record, accessible to field crews and administrators without any desktop GIS software.

Here's how to build it from scratch or migrate from what you have now.

Why a Structured Inventory Database Is the Foundation of Streetlight Management

A fixture you can't accurately describe is one you can't efficiently maintain.

The inventory database isn't separate from operations — it's the data layer that makes every operational decision faster and better informed.

Step 1: Define Your Data Schema Before You Import Anything

Before importing a single record, decide what fields every fixture will carry:

Unique fixture ID — a stable alphanumeric identifier that doesn't encode location or address, so it survives pole moves and street renames without requiring renumbering
Geographic coordinates — latitude and longitude in decimal degrees, or a street address for geocoding, as the primary spatial anchor for each record
Fixture classification fields — fixture type, light source technology (HPS, MH, LED), pole material, pole height, mounting configuration — the attributes that determine maintenance approach and replacement parts
Ownership and billing fields — municipal-owned, utility-owned, developer-installed, or BID district, with the corresponding account number or agreement reference
Installation and warranty fields — installation date, warranty expiration, installing contractor, original specifications reference — the documentation that determines cost responsibility when failures occur
District and route assignment — the maintenance district, crew route, and management zone each fixture belongs to, enabling filtered views for dispatching and reporting
Current condition and status — functioning, out, flagged, under repair, scheduled replacement — the operational status that changes with every work order completion

Defining the schema first prevents the most common inventory migration problem: discovering halfway through import that your source data has a field you didn't plan for and no clean place to put it.

Step 2: Audit and Clean Your Existing Inventory Data

Your existing data is the starting point — but it needs preparation:

Export everything from your current source — spreadsheet, CMMS, legacy GIS system, paper ledger — into a single CSV file with one row per fixture and consistent column names
Identify and flag duplicate records where the same physical fixture appears twice under different IDs or slightly different addresses
Standardize fixture type values across entries that describe the same fixture type in different ways — "cobra head," "cobrahead," and "CH" all mean the same thing and need to be unified before import
Note records with missing coordinates where only a street address exists, and records with missing addresses where only a fixture ID exists — these need different treatment during geocoding
Flag obviously wrong records where coordinates place fixtures in bodies of water, outside your jurisdiction boundary, or at coordinates of 0,0 — these need field verification before or after import

A cleaned source file produces a much better initial import than raw data from a legacy system that accumulated inconsistencies over years of manual entry.

Step 3: Import and Geocode Your Fixture Records in Atlas

With your cleaned CSV prepared:

Import CSV into Atlas using the data import tool, mapping your column names to the standard Atlas attribute fields you defined in Step 1
Run automatic geocoding for records that have street addresses but no GPS coordinates — Atlas matches addresses to map locations and places each fixture point on the aerial imagery base map
Review geocoding results by scanning the map for fixtures placed on wrong blocks, offset from the street, or appearing in the wrong location — these need manual coordinate correction
Import GPS coordinate records directly if your source data includes latitude/longitude columns, bypassing geocoding for fixtures already surveyed with a GPS device
Validate placement visually by switching to satellite imagery base map and confirming each fixture appears on an actual pole location rather than a nearby parcel or intersection

The result is your full existing inventory as a geographic dataset — imperfect, but spatially located and ready for enrichment.

Step 4: Enrich Records with Classification and Documentation

Now populate the fields that make the database operationally useful:

Run a field verification sweep for fixtures where type, technology, or condition is unknown or inconsistent, sending crews to record the actual fixture specifications at each location
Attach installation documentation — original specs, contractor records, warranty certificates — to each fixture where this paperwork exists, creating a digital record linked to the map point
Upload baseline condition photos so the initial physical state of each fixture is documented before any maintenance is recorded
Assign district and route codes to every fixture using a bulk assignment tool based on geographic overlap with district boundary layers, eliminating manual record-by-record assignment
Cross-reference utility billing records to verify ownership classification against what the utility has on file, correcting discrepancies that would otherwise create cost responsibility disputes

Also read: How to Map Streetlight Locations with GPS

Step 5: Configure Access Roles for Different Users

Your inventory database serves different people with different needs:

Field crews need quick access to fixture location, type, work order history, and access notes — they don't need to see utility account numbers or warranty documentation
Maintenance supervisors need filtered views by district showing open work orders, fixtures overdue for inspection, and aging inventory approaching end of service life
Administrators need full record access including ownership, billing information, and cost history for budget reporting and capital planning
Utility account managers need the ownership and account reference fields to reconcile billing, without visibility into operational maintenance detail
Public works leadership needs a dashboard view showing portfolio condition summary, work order volume trends, and capital replacement pipeline — not individual fixture records

Atlas lets you configure role-based access views so each user type sees the right subset of information without the complexity of the full database.

Step 6: Establish Data Maintenance Protocols That Keep the Database Current

An inventory database is only as useful as it is current:

Require status updates at work order close so every completed repair, replacement, or inspection is recorded against the fixture's map record before the work order closes
Add new fixtures to the database at installation — not after, not at the next audit — so every new asset is in the inventory before it enters service
Decommission removed fixtures immediately rather than letting them linger as ghost records that inflate active inventory counts
Schedule an annual field verification comparing the database to physical conditions, correcting positions, updating conditions, and capturing any fixtures that were installed without being added to the system
Audit for orphaned records — entries in your work order system that reference fixture IDs that don't exist in the inventory database — and resolve each one before it creates reporting inaccuracies

Use Cases

Building a streetlight inventory database with a map matters for:

Municipal public works departments managing inherited or fragmented fixture records from multiple decades of installation projects who need to consolidate everything into a single authoritative source
Utility companies with streetlight service agreements who need to maintain customer-owned fixture records alongside utility-owned infrastructure for billing and maintenance separation
Newly incorporated municipalities or growing jurisdictions that are building their first formal streetlight inventory after years of informal tracking in whoever's spreadsheet
Transportation departments managing highway and arterial lighting separately from residential city lighting who need a clean database boundary between the two inventories
Engineering firms conducting comprehensive streetlight audits and retrofits who need a data collection and database-building tool that produces a deliverable their client can continue to use

It's critical for any organization that can't currently answer "how many fixtures do we have, what type are they, and when were they installed?" without significant research effort.

Tips

Don't wait for perfect data to start — an imperfect database that's spatially located and accessible is more valuable than a perfect database that exists only on one person's desktop
Use a fixture ID prefix that encodes nothing — avoid IDs like "MainSt-001" that embed location information which breaks when the fixture is moved or the street is renamed
Store GPS coordinates in decimal degrees rather than degrees-minutes-seconds — it's the standard for digital mapping and eliminates conversion errors when importing from GPS devices
Document your schema decisions in a data dictionary that any new staff member can read — when the person who set up the system leaves, the next person needs to understand what every field means and how values are standardized
Plan for the warranty tracking use case from the beginning — it's easy to add warranty date fields at database creation and nearly impossible to reconstruct them from paper records two years later

A streetlight inventory database built on Atlas gives your organization the spatial, structured, and accessible fixture records that transform infrastructure management from a guessing game into a data-driven operation.

Streetlight Inventory Management with Atlas

Managing streetlight infrastructure at scale requires knowing exactly what you have — fixture type, technology, age, ownership, and condition — and where every fixture is located. That knowledge lives in your inventory database, and Atlas makes that database a live, spatial tool accessible to everyone who needs it.

From Scattered Records to a Unified Database

With Atlas you can:

Consolidate fixture records from spreadsheets, legacy GIS files, and paper inventories into a single geocoded database in a single import session
Enrich records with classification, documentation, and condition data in the field or the office from any device
Assign district and route codes in bulk using geographic boundary overlays so every fixture is correctly categorized without manual record-by-record work

Also read: How to Create a Streetlight Asset Map for Your Municipality

Data That Supports Every Decision

Atlas lets you:

Filter your entire fixture inventory by district, type, age, or condition to identify patterns and prioritize maintenance resources before failures drive the decision
Export complete inventory data for capital improvement planning, grant applications, and utility billing reconciliation at any time
Track warranty expiration dates and installation ages across your entire portfolio so planned replacements happen before emergency repairs become necessary

That means no more "we'll check when we get there" — and no more discovering that the fixtures in a newly annexed area haven't been added to any inventory system.

Inventory at Any Scale

Whether you're building your first digital streetlight inventory for 300 fixtures in a small municipality or consolidating a 40,000-fixture database after a merger, Atlas handles the data volume without requiring specialized GIS expertise.

It's streetlight inventory software built for public works — not a database administrator.

Build Your Streetlight Inventory Database Today

Every maintenance decision, budget request, and capital improvement plan depends on knowing what you have. Atlas gives you the platform to build and maintain that knowledge without enterprise software complexity.

In this article, we covered how to build a streetlight inventory database with a map — from defining your data schema and cleaning existing records to importing, enriching, configuring access, and keeping data current through daily operations.

From the initial inventory build through ongoing maintenance tracking and capital planning, Atlas supports the complete streetlight asset lifecycle in a browser-based platform any staff member can use.

So whether you're starting from a spreadsheet with 500 rows or migrating from a legacy system that takes a GIS specialist to operate, Atlas gets you to a live, spatial inventory faster.