Data & GIS
Why Data is the Hardest Part of Any GIS or Web Project
The hardest part of any GIS or web project isn’t the map or the application. It’s getting the data into a state where it can actually be trusted and used.
Data is the Hard Part
Most people assume the hard part of a GIS or web project is the interface, the map, or the application itself. It’s not. The hardest part is the data.
The Reality of Data: On paper, data sounds straightforward. In reality, it’s anything but. The biggest challenges are consistency, quality, and ownership. Even within a single organization, data can vary widely with different naming conventions, structures, and levels of completeness. Ownership is often unclear. Who maintains it, who approves it, and whether it can be shared publicly are not always defined. Even in government, where data is expected to be accessible, acquiring usable data can take significant effort.
Where Projects Break Down: Most projects don’t fail during development. They fail after. Teams get the data, build something on top of it, and then stop thinking about it. There is no maintenance, no update cycle, and no long-term plan. Over time, the data drifts. As it drifts, the system built on top of it starts to break down.
What People Get Wrong: Many assume the difficult part is serving the data. It’s not. Once data is clean and consistent, serving it is usually the easiest part of the system. The real work is getting it into that state in the first place.
A Real Example: In the private sector, compiling parcel data across multiple counties highlighted the issue. The data was available, but it was not consistent. Different formats, fields, and standards made it difficult to use. Aligning everything into a usable structure required far more effort than anything built on top of it.
How I Approach It: The most effective approach is to start simple and build from there. Establish clear naming conventions, enforce consistency early, and avoid overcomplicating the structure. Systems can always expand over time, but fixing a messy foundation is significantly harder.
What Would Actually Help: Data needs to be more accessible and more understandable. Not just easier to obtain, but easier to interpret. Much of the difficulty is not in getting the data, but in understanding what it actually represents.
The Bottom Line: The success of any system is determined by the quality and structure of its data. Get that right, and everything else becomes easier. Get it wrong, and nothing built on top of it will hold.