Intro:
You ever open a map app, zoom around a bit, and think, “This is cool—I could do this for a living”? Well, guess what? You can! But if you’re dreaming of becoming a GIS Administrator, let me pop that bubble of easy-breezy cartography and introduce you to the spicy world of GIS infrastructure.
Spoiler: It’s less Indiana Jones with a compass and more sysadmin who yells at a spatial database at 2 AM because someone imported a 300MB shapefile with no projection.
What the Heck Is a GIS Admin Anyway?
Think of a GIS Admin as a slightly caffeinated wizard who keeps the geospatial world from imploding. Sure, people think we “just make maps,” but you and I know the truth: we keep the whole damn planet spinning (digitally, at least).
You’ll be that behind-the-scenes MVP who:
- Keeps the ArcGIS Enterprise servers alive through software updates and sheer willpower
- Babysits SQL Server like it’s a toddler holding a chainsaw
- Deals with user permissions like a digital bouncer (“No, Karen, you still can’t publish services”)
- And explains (again) that “the map is slow” probably means the user’s Wi-Fi is garbage
GIS Infrastructure: Where the Real Drama Happens
Let’s break this down like a brittle shapefile in ArcMap 10.3:
1. Servers, Glorious Servers
You’ve got ArcGIS Server, Portal, Data Store, and Web Adaptor — basically the Four Horsemen of your IT apocalypse. And yes, they all need patches. Constantly. And yes, that means downtime on Friday at 4:59 PM.
If you’re lucky, it’s all virtualized. If you’re not, it’s on a 2012R2 server under someone’s desk next to a space heater.
2. Databases — AKA “Where the Magic Dies”
Enterprise geodatabases (SQL Server, PostgreSQL, etc.) are where your lovely spatial data lives, cries, and gets corrupted. You’ll write SQL queries that either save the day or crash production. There is no in-between.
Bonus: vacuuming PostGIS tables is not about cleaning. It’s about pain.
3. Web Hosting for Geonerds
Hosting web apps? Congrats, now you’re also a reluctant front-end developer. Get ready to deal with Experience Builder updates, JavaScript errors, and one guy who still uses IE11.
4. Networking & Firewalls
Your maps don’t load because the firewall said no. Welcome to learning ports, proxies, and why your public-facing apps suddenly broke after a Windows Update.
Pro tip: Learn how to sweet-talk your network engineer. Or become one.
5. Security & User Management
You’ll be neck-deep in SAML, Active Directory groups, Portal roles, and panic. You’ll lock it down so tight even you can’t log in anymore.
What You’ll Need (Besides Therapy):
- Windows Server Skills – ArcGIS Enterprise lives here and it’s not moving
- SQL Sorcery – You’ll write queries, troubleshoot locks, and maybe scream
- Python + PowerShell – Automate your way out of burnout
- Basic Networking Knowledge – Because “the map won’t load” is always your fault
- Backup & DR Planning – Because someone will delete the production database “by accident”
Certs That Make You Look Smarter:
- Esri Admin Associate (the official “yes, I know what I’m doing” badge)
- CompTIA Network+ (if switches and subnets make you weep)
- Azure Admin (if your boss says “cloud” but means “mystery”)
- PostgreSQL Certs – Just to feel something
Daily Toolkit of GIS Admin Glory:
- ArcGIS Monitor – Because watching logs is your new hobby
- SSMS / pgAdmin – The place where queries go to die
- Notepad++ – For scripting, notes, and digital crying
- Task Scheduler / cron – So you can nap while jobs run
- GeoJobe Admin Tools – Aka your “I’m not doing this manually” savior
Final Thoughts (Before You Rage-Click Out):
Being a GIS Administrator focused on infrastructure is like being a map wizard and server janitor rolled into one glorious, underappreciated role. You don’t just make maps — you make them possible. You fight DNS demons, rebuild corrupt tile caches, and protect the portal like it’s your digital baby.
And when that shapefile from 2004 comes knocking with 900,000 features and no metadata? You’ll be ready. Or at least have a backup.