{"id":34748,"date":"2026-04-07T14:39:50","date_gmt":"2026-04-07T14:39:50","guid":{"rendered":"https:\/\/www.ogc.org\/?p=34748"},"modified":"2026-04-10T09:12:03","modified_gmt":"2026-04-10T09:12:03","slug":"common-challenges-in-geospatial-integration","status":"publish","type":"post","link":"https:\/\/www.ogc.org\/blog-article\/common-challenges-in-geospatial-integration\/","title":{"rendered":"Common Challenges in Geospatial Integration","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Data integration is often where geospatial projects slow down. It is a critical step in building a Spatial Data Infrastructure (SDI), and it is often where a great deal of time is spent. This is largely due to the chronic lack of adherence to FAIR (Findable, Accessible, Interoperable, Reusable) principles in many data sources.<\/p>\n<p>One of the most common challenges I have encountered is the lack of knowledge about the data to be integrated. This makes it very difficult to plan timelines for developing an SDI. By \u201cknowledge,\u201d I mean knowing exactly which datasets will be integrated, along with their technical metadata, such as format, size, and frequency of updates.<\/p>\n<p>In an ideal scenario, this information would be provided in a metadata record, preferably in a standardized format. However, in many cases, data comes without metadata, which brings me to the second challenge: the creation of standards-based metadata. As with building a data inventory, this is often less a technical issue and more a human one, as it requires collaboration with data owners.<\/p>\n<p>Another major challenge I have encountered is the format of the data itself, which in many cases is neither standardized nor structured. One of the most common examples I have seen is CSV (Comma-Separated Value) files, which are text files that may contain anything within comma-enclosed fields. For instance, coordinates can be expressed in different formats within the same column. These integration challenges arise from the lack of a mechanism to enforce a schema. Despite these limitations, CSV and Excel files remain among the most commonly used formats for data exchange.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter\" src=\"https:\/\/www.ogc.org\/wp-content\/uploads\/2026\/04\/sdi.png\" alt=\"Standards-based geospatial data integration workflow\" \/><\/p>\n<p>The image above depicts the ideal situation: a dataset is provided in a standards-based format, along with an accompanying metadata record. This allows the data to be more easily ingested into an SDI and published through various OGC API formats, such as <a href=\"https:\/\/www.ogc.org\/standards\/ogcapi-tiles\/\">tiles<\/a>, <a href=\"https:\/\/www.ogc.org\/standards\/ogcapi-features\/\">features<\/a>, or <a href=\"https:\/\/www.ogc.org\/standards\/ogcapi-records\/\">records<\/a>.<\/p>\n<p>In this post, I have highlighted some of the most common challenges. In the coming posts, I will explore each of these challenges in more detail and share some practical strategies that I have developed to address them.<\/p>\n<p>My key takeaway is that while software tools can assist us with these tasks, education remains the most effective way to prevent these challenges in the first place.<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>Data integration is often where geospatial projects slow down. It is a critical step in building a Spatial Data Infrastructure (SDI), and it is often where a great deal of time is spent. This is largely due to the chronic lack of adherence to FAIR (Findable, Accessible, Interoperable, Reusable) principles in many data sources. One [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":9,"featured_media":34751,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_eb_attr":"","footnotes":""},"categories":[190],"tags":[200,484,302,416,1431,1433,1432,329,486,175],"post_author_tag":[930],"class_list":["post-34748","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-article","tag-data-integration","tag-data-interoperability","tag-fair-principles","tag-geospatial-data","tag-geospatial-integration","tag-gis-challenges","tag-metadata-standards","tag-ogc-standards","tag-sdi","tag-spatial-data-infrastructure","post_author_tag-joana-simoes"],"acf":[],"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/posts\/34748","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/comments?post=34748"}],"version-history":[{"count":2,"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/posts\/34748\/revisions"}],"predecessor-version":[{"id":34772,"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/posts\/34748\/revisions\/34772"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/media\/34751"}],"wp:attachment":[{"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/media?parent=34748"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/categories?post=34748"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/tags?post=34748"},{"taxonomy":"post_author_tag","embeddable":true,"href":"https:\/\/www.ogc.org\/wp-json\/wp\/v2\/post_author_tag?post=34748"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}