<commit_before>---
title: Introducing the Open SGID Database - A new publicly available data offering
author:
  display_name: <NAME>
  email: <EMAIL>
date: 2020-04-30 16:30:00
categories:
  - Featured
tags:
  - SGID
  - open source
  - cloud
  - data
---

It seems so long ago now, but it was less than a year ago when we first [hinted at the possibility]({% link _posts/2019-06-11-sgid-then-and-now.md %}#where-is-the-sgid-going) of a new SGID offering ([then again last fall]({% link _posts/2019-11-12-sgid-product-relaunch-update.md %}#potential-google-cloud-managed-postgis)). We are finally ready to announce the debut of a new open source SGID database - the Open SGID - a cloud-hosted PostgreSQL PostGIS database.

<p align="center">Database Platform: PostgresSQL</p>
<p align="center">Instance: opensgid.agrc.utah.gov</p>
<p align="center">Username: agrc</p>
<p align="center">Password: <PASSWORD></p>

The timing could not be more perfect with the sudden increase in teleworking, which is not expected to wane any time soon, especially here in Utah with the implementation of the [Governor’s teleworking initiative](https://governor.utah.gov/2019/07/16/state-of-utah-introduces-teleworking-program-for-employees/). Not only does the Open SGID benefit Utahns, but it also signals the return to a truly publicly-available, direct database connection that can be utilized on a multitude of GIS platforms. Furthermore, it initiates the sunsetting of the state network-only SGID10 database, although both databases (Open SGID and SGID10) will run in parallel for some time to allow users to make the transition to the Open SGID and adapt to the change.

The new tools and processes developed collectively by AGRC staff to accomplish the Open SGID, as well as the new and improved [Open Data site](https://opendata.gis.utah.gov/), are numerous and worthy of their own blogpost - perhaps some foreshadowing there. However, it is worth noting that a paradigm shift led to the creation of a new internal SGID database that serves as the sole editing environment and data source for the Open SGID and the Open Data site. Automated processes provide nightly updates to both data resources to maintain consistency between them, so you can be sure that you are utilizing the most current data available.

A nearly month-long beta testing period was helpful to identify several issues and some inherent differences between the Open SGID and the enterprise geodatabase of the SGID10 era. A [GitHub repository](https://github.com/agrc/open-sgid) was created as the primary source of information for the Open SGID, and to catalog and address [these issues and differences](https://github.com/agrc/open-sgid/issues) with explanations or troubleshooting techniques.

Known issues:<commit_msg>fix: one post link and font matter section<commit_after>---
title: Introducing the Open SGID Database - A new publicly available data offering
author.display_name: <NAME>
author.email: <EMAIL>
date: 2020-05-04
tags:
  - SGID
  - open source
  - cloud
  - data
  categories:
  - Featured
---

It seems so long ago now, but it was less than a year ago when we first [hinted at the possibility]({% link _posts/2019-06-11-sgid-then-and-now.md %}#where-is-the-sgid-going) of a new SGID offering [(then again last fall)]({% link _posts/2019-11-12-sgid-product-relaunch-update.md %}#potential-google-cloud-managed-postgis). We are finally ready to announce the debut of a new open source SGID database - the Open SGID - a cloud-hosted PostgreSQL PostGIS database.

<p align="center">Database Platform: PostgresSQL</p>
<p align="center">Instance: opensgid.agrc.utah.gov</p>
<p align="center">Username: agrc</p>
<p align="center">Password: <PASSWORD></p>

The timing could not be more perfect with the sudden increase in teleworking, which is not expected to wane any time soon, especially here in Utah with the implementation of the [Governor’s teleworking initiative](https://governor.utah.gov/2019/07/16/state-of-utah-introduces-teleworking-program-for-employees/). Not only does the Open SGID benefit Utahns, but it also signals the return to a truly publicly-available, direct database connection that can be utilized on a multitude of GIS platforms. Furthermore, it initiates the sunsetting of the state network-only SGID10 database, although both databases (Open SGID and SGID10) will run in parallel for some time to allow users to make the transition to the Open SGID and adapt to the change.

The new tools and processes developed collectively by AGRC staff to accomplish the Open SGID, as well as the new and improved [Open Data site](https://opendata.gis.utah.gov/), are numerous and worthy of their own blogpost - perhaps some foreshadowing there. However, it is worth noting that a paradigm shift led to the creation of a new internal SGID database that serves as the sole editing environment and data source for the Open SGID and the Open Data site. Automated processes provide nightly updates to both data resources to maintain consistency between them, so you can be sure that you are utilizing the most current data available.

A nearly month-long beta testing period was helpful to identify several issues and some inherent differences between the Open SGID and the enterprise geodatabase of the SGID10 era. A [GitHub repository](https://github.com/agrc/open-sgid) was created as the primary source of information for the Open SGID, and to catalog and address [these issues and differences](https://github.com/agrc/open-sgid/issues) with explanations or troubleshooting techniques.

Known issues:
{'fraction_non_alphanumeric': 0.07265569076592698, 'fraction_numerical': 0.01467430207587688, 'mean_word_length': 4.61144578313253, 'pattern_counts': {'":': 0, '<': 25, '<?xml version=': 0, '>': 25, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5000214', 'n_tokens_mistral': 1598, 'n_tokens_neox': 1469, 'n_words': 742}