The user from Portugal who wants a map of their municipality divided by parishes is facing a problem that millions of spreadsheet users know intimately: the tool they rely on daily simply wasn't built for the data they actually have. They have the boundaries in DWG, Shapefile, and KML, standard formats in any GIS toolkit, yet Excel offers no path from those files to a chart. That gap is not a minor inconvenience. It is a fundamental limitation of legacy spreadsheet design.
This is not a complaint about a single missing feature. It is a clear signal that the definition of a spreadsheet must evolve. Data is no longer confined to rows of numbers and text. It lives in geographic coordinates, in polygons that define a parish border, in layers that give a dataset its shape and context. A modern spreadsheet should treat a shapefile not as an alien artifact, but as a first-class data type. The user should be able to import that municipal boundary, assign it population or revenue figures, and produce a thematic map in minutes. That is not a luxury; it is the logical next step for anyone who manages location-based data, whether they work in local government, urban planning, real estate, or logistics.
The practical implication is straightforward: if your spreadsheet cannot read the formats your municipality already uses, you are spending time converting files instead of analyzing insights. The user here is considering falling back to CAD software, which would be faster than anything in Excel today. That is a valid workaround, but it is a concession, not a solution. Every time a user has to switch tools to complete a task that should live entirely within their spreadsheet, the tool has failed. The promise of AI-native spreadsheet technology is that it can close this gap by understanding context, recognizing that a KML file contains boundaries, not just coordinates, and knowing how to render it without requiring users to learn GIS terminology or export workflows.
The takeaway is concrete: if you have ever felt constrained by what your spreadsheet can import, you are not asking for too much. You are asking for the right thing. The only question is whether the tools you use will evolve to meet that need. For now, the user in Portugal will likely export to CAD or a dedicated GIS tool. But that should be a choice, not a necessity. The next generation of spreadsheets should make that map import feel as natural as typing a number into a cell. Anything less leaves too much data on the table.