diff --git a/.vscode/settings.json b/.vscode/settings.json index 2a9f537676..98bcb28573 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -275,6 +275,7 @@ "PMETHOD", "POLYLINE", "polylines", + "postgis", "PRECINCTID", "prepend", "psap", @@ -320,6 +321,7 @@ "SUBDIV", "subprecinct", "subprecincts", + "subsetting", "Sulphurdale", "Sunnyside", "tabindex", diff --git a/src/content/blog/2013-04-02-using-the-mapserv-utah-gov-api-to-geocode-address.mdx b/src/content/blog/2013-04-02-using-the-mapserv-utah-gov-api-to-geocode-address.mdx index d1301a5aa5..1eb7e09ff3 100644 --- a/src/content/blog/2013-04-02-using-the-mapserv-utah-gov-api-to-geocode-address.mdx +++ b/src/content/blog/2013-04-02-using-the-mapserv-utah-gov-api-to-geocode-address.mdx @@ -17,7 +17,7 @@ import Contacts from '@components/page/Contacts.astro'; Geographic coordinates for Utah addresses can now be located using the UGRC's Web API. This is the same API that are used by UGRC web applications. -[![API Explorer](/images/404.png)](https://api.mapserv.utah.gov) +[API Explorer](https://api.mapserv.utah.gov) The geocoding-related endpoints currently include single address geocoding, reverse geocoding, route and milepost lookup. The APIs and their parameters can be viewed and tested using the [API Explorer](https://api.mapserv.utah.gov). diff --git a/src/content/blog/2013-05-10-utah-statewide-address-geocoding-web-service-upgrade.md b/src/content/blog/2013-05-10-utah-statewide-address-geocoding-web-service-upgrade.md index 94580fc2b5..7bfa8757df 100644 --- a/src/content/blog/2013-05-10-utah-statewide-address-geocoding-web-service-upgrade.md +++ b/src/content/blog/2013-05-10-utah-statewide-address-geocoding-web-service-upgrade.md @@ -17,8 +17,6 @@ cover_image_alt: ugrc social card Last week, UGRC finished a substantial upgrade to the Utah statewide address locator (geocoding) web service. This service utilizes point and road-based address map reference data compiled into the State Geographic Information Database (SGID) from local sources, and published on a bi-monthly basis. -[![Geocoding image](/images/404.png)]() - The publicly accessible geocoding service allows developers to include 'best effort' Utah address finding functionality into web applications at no cost. Just as important, this service enables database administrators to build processes that allow any database containing information tied to an address to pick up geographic coordinates so that information can be easily integrated and viewed on mapping platforms. diff --git a/src/content/blog/2016-03-25-about-our-new-v6-website-in-ghpages.mdx b/src/content/blog/2016-03-25-about-our-new-v6-website-in-ghpages.mdx index 5ea08590a8..5ad8e4fa74 100644 --- a/src/content/blog/2016-03-25-about-our-new-v6-website-in-ghpages.mdx +++ b/src/content/blog/2016-03-25-about-our-new-v6-website-in-ghpages.mdx @@ -20,7 +20,7 @@ In releasing the new, updated gis.utah.gov, we feel we have taken logical, evolu The primary driver behind this release was to solve some nagging issues associated with operating a locally-hosted Content Management System (CMS). Our new GitHub Pages ([GH Pages](https://pages.github.com/)) architecture releases us from the ‘upkeep’ that included care and feeding for WordPress, its associated extensions, a relational database (mySQL), dynamic programming interface (PHP), a server OS, and operation and hosting expenses for a virtual machine. GitHub’s **free** hosting policy for openly-sourced content means we are saving real resources that can be applied to other priorities. -[![How Git Works](../../images/pillar-blog/2016-03-25-about-our-new-v6-website-in-ghpages/howgitworkssmall.png)](../../images/pillar-blog/2016-03-25-about-our-new-v6-website-in-ghpages/howgitworks.png) +![How Git Works](../../images/pillar-blog/2016-03-25-about-our-new-v6-website-in-ghpages/howgitworks.png) While, it is true that we are putting our faith in the engineers at GitHub to keep their stack [running for us](https://www.githubstatus.com/), we are not solely in the company of freeloaders. The paid services GitHub provides to their top-tier paying customers (many of the largest software firms in the world, including the most prominent commercial GIS software vendor), should ensure we are in good hands. And since all our pages are static (as opposed to dynamically generated from PHP database calls), we could easily port the site to another cloud platform if we ever find the need. diff --git a/src/content/blog/2016-03-30-3d-elevation-program-proposal.md b/src/content/blog/2016-03-30-3d-elevation-program-proposal.md index a254084783..33a0977517 100644 --- a/src/content/blog/2016-03-30-3d-elevation-program-proposal.md +++ b/src/content/blog/2016-03-30-3d-elevation-program-proposal.md @@ -11,6 +11,4 @@ cover_image: '/src/images/pillar-blog/default-social-card.png' cover_image_alt: ugrc social card --- -[![3D Elevation Program](/images/404.png 'click to enlarge')](/images/404.png) - In October 2015, UGRC, in partnership with local, state, and federal partners submitted a proposal to the U.S. Geological Survey's 3D Elevation Program (3DEP) Grant program. The proposed project will acquire QL1 and QL2 specification Lidar and elevation data in Northern Utah and other areas of interest. UGRC received notice that the proposal has been recommended for funding and the partnership is preparing for a Fall 2016 acquisition. The proposed areas in the graphic are subject to change. diff --git a/src/content/blog/2016-05-24-25th-anniversary-state-geographic-information-database.md b/src/content/blog/2016-05-24-25th-anniversary-state-geographic-information-database.md index 8116c8f87c..1e316c7386 100644 --- a/src/content/blog/2016-05-24-25th-anniversary-state-geographic-information-database.md +++ b/src/content/blog/2016-05-24-25th-anniversary-state-geographic-information-database.md @@ -49,10 +49,10 @@ quantity. One size fits all SGID data stewards and SGID data users alike. Get yours from an UGRC staffer at your next opportunity. Cover of SGID Data CD, 1995 -[Cover, SGID CD, 1995](../../images/pillar-blog/2016-05-24-25th-anniversary-state-geographic-information-database/sgid_cover.jpg) +![Cover, SGID CD, 1995](../../images/pillar-blog/2016-05-24-25th-anniversary-state-geographic-information-database/sgid_cover.jpg) SGID Data CD, 1995 -[Inside, SGID CD, 1995](../../images/pillar-blog/2016-05-24-25th-anniversary-state-geographic-information-database/sgid_cd.jpg) +![Inside, SGID CD, 1995](../../images/pillar-blog/2016-05-24-25th-anniversary-state-geographic-information-database/sgid_cd.jpg) SGID Data User Guide, 1999 -[SGID Data User Guides, 1999](../../images/pillar-blog/2016-05-24-25th-anniversary-state-geographic-information-database/sgid_userguide.jpg) +![SGID Data User Guides, 1999](../../images/pillar-blog/2016-05-24-25th-anniversary-state-geographic-information-database/sgid_userguide.jpg) diff --git a/src/content/blog/2016-08-29-2016-utah-lidar-acquisition.mdx b/src/content/blog/2016-08-29-2016-utah-lidar-acquisition.mdx index 73c4fa7f70..6409fac76c 100644 --- a/src/content/blog/2016-08-29-2016-utah-lidar-acquisition.mdx +++ b/src/content/blog/2016-08-29-2016-utah-lidar-acquisition.mdx @@ -15,7 +15,6 @@ import Contacts from '@components/page/Contacts.astro'; UGRC has awarded [Quantum Spatial Inc. (QSI)](https://quantumspatial.com/) and [Digital Mapping Inc. (DMI)](https://web.archive.org/web/20161001160031/http://admap.com/) to acquire [**3,182 square miles**](https://www.arcgis.com/home/webmap/viewer.html?webmap=817e60a9c3374c95aab76c43876b8673&extent=-117.1875,36.3217,-104.5752,43.2351 'view project areas in ArcGIS Online') of Lidar Elevation data. The Lidar will be a combination of USGS Quality Level 1 (QL1), 8 ppsm and Quality Level 2 (QL2), 2 ppsm depending on the area. The acquisitions will be during leaf-off conditions with the exception of Monroe Mountain project that will be collected leaf-on. The Monroe Mountain acquisition has already started. The rest of the areas will be collected starting mid-October with the exception of the non-vegetated areas of the Great Salt Lake that will start in the coming weeks. The acquisitions and project deliverables are scheduled to be completed by May 31, 2017 (extended to Aug. 31, 2017). -[![Project area map](/images/404.png 'view project area map')](/images/404.png) The project areas include: - Great Salt Lake shoreline and wetlands diff --git a/src/content/blog/2016-08-31-new-2016-google-imagery.mdx b/src/content/blog/2016-08-31-new-2016-google-imagery.mdx index 2f613033bd..8d50e489d0 100644 --- a/src/content/blog/2016-08-31-new-2016-google-imagery.mdx +++ b/src/content/blog/2016-08-31-new-2016-google-imagery.mdx @@ -22,14 +22,12 @@ import Contacts from '@components/page/Contacts.astro'; New 2016 high-resolution Google imagery is available from the Discover server. Updated areas include the Salt Lake Block and part of the Torrey Block that was previously covered by clouds. The new imagery can be found in the `utah` service. The new imagery is not yet available for download and the archive services have not been updated but should be very soon. -[![Google update](/images/404.png 'view sample')](/images/404.png) +![Google update](../../images/pillar-blog/2016-08-31-new-2016-google-imagery/slcoblock.png 'view sample') -[![Google update](../../images/pillar-blog/2016-08-31-new-2016-google-imagery/slcoblock_sm.png 'view sample')](../../images/pillar-blog/2016-08-31-new-2016-google-imagery/slcoblock.png) - -[![Google update](../../images/pillar-blog/2016-08-31-new-2016-google-imagery/torreyblock_sm.png 'view sample')](../../images/pillar-blog/2016-08-31-new-2016-google-imagery/torreyblock.png) +![Google update](../../images/pillar-blog/2016-08-31-new-2016-google-imagery/torreyblock.png 'view sample') ArcMap users may need to clear the cache on the `utah` layer from Discover to see the new imagery. This can be done by going to the service’s `Layer Properties -> Cache` tab and selecting `Clear Local Cache Now`. Be patient as this could take several minutes. -Are you not signed up for access to the Google imagery yet? Visit [the Google Imagery License page](/documentation/discover/licensed-imagery"Google imagery license information"). +Are you not signed up for access to the Google imagery yet? Visit [the Google Imagery License page](/documentation/discover/licensed-imagery 'Google imagery license information'). diff --git a/src/content/blog/2016-10-31-ffsl-launches-new-wildfire-risk-assessment-portal.md b/src/content/blog/2016-10-31-ffsl-launches-new-wildfire-risk-assessment-portal.md index 399846d318..2ffc67b5b8 100644 --- a/src/content/blog/2016-10-31-ffsl-launches-new-wildfire-risk-assessment-portal.md +++ b/src/content/blog/2016-10-31-ffsl-launches-new-wildfire-risk-assessment-portal.md @@ -18,8 +18,6 @@ cover_image_alt: ugrc social card Earlier this summer, The [Utah Division of Forestry, Fire and State Lands](https://www.ffsl.utah.gov/) launched a new Wildfire Risk Assessment Portal (uWRAP) to educate and inform the public and land management professionals. The portal assesses the users location or area of interest and provides general and/or detailed information about the wildfire risks associated with a location or area. -[![uWRAP]\(/images/404.png "Wildfire Risk Assessment Portal")](https://wildfirerisk.utah.gov/) - There is a public and a professional viewer. The public viewer provides unregistered access to the site and gives the user basic information about their location of interest. The professional viewer maintains the same functionality as the public viewer, and adds a few more GIS layers and the ability to build an area of interest multiple ways. Once an area of interest is created, a detailed report of the wildfire threats and risks can be exported as well as a file geodatabase of all the GIS layers used for that area in the WRAP. Please visit [utahwildfirerisk.com](https://wildfirerisk.utah.gov/) to learn more about this new tool. If you are interested in the professional portal for your county, municipality, or other GIS needs, please register for an account and the administrators will get you set up. diff --git a/src/content/blog/2016-12-06-naip-2016-mr-sid-county-mosaics-available.mdx b/src/content/blog/2016-12-06-naip-2016-mr-sid-county-mosaics-available.mdx index 72f4c558b9..1d1fe42988 100644 --- a/src/content/blog/2016-12-06-naip-2016-mr-sid-county-mosaics-available.mdx +++ b/src/content/blog/2016-12-06-naip-2016-mr-sid-county-mosaics-available.mdx @@ -15,7 +15,6 @@ cover_image_alt: ugrc social card import Contacts from '@components/page/Contacts.astro'; -[![NAIP 2016 Sample](/images/404.png 'view project area map')](/images/404.png) The statewide 2016 National Agricultural Imagery Program (NAIP) 1 meter aerial photography is now available. The imagery is currently only available as 3-band diff --git a/src/content/blog/2017-02-21-naip-2016-now-available.mdx b/src/content/blog/2017-02-21-naip-2016-now-available.mdx index d4c89605f4..1498b39a63 100644 --- a/src/content/blog/2017-02-21-naip-2016-now-available.mdx +++ b/src/content/blog/2017-02-21-naip-2016-now-available.mdx @@ -17,6 +17,4 @@ import Contacts from '@components/page/Contacts.astro'; The 2016 National Agricultural Imagery Program (NAIP) aerial photography is now available from the [2016 NAIP 1 Meter Orthophotography](/products/sgid/aerial-photography/naip"go to NAIP 2016 page") page. The imagery was collected in the Summer of 2016 as 4-band imagery however the natural color (RGB) and near infrared (NRG) imagery are two separate services on Discover, _NAIP 2016 RGB_ and _NAIP 2016 NRG_. -[![NAIP Sample](/images/404.png 'click for map')](/images/404.png) - diff --git a/src/content/blog/2017-09-18-new-2017-google-imagery.mdx b/src/content/blog/2017-09-18-new-2017-google-imagery.mdx index 02c611fc03..095738f844 100644 --- a/src/content/blog/2017-09-18-new-2017-google-imagery.mdx +++ b/src/content/blog/2017-09-18-new-2017-google-imagery.mdx @@ -25,8 +25,6 @@ The new imagery is already loaded into the `Google`, `Utah`, `Basemap-Hybrid`, a If you have not signed up for access to the Google imagery visit the [Discover - Imagery and Base Map Server](/products/discover) page for details and to access the links needed to request an account. -[![Google update](/images/404.png '2017 Google Imagery updates - click for larger image')](/images/404.png) - #### Don't see the updated imagery diff --git a/src/content/blog/2017-12-14-3-dep-lidar-proposal-2018.md b/src/content/blog/2017-12-14-3-dep-lidar-proposal-2018.md index 5238831c5a..44a5cb7068 100644 --- a/src/content/blog/2017-12-14-3-dep-lidar-proposal-2018.md +++ b/src/content/blog/2017-12-14-3-dep-lidar-proposal-2018.md @@ -21,7 +21,6 @@ It's important to keep in mind that we're still a month or two away from any pre in advance, in an effort to promote coordination and avoid potential duplication of effort in these areas. The proposed areas break down to the following square mileages by USGS quality levels (QL1 - 8 points per meter | QL2 - 2 points per meter): -[![3DEP Proposal](/images/404.png '2018 3DEP Lidar Proposal A - click for larger image')](/images/404.png) - QL1 - 1,892 - QL2 - 7,018 diff --git a/src/content/blog/2018-05-17-2018-utah-lidar-acquisition.mdx b/src/content/blog/2018-05-17-2018-utah-lidar-acquisition.mdx index 98f0088f7e..de0f45651e 100644 --- a/src/content/blog/2018-05-17-2018-utah-lidar-acquisition.mdx +++ b/src/content/blog/2018-05-17-2018-utah-lidar-acquisition.mdx @@ -30,8 +30,6 @@ Three additional areas in Utah have been added to the 2018 project areas: All three project areas will be acquired as USGS QL1, 8 points per square meter. The acquisition of these areas will be completed in 2018, and project deliverables are scheduled to be completed by August 31, 2019. You are welcome to download the boundaries for all the project areas as a [geodatabase and shapefile](https://drive.google.com/a/utah.gov/uc?id=1BkO7aWhFARM-U--KGi4Wn3diNIx7kban&export=download). -[![Project area map](/images/404.png 'view project area map')](/images/404.png) - #### UPDATE 7/17/2019 With the exception of the Unitah Basin / Heber Valley project, managed through the USGS Geospatial Product and Service Contracts (GPSC), all other 2018 project areas are completed and available for download. The Unitah Basin / Heber Valley project should be completed and delivered soon. All other 2018 projects are available from [Raster.utah.gov](https://raster.utah.gov/). Below are links to the individual web pages for each project. diff --git a/src/content/blog/2018-12-18-creating-new-state-plane-zone-for-2022.mdx b/src/content/blog/2018-12-18-creating-new-state-plane-zone-for-2022.mdx index 2a10beeade..5201614e09 100644 --- a/src/content/blog/2018-12-18-creating-new-state-plane-zone-for-2022.mdx +++ b/src/content/blog/2018-12-18-creating-new-state-plane-zone-for-2022.mdx @@ -17,7 +17,7 @@ import Contacts from '@components/page/Contacts.astro'; In 2022 the NGS plans to publish a series of new horizontal reference frames that will replace the NAD83 and a vertical reference frame that will replace the NAVD88. -[![Preliminary zone layout](../../images/pillar-blog/2018-12-18-creating-new-state-plane-zone-for-2022/preliminary_zone_layout_thumb.png)) +![Preliminary zone layout](../../images/pillar-blog/2018-12-18-creating-new-state-plane-zone-for-2022/preliminary_zone_layout_thumb.png) The new horizontal reference frames are the: diff --git a/src/content/blog/2018-12-19-new-2018-google-imagery.mdx b/src/content/blog/2018-12-19-new-2018-google-imagery.mdx index 637770ed90..7144d4b4ea 100644 --- a/src/content/blog/2018-12-19-new-2018-google-imagery.mdx +++ b/src/content/blog/2018-12-19-new-2018-google-imagery.mdx @@ -18,8 +18,6 @@ import Contacts from '@components/page/Contacts.astro'; The new 2018 high-resolution Google imagery (6" pixels) is available through UGRC's [Discover server](/products/discover)[^1]! Updated areas (map below) include what Google calls the "Salt Lake and Logan blocks," which make up most of the Wasatch Front urban area (i.e., Brigham City, Weber County, Davis County, Salt Lake County, and Utah County). The Salt Lake block was flown 9/11/2018 and the Logan block was flown 9/15/2018. -[![Google update](/images/404.png '2018 Google imagery updates - click for larger image')](/images/404.png) - The new imagery is already loaded into the `Google`, `Utah`, `Basemap-Hybrid`, and `Google 2018archive` services. If you are using these services, you do not need to change anything layer-wise, but you may need to clear your cache (instructions below). The new imagery is also available for download as georeferenced jpeg files (.jp2) by all organizations that have signed up to use the licensed content on the Discover server. If you have not signed up for access to the Google imagery, visit the [Discover - Imagery and Base Map Server](/products/discover) page for details and to access the links needed to request an account. diff --git a/src/content/blog/2019-01-17-naip-2018-mr-sid-county-mosaics-available.md b/src/content/blog/2019-01-17-naip-2018-mr-sid-county-mosaics-available.md index 6860dc2bd0..eba546e6bd 100644 --- a/src/content/blog/2019-01-17-naip-2018-mr-sid-county-mosaics-available.md +++ b/src/content/blog/2019-01-17-naip-2018-mr-sid-county-mosaics-available.md @@ -15,8 +15,6 @@ cover_image_alt: ugrc social card The statewide 2018 National Agricultural Imagery Program (NAIP) aerial photography is now available. This year the imagery is higher resolution .6 meter (60 centimeter) imagery compared to 1 meter resolution in previous years. The imagery is currently only available as 3-band Natural Color (RGB) and 3-band Color Infrared (CIR) Mr. Sid compressed county mosaics. The 4-band GeoTIFF or JP2 tiles should be available in a couple of months with statewide imagery services soon to follow. -[![NAIP Sample](/images/404.png 'click to enlarge')](/images/404.png) - The files can be downloaded from [Raster.utah.gov]() or from the following links. The dates the imagery was collected can be found in the shapefile associate with each download. - Beaver [Natural Color (RGB)](https://storage.googleapis.com/state-of-utah-sgid-downloads/aerial-photography/naip/naip2018/NAIP2018_Beaver_RGB.zip) [Color Infrared (CIR)](https://storage.googleapis.com/state-of-utah-sgid-downloads/aerial-photography/naip/naip2018/color-infrared/NAIP2018_Beaver_CIR.zip) diff --git a/src/content/blog/2019-06-11-sgid-then-and-now.md b/src/content/blog/2019-06-11-sgid-then-and-now.mdx similarity index 97% rename from src/content/blog/2019-06-11-sgid-then-and-now.md rename to src/content/blog/2019-06-11-sgid-then-and-now.mdx index 85ad9be9a3..78b632803b 100644 --- a/src/content/blog/2019-06-11-sgid-then-and-now.md +++ b/src/content/blog/2019-06-11-sgid-then-and-now.mdx @@ -14,6 +14,9 @@ cover_image: /src/images/pillar-blog/2019-06-11-sgid-then-and-now/sgid_1994_bind cover_image_alt: 1994 SGID User Guide Binder --- +import { Image } from 'astro:assets'; +import customMapPhoto from '../../images/pillar-blog/2019-06-11-sgid-then-and-now/sgid_early2000s_create_custom_map.gif'; + Access to high-quality GIS data is a privilege, and the fact that it's open and free is nothing short of amazing. Yes, I’m talking about Utah's SGID. From a local perspective, we’re all accustomed to it being there. But really, the concept of readily available, mature, open data is somewhat unique. Over the years, many factors have played into the SGID’s development and current maturity, and it takes ongoing maintenance and planning to ensure its continued success. This post explores some of the early milestones ("highlights") of the SGID, the current state of the SGID with usage stats, and, finally, where we are going next--with a poll requesting user input! @@ -54,7 +57,7 @@ Here are a few of the highlights that have brought the SGID to where it is now: ![1999 SGID User Guide Binder](../../images/pillar-blog/2019-06-11-sgid-then-and-now/sgid_1999_binders_cover_sm.png) - **SGID Meets the World Wide Web (Early 2000s)** - - By the early 2000s the SGID user guide, data, and data viewer were all solely available over the Web. AGRC was using ArcSDE 8.2 to maintain the data and ArcIMS for the interactive mapping website. Users could also use a separate ArcIMS site to create their own exportable map using a [custom map authoring tool](../../images/pillar-blog/2019-06-11-sgid-then-and-now/sgid_early2000s_create_custom_map.gif). + - By the early 2000s the SGID user guide, data, and data viewer were all solely available over the Web. AGRC was using ArcSDE 8.2 to maintain the data and ArcIMS for the interactive mapping website. Users could also use a separate ArcIMS site to create their own exportable map using a custom map authoring tool. ![SGID Early 2000s](../../images/pillar-blog/2019-06-11-sgid-then-and-now/sgid_early2000s_sm.png) diff --git a/src/content/blog/2019-11-04-3-dep-lidar-proposal-2020.md b/src/content/blog/2019-11-04-3-dep-lidar-proposal-2020.md index 5778e80906..95488fb00f 100644 --- a/src/content/blog/2019-11-04-3-dep-lidar-proposal-2020.md +++ b/src/content/blog/2019-11-04-3-dep-lidar-proposal-2020.md @@ -19,7 +19,6 @@ While we're months away from any preliminary or final funding decisions, the par in advance in an effort to promote coordination between the partners and avoid duplication of effort in these project areas. The proposed areas have the following square mileage: -[![3DEP Proposal](/images/404.png '2020 3DEP Lidar Proposal A - click for larger image')](/images/404.png) Projects Already Underway diff --git a/src/content/blog/2020-05-27-bike-related-gis-data-resources.md b/src/content/blog/2020-05-27-bike-related-gis-data-resources.md index c792dcdb76..4255406f40 100644 --- a/src/content/blog/2020-05-27-bike-related-gis-data-resources.md +++ b/src/content/blog/2020-05-27-bike-related-gis-data-resources.md @@ -23,14 +23,12 @@ The goal of the regional, and eventually statewide, bike datasets assembled by U So, if you’ve got an interest or use for GIS bike data, here are some of the latest developments that you are invited to explore. Keep in mind that we are hoping that these datasets will continue to improve and stay current, so please consider how you might share feedback or data updates or otherwise help improve these processes and data products. - **Existing On-street Bike Lanes and Near-street Bike Paths.** Thanks to work being done by UDOT Traffic and Safety and UDOT Planning staff, the existing bike facility attributes stored within [Utah’s statewide road centerline GIS dataset](/products/sgid/transportation/road-centerlines) have been revised to the most up-to-date 2018 aerial photography. Initial work for the Wasatch Front metro area (i.e., Salt Lake, Utah, Davis, Weber, and southern Box Elder counties) has been completed and is now available in the May 2020 road centerline update available from UGRC. Attributes are stored in the `Bike_L` and `Bike_R` fields using a [coded-value domain](https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=2110432100). UDOT plans to complete the photo revision of road-based bike facilities for other areas of the state in upcoming months. - [![Existing Bike Features](/images/404.png 'click to enlarge')](/images/404.png) - **Existing and Planned Off-street Bike Paths.** [Utah’s Recreation.Trails dataset](/products/sgid/recreation/trails-pathways), hosted by UGRC, contains known off-street bike paths like the Jordan River Parkway. Paved trails can be queried from this dataset by using this SQL expression: `[CARTOCODE] = 3 and not [STATUS] = “PROPOSED”` - **Planned Bike Lanes and Pathways for the WFRC Area.** WFRC staff have worked to integrate local and regional bike facility plans into the UGRC-hosted road centerline and trails datasets for (Salt Lake, Davis, Weber, and southern Box Elder counties). In the road centerline dataset, the planned facilities are stored in the `BIKE_PLN_L` and `BIKE_PLN_R` fields using the same coded-value domain noted above. WFRC has coordinated with UGRC to add planned off-street pathways for the same area. They can be found by querying Recreation.Trails with this SQL expression: `[CARTOCODE] = 3 and [STATUS] = “PROPOSED”` - **WFRC-area Bike Plan Areas.** WFRC has created a polygon dataset with links to recent local completed and in-progress bike plans. This dataset is featured in an interactive map on [BikeUtah’s webpage](https://www.bikeutah.org/wbp) and has links to local plan documents. - **Multimodal Network.** The new [Multimodal Network Dataset](/products/sgid/transportation/street-network) allows shortest-path and travel shed calculations using roads and trails with built-in bike, pedestrian, transit, and vehicle travel cost (impedance) values. This dataset will be updated periodically to reflect road attribute and trail updates. The [process for creating this dataset](https://docs.google.com/document/d/1OsXexJTap9tDY89Y_v2woGatK_u5nYd_jDdlMwWRhog/edit) was developed by UDOT and UGRC through an [FHWA funded project](/blog/2018-11-07-multi-modal-travel-shed-analysis-project). Other bike-related information resources that are _coming soon_ (i.e., over the next few months): -[![Planned Bike Features](/images/404.png 'click to enlarge')](/images/404.png) - **Wasatch Front Bike and Pedestrian Demand Score.** This is an update of the 2013 UCATS “Latent Demand” methodology that assigned a variety of demand-related indicators to the road network. [This dataset](http://wfrc.maps.arcgis.com/home/webmap/viewer.html?webmap=8ca837a9d3ff4b1299468e40b3eac383) will incorporate new and updated GIS data and will be published as a stand-alone layer that uses the road centerline geometry. Future enhancements building on this methodology are also planned by WFRC and partners. - **Network Quality.** Metrics for nearby bike network quality implemented by UDOT and UGRC will also soon be available for the Wasatch Front metro area, Bike Data Resources Webmap. This integrated web map application allows all of the above datasets to be explored and downloaded for the Wasatch Front metro area. diff --git a/src/content/blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools.md b/src/content/blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools.md index 6a22402ade..9db941a6d2 100644 --- a/src/content/blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools.md +++ b/src/content/blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools.md @@ -20,7 +20,7 @@ The accompanying Python Notebook for this blog post can be found [here on Google ### The Open SGID -The introduction of the [Open SGID](https://gis.utah.gov/introducing-open-sgid/) has opened the door for new ways to explore Utah's GIS data. Before the Open SGID, a user would typically have gone to the UGRC web page to find the data they were looking for and download it in shapefile or file geodatabase format. This can still be done today, but now that UGRC has leveraged the [Open Data](https://opendata.gis.utah.gov/) platform, there are more options for users to access geospatial data in their preferred way. Data can now be streamed to clients via web services or can be downloaded in even more formats (e.g., GeoJSON, KML, and CSV). But the recently launched Open SGID is an especially valuable resource because it is a cloud-hosted PostgreSQL PostGIS database that anyone can connect to. As the Open SGID has nightly automated updates, tapping into the Open SGID means you'll have a living connection to the freshest SGID data available. +The introduction of the [Open SGID](https://gis.utah.gov/blog/2020-05-04-introducing-open-sgid) has opened the door for new ways to explore Utah's GIS data. Before the Open SGID, a user would typically have gone to the UGRC web page to find the data they were looking for and download it in shapefile or file geodatabase format. This can still be done today, but now that UGRC has leveraged the [SGID on ArcGIS](https://opendata.gis.utah.gov/) platform, there are more options for users to access geospatial data in their preferred way. Data can now be streamed to clients via web services or can be downloaded in even more formats (e.g., GeoJSON, KML, and CSV). But the recently launched Open SGID is an especially valuable resource because it is a cloud-hosted PostgreSQL PostGIS database that anyone can connect to. As the Open SGID has nightly automated updates, tapping into the Open SGID means you'll have a living connection to the freshest SGID data available. The Open SGID also creates an opportunity for users to pull in data and perform analysis using open source software and libraries-like Python. With this route, you don't need to worry about paying for licensed software or even installing GIS desktop software at all. And if you use a cloud-hosted Jupyter notebook—like Google Colab—you don't even have to install Python on your computer (or tablet or chromebook)! @@ -73,7 +73,7 @@ counties = gpd.GeoDataFrame.from_postgis(sql, con, geom_col='shape') counties.plot(figsize=(10, 6), color='white', edgecolor='black') ``` -[![Utah County Boundaries](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_counties_plot.png 'Utah County Boundaries')](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_counties_plot.png) +![Utah County Boundaries](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_counties_plot.png 'Utah County Boundaries') ### EXAMPLE 2: Davis County Address Points by Zip Code @@ -104,7 +104,7 @@ plt.title('Davis County Address Points') plt.show() ``` -[![Davis County Address Points](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_addpts_plot.png 'Davis County Address Points')](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_addpts_plot.png) +![Davis County Address Points](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_addpts_plot.png 'Davis County Address Points') ### EXAMPLE 3: Utah Faults Longer than One Mile @@ -133,11 +133,11 @@ plt.title('Utah Faults > 1 Mile') plt.show() ``` -[![Utah Faults > 1 Mile](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_faults_plot.png 'Utah Faults > 1 Mile')](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_faults_plot.png) +![Utah Faults > 1 Mile](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_faults_plot.png 'Utah Faults > 1 Mile') ## EXAMPLE 4: Libraries in State Senate District 24 -For this fourth example, you'll plot public libraries within State Senate District 24 by using a spatial operation, which is really where GeoPandas shines and sets itself apart from nonspatial tools. +For this fourth example, you'll plot public libraries within State Senate District 24 by using a spatial operation, which is really where GeoPandas shines and sets itself apart from non-spatial tools. 1. Start by selecting the data layers (hopefully the syntax is getting familiar now) with SQL queries and importing them with GeoPandas. 1. Next, subset the senate districts down to just district 24 using Pandas square bracket `[]` notation. @@ -165,7 +165,7 @@ plt.title('Libraries in Utah Senate District 24') plt.show() ``` -[![Libraries in Utah Senate District 24](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_libraries_plot.png 'Libraries in Utah Senate District 24')](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_libraries_plot.png) +![Libraries in Utah Senate District 24](../../images/pillar-blog/2020-05-28-exploring-the-open-sgid-with-open-source-python-tools/emn_20200526_libraries_plot.png 'Libraries in Utah Senate District 24') That's it! This brief tutorial has shown a few different ways to gather and analyze data from the Open SGID with the psycopg2 and GeoPandas libraries. Hopefully it was helpful and will spark your interest in both the Open SGID and using open source Python tools. diff --git a/src/content/blog/2021-04-26-introducing-ugrcodes.mdx b/src/content/blog/2021-04-26-introducing-ugrcodes.mdx index f673c01ab6..ac4d786295 100644 --- a/src/content/blog/2021-04-26-introducing-ugrcodes.mdx +++ b/src/content/blog/2021-04-26-introducing-ugrcodes.mdx @@ -15,7 +15,7 @@ import Contacts from '@components/page/Contacts.astro'; Are you tired of fighting with esoteric municipal FIPS codes? Have you even tried using them? It's not easy and it's certainly not intuitive. Five digit integer codes with minimal consistency and continuity across space, and require a lookup table to understand, don't lend themselves as a simple identifier for a municipality. As a solution, UGRC is implementing a new attribute field called the UGRCode (get it?) in our [Municipal Boundaries](https://opendata.gis.utah.gov/datasets/utah-municipal-boundaries) and [Metro Townships](https://opendata.gis.utah.gov/datasets/utah-metro-townships) data. The full list of UGRCodes can be found [in this spreadsheet](https://docs.google.com/spreadsheets/d/19cwbXoewTynDDv_fJ3hGekD4VbLef5VxrnSJfRx8My8/edit#gid=2028111876). -[![UGRCodes in Salt Lake County](../../images/pillar-blog/2021-04-26-introducing-ugrcodes/20210422_ugrcodes.png 'UGRCodes in Salt Lake County')](../../images/pillar-blog/2021-04-26-introducing-ugrcodes/20210422_ugrcodes.png) +![UGRCodes in Salt Lake County](../../images/pillar-blog/2021-04-26-introducing-ugrcodes/20210422_ugrcodes.png 'UGRCodes in Salt Lake County') Inspired by a suggestion from one of our colleagues at the Wasatch Front Regional Council, we believe these codes provide several advantages that make them more useful and easier to use than FIPS codes or municipality names for uniquely identifying municipalities in Utah. They also [support our efforts](https://docs.google.com/document/d/12bdtmtv-ZVF9g-lFshbobx8DbKX9LfbL44HawLjFTVw/edit) to ensure that attribute domain values match their corresponding descriptions within our datasets. Some advantages of the UGRCodes are: diff --git a/src/content/blog/2021-11-23-voter-counts-tool-release.mdx b/src/content/blog/2021-11-23-voter-counts-tool-release.mdx index 2769606c05..a89240d039 100644 --- a/src/content/blog/2021-11-23-voter-counts-tool-release.mdx +++ b/src/content/blog/2021-11-23-voter-counts-tool-release.mdx @@ -18,16 +18,12 @@ import Contacts from '@components/page/Contacts.astro'; Utah's [statewide election districts](https://opendata.gis.utah.gov/search?q=election) have been released and many local governments are now in the process of redrawing their precincts to accommodate the changes and manage their upcoming elections. To help facilitate these "precincting" efforts, UGRC has created an ArcGIS Pro tool that counts up the number of actively registered voters within a given polygon layer. The primary use case for the tool is to help counties adjust precinct boundaries to optimize the number of voters within their precincts. The tool can be run iteratively as precinct boundaries are adjusted to update voter counts and guide further adjustments. The Python Script Tool resides within an ArcGIS Pro Toolbox that can be installed and run locally from your desktop computer. -[![Voter Counts in Precincts](/images/404.png 'Voter Counts in Precincts')](/images/404.png) - _Precincts with voter counts labeled_ Behind the scenes, the tool grabs voter count totals from a voter points layer in ArcGIS Online (AGOL). This data has access restrictions placed on it, so only specific AGOL users or groups that have been granted permission, can access it. This means that the user must be logged into AGOL from ArcGIS Pro in order for the tool to work correctly and to have access granted to the voter points layer. The ArcGIS Pro Toolbox can be [downloaded](https://drive.google.com/file/d/1i9OZdYVBkDs-EeFu9JItVTk8rNCs1K0M/view?usp=sharing) by anyone and a [user guide](https://docs.google.com/document/d/1BG-FPROoZkfsoAScDLLSvHGMLuFucdlzaJRILp33rSk) has been created with information on installing and using the tool. Additionally, we recorded a [UGRC Voting Tools](https://drive.google.com/file/d/1i6ZIwuJjlA0MXdaIxbQcsvUO8nTrkFqe/view) Webinar earlier this year that demonstrates the voter counts tool and data validation checks done by UGRC. -[![Voter Counts Tool](/images/404.png 'Voter Counts Tool')](/images/404.png) - If you're interested in using the voter counts tool to help with redrawing your precincts, please reach out to us and we can help set you up. diff --git a/src/content/blog/2022-04-11-utah-lidar-coverage-application.mdx b/src/content/blog/2022-04-11-utah-lidar-coverage-application.mdx index 5d728ad2ef..693273e742 100644 --- a/src/content/blog/2022-04-11-utah-lidar-coverage-application.mdx +++ b/src/content/blog/2022-04-11-utah-lidar-coverage-application.mdx @@ -22,6 +22,6 @@ To accompany our [web pages of Lidar projects](/products/sgid/elevation) and dow _**Please note:** The proposed project footprints can change frequently and will be updated as we receive more information._ -[![Lidar Coverage Application](/images/404.png 'Lidar Coverage Application')](https://arcg.is/18SWjy) +[Lidar Coverage Application](https://arcg.is/18SWjy) Have questions? Reach out to .