← All resourcesGIS · 2026 · Cornerstone
What "GIS-native" actually means for municipal asset management
Almost every asset management vendor claims "GIS integration." Very few are actually GIS-native. The distinction is not marketing — it determines whether your map is ever wrong.
Reference vs. copy
A copy-based system imports your ArcGIS features into its own database on a sync schedule. The moment your GIS team edits a feature, the two are out of step until the next sync — and conflicts get resolved by whoever wrote the last import.
A GIS-native system stores only a reference: the feature’s ObjectID and its layer URL. Every time it needs an attribute, it queries ArcGIS live. Your GIS stays the single source of truth, and the map is never stale.
Ask any vendor one question: "When my GIS team edits a feature, does your system show the change immediately, or on the next sync?" The answer tells you everything.