Git Product home page Git Product logo

porter's Introduction

Porter

A porter is person that

  • carries things, such as bags
  • performs routine cleaning, likely on a train, taking care of the sleeping berths.

UGRC tracks the additions, replacements, and deletions of SGID items (in the broadest sense of add, replace, or delete) through issues in this repository.

How to use

  1. Create a new issue when an application, dataset, or both needs to be added, deleted, or moved to a different long-term storage
  2. Choose the Removing Data From Anywhere (for moving or deleting data) or Introduce data to the SGID (for adding data) template from the buttons
  3. Tag the three triagers (one from each team) in the triage section:
    • Data Team Triage (@gregbunce)
  4. The triagers will choose which items need to be handled and tag the appropriate people to handle them:
    • ArcGIS Online (@jacobdadams)
    • Items that don't need to be handled should be struck through (wrap the line with ~'s) instead of being deleted:
      • ~ArcGISOnline (assigned to)~ (note there are no spaces between the ~'s and the text to be struck out)
    • Once the triager has identified any steps required for their team or made any relevant comments, they should check the box in the triage section to indicate that their triage is complete:
      • Data Team Triage (@gregbunce)
  5. The people assigned to different issues will check the boxes as they are completed and comment on the issue to notify the rest of the group:
    • ArcGIS Online (@jacobdadams)
  6. Once all boxes are checked, the person who first opened the issue should close it.

Data Flow for New SGID Datasets

If there is a record added to SGID.META.AGOLItems, the corresponding dataset will automatically be added to:

  1. the open sgid with cloudb
  2. arcgis online with forklift
  3. open data with the agol validator

Note: cloudb is the only automation from the list above that works in reverse. If a record is removed from SGID.META.AGOLItems, the corresponding data needs to be manually removed from all of the systems above with the exception of the Open SGID.

Tweet templates

intent to deprecate

🚮🗑️🚮 Deprecation Notice 🚮🗑️🚮

[Dataset]

https://github.com/agrc/porter/issues/#

#utmap #ugrcporter

issue completed

🚮🗑️🚮 Deprecation Complete 🚮🗑️🚮

[Dataset]

https://github.com/agrc/porter/issues/#

#utmap #ugrcporter

intent to add

🌱🌱The SGID is growing🌳🌳

Dataset from Agency coming soon!

https://github.com/agrc/porter/issues/#

Follow along and comment if you are interested!

#utmap #ugrcporter

addition complete

🌱🌱The SGID has grown🌳🌳

Dataset from Agency is live in the SGID!

https://github.com/agrc/porter/issues/#

#utmap #ugrcporter

porter's People

Contributors

dependabot[bot] avatar eneemann avatar gregbunce avatar jacobdadams avatar nathankota avatar rkelson avatar stdavis avatar steveoh avatar ugrc-release-bot[bot] avatar

Stargazers

avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

porter's Issues

Old AGOL Items: Scott

I've found the following items in AGOL that are owned by you that look old, unused, and/or broken. Please take a look at them and see if they can be deprecated/deleted. If they are part of the SGID or some other major project, consider opening a new issue using the full deprecation checklist/process.

I don't mean to call anyone out for their old data. I just wanted to have a place to track these things as I found them as part of the HTTP/HTTPS update process.

This will be a living issue while we track down http links. The list may be edited from time to time.

Create labels for extra context

Describe the problem you are having

I think labels could help give context to the state of an open issue.

For additions something like...

  • intending to add
  • added
  • waiting for propagation
  • waiting for validation
  • validated

We could do something similar with removals.

I wonder if you think this would be too much ceremony or if it would be helpful.

Deprecate old VISTA! (mapserv.utah.gov/havaaddressfix)

mapserv.utah.gov/havaaddressfix is being deprecated in favor of mapserv.utah.gov/vista.

Identify places where the data lives

  • Mapserv (sd)
    • Action taken (sd)
      - Removed VistaBallotAreas and VistaBallotAreas_Proposed from political_utm.gdb.
      - Removed boundaries_utm.gdb
      - Removed cadastre_utm.gdb
      - Removed location_utm.gdb

Is there a website?

  • Is the source code on GitHub? yes (https://github.com/agrc/vista/tree/3.x) (sd)
  • Should it be archived? No, because the repo also houses the newer version of this app (mapserv.utah.gov/vista). (sd)
  • Should it be removed from the web server or show a static page with information? N/A
    • Action take: none (sd)

Is there a map service?

  • Should it be stopped or deleted? deleted (sd)
    • Action taken: mapserv.utah.gov/arcgis/rest/services/Hava has been deleted. (sd)

Is there a forklift pallet?

Are there service dependencies?

  • Does the web api query it? no (sg)
    • Action taken: none (sg)
  • Do AGRC or applications widgets reference it? no (sg)
    • Action taken: none (sg)

Add Schools_PreK_12 from WFRC data

Summary

WFRC has taken the time to download, geocode, and QAQC new schools data from the State Office of Education. This data will replace the existing schools data in the SGID. Higher Ed locations will need to be exported from the existing schools data and moved into their own data set.

  • Proposed Dataset Name: Schools_PreKto12
  • Proposed ISO Category: Society
  • Data Description: pre school and K-12 locations
  • Source Agency/Entity: State Office of Education
  • Contact: SOE
  • Update Frequency: Yearly

Triage

  • Data Team Triage Complete
  • Dev Team Triage Complete (@steveoh )
  • Cadastre Team Triage Complete

We are introducing data

The data was or will be added on 2020/08/20 to the following areas

  • Internal SGID
  • SGID10
  • ArcGIS Online

The data is high quality

  • Sweeper checks have run and passed
  • The minimum requirements for metadata are populated
  • The data complies with our domain rules

The data should propagate automatically to

  • ArcGIS Online
  • SGID10
  • Open SGID
  • Open data
  • SGID.META.ChangeDetection

References to the data need to be manually added to

We have verified the data is live

Notification

Add Utah Quaternary Faults from UGS replacing existing faults in AGOL

Summary

UGS Utah Quaternary Faults are to be shared with the AGOL Geoscience group. This shared feature layer will replace the exiting AGRC version of Quaternary Faults in AGOL and will need to be pulled into SDE as well

  • Proposed Dataset Name: Quaternary Faults
  • Proposed ArcGIS Online Name: Utah Quaternary Faults
  • Proposed ISO Category: Geoscience
  • Data Description: Quaternary faults in Utah
  • Source Agency/Entity: UGS
  • Contact: Gordon Douglass
  • Update Frequency: As needed

Triage

We are introducing data

The data was or will be added on 2020/11/09 to the following areas

  • Internal SGID
  • [ ] SGID10
  • ArcGIS Online

The data is high quality

  • Sweeper checks have run and passed (on their service, prior to coming into internal) (@gregbunce)
  • The minimum requirements for metadata are populated
  • The data complies with our domain rules

The data should propagate automatically to

  • Internal via Forklift (@stdavis)
  • [ ] ArcGIS Online
  • [ ] SGID10
  • Open SGID
  • Open data
  • SGID.META.ChangeDetection

References to the data need to be manually added to

We have verified the data is live

Notification

Remove Trails from SGID

Summary

We are deprecating this layer and replacing it with a new and improved version called "TrailsAndPathways". I will put in a separate issue to add that layer.

Triage

Remove data from the following areas

  • ArcGIS Online (@jacobdadams)
  • Internal SGID (@gregbunce on 7/15/2020)
  • SGID10 (@gregbunce on 7/15/2020)
  • Open SGID (@steveoh)
    - [ ] Google Drive (I think I'll hold off on this for now. this source provides access to older versions of the data. might be worth holding on to all sgid google drive data for future analysis. just thinking out loud).
  • Open data (@jacobdadams)
    - [ ] Mapserv (assigned to)
  • Backseat Driver (@stdavis)

Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (new layer contains all features in this layer)
- [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (new layer contains all features in this layer)
- [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (@jacobdadams)

Update information in the following areas

  • gis.utah.gov data pages (@gregbunce )
  • Stewardship doc and sgid-index (@gregbunce )
  • SGID.META.AGOLItems (@gregbunce on 7/15/2020)
    - [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL)
  • SGID.META.ChangeDetection (@stdavis)

Is there a website?

- [ ] Archive source code repository (assigned to)
- [ ] Remove from the web server (assigned to)
or
- [ ] Replace app with a static page with information (assigned to)
or
- [ ] Redirect somewhere else (assigned to)

Is there a map service?

- [ ] Stop (assigned to)
- [ ] Delete (assigned to)

Is there a forklift pallet?

- [ ] Remove repo (assigned to)

  • Remove stale data from forklift hashing and receiving (@stdavis)

Are there service dependencies?

  • Validate that the web api does not query it (@steveoh )
  • Validate that AGRC or applications widgets do not reference it (@stdavis)

Notification

Deprecate Preservation Pro

Summary

Preservation pro runs on an ArcGIS Server machine GRGS01SPR . I believe it also has a DB associated with it. I do not believe the data has been updated by UDSH staff forever, as they are migrating away from it. It is now time to shut it down and delete all things associated with it. Today, April 13 2020 UDSH staff are confirming, that they have all the information they need from the system. Once I hear back from UDSH, and the machine is shutdown, then I will lay out a schedule for destruction.

Remove data from the following areas

  • ArcGIS Online (sg - no data)
  • Internal SGID (sd - no data)
  • SGID10 (sd - no data)
  • Open SGID (sg - no data)
  • Google Drive (sd - removed from backseat driver)
  • Open data (sg - data)
  • Mapserv (sd - no data, service was pointed directly at database)
  • gis.utah.gov data pages (sd - no data)
  • Stewardship doc and sgid-index (sd)
  • SGID.META.AGOLItems (sd - not there)
  • SGID.META.ChangeDetection (sd)

Is there a website?

  • Archive source code repository (sg - managed externally)
  • Remove from the web server (sg - machine was removed)
    or
  • Replace app with a static page with information (sg - machine was removed)
    or
  • Redirect somewhere else (sg - machine was removed)
  • Is there DNS to remove (nk - INC1273888)

Is there a map service?

Cures map service references old db data

  • Stop (sd)
  • Delete (sd)

Is there a forklift pallet?

I think there is a script expecting data to be placed in a share or something?

  • Remove repo (sd)
  • Remove stale data from forklift hashing and receiving (sd)

Are there service dependencies?

  • Validate that the web api does not query it (sg)
  • Validate that AGRC or applications widgets do not reference it (sg)

@stdavis @steveoh @MichaelAGRC

Remove OGM Items from AGRC AGOL Org

Summary

DOGM has hosts their own AGOL items for these datasets now so we should not duplicate their offerings. The data will continue to be hosted in SGID, SGID10 and OpenSGID.

AGRC Items

DOGM Items

Triage

  • Data Team Triage
  • Dev Team Triage (@stdavis)
  • Cadastre Team Triage

Remove data from the following areas

  • ArcGIS Online (@gregbunce)
  • Google Drive (@ZachBeck )
  • Open data (@nathankota )
    • How do we switch our open data from our items to DOGMs? Do we need to ask them to share them with us? SITLA land ownership would be a good example.
  • Backseat driver (@stdavis)

Copy data to the following areas

deleting

  • [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
  • [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
  • [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

  • gis.utah.gov data pages (@steveoh )
  • Stewardship doc and sgid-index (@steveoh)
  • Update row from SGID.META.AGOLItems (@stdavis)

Is there a forklift pallet?

  • Update OGMPallet to point to DOGM AGOL services (@stdavis)
  • [ ] Remove row from data/hashed/changedetection.gdb/TableHashes (@stdavis)

Notification

- [ ] Blog post (assigned to)

Add historical monuments and marker data to the SGID

Summary

  • Proposed Dataset Name: MonumentsAndMarkers
  • Proposed ISO Category: History
  • Data Description: Point feature class of historical monuments and markers
  • Source Agency/Entity: State History
  • Contact: Skylar Schulzke [email protected]
  • Update Frequency: as needed

Triage

  • Data Team Triage Complete (@ZachBeck )
  • Dev Team Triage Complete (@steveoh )
    - [ ] Cadastre Team Triage Complete

We are introducing data

The data was or will be added on 2020/06/22 to the following areas

  • Internal SGID
    - [ ] SGID10
    - [ ] ArcGIS Online

The data should propagate automatically to

  • ArcGIS Online
    - [ ] Internal SGID
  • SGID10
  • Open SGID
  • Open data
  • SGID.META.ChangeDetection

References to the data need to be manually added to

  • gis.utah.gov data pages
  • Stewardship doc and sgid-index
  • SGID.META.AGOLItems

We have verified the data is live

Notification

- [ ] Blog post (@assigned)

Visually different result emojis

It's hard to differentiate between 👍 and 👎 at a quick glance in the conductor results table.

Perhaps 👎 could be replaced with ⛔ ?

Deprecate LOCATION.PlaceNamesGNIS1990

Is the data removal temporary or permanent?

  • Replaced with newer data
  • Historical data for archive
  • No longer relevant

Identify places where the data lives

  • ArcGIS Online
  • Internal SGID
  • External SGID
  • Google Drive
  • Open data
  • Mapserv
  • gis.utah.gov data pages
  • Stewardship doc and sgid-index

Is there a website?

  • Is the source code on GitHub?
  • Should it be archived?
  • Should it be removed from the web server or show a static page with information?
  • Should it redirect somewhere else?

Is there a map service?

  • Should it be stopped or deleted?

Is there a forklift pallet?

  • Should it continue to run or be removed?

Are there service dependencies?

  • Does the web api query it?
  • Do AGRC or applications widgets reference it?

Duplicate AGOL UTA layers

Summary

The following layer have been marked deprecated for some time.

Two replacement layers were uploaded near the end of 2019 and are the layers referenced in the SGID.META.AGOLItems table. These older layers are still getting some use, but should be removed.

Suggested Action

  • [ ] Move items to shelved folder/group for x months (1? 3? 6?)
  • Update description with upcoming deletion date (@ZachBeck)
  • Delete completely

Triage

  • Data Team Triage (data team )
  • Dev Team Triage (@steveoh)
  • [ ] Cadastre Team Triage

Remove data from the following areas

  • ArcGIS Online (@ZachBeck )
  • [ ] Internal SGID (assigned to)
  • [ ] SGID10 (assigned to)
  • [ ] Open SGID (assigned to)
  • [ ] Google Drive (assigned to)
    - [ ] Open data (assigned to)
    - Mapserv (assigned to)

Copy data to the following areas

  • [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
  • [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
  • [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

  • [ ] gis.utah.gov data pages (assigned to)
  • [ ] Stewardship doc and sgid-index (assigned to)
  • [ ] SGID.META.AGOLItems (assigned to)
  • [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
  • [ ] SGID.META.ChangeDetection (assigned to)

Is there a website?

  • [ ] Archive source code repository (assigned to)
  • [ ] Remove from the web server (assigned to)
    or
  • [ ] Replace app with a static page with information (assigned to)
    or
  • [ ] Redirect somewhere else (assigned to)

Is there a map service?

  • [ ] Stop (assigned to)
  • [ ] Delete (assigned to)

Is there a forklift pallet?

  • [ ] Remove repo (assigned to)
  • [ ] Remove stale data from forklift hashing and receiving (assigned to)

Are there service dependencies?

  • [ ] Validate that the web api does not query it (assigned to)
  • [ ] Validate that AGRC or applications widgets do not reference it (assigned to)

Notification

  • Blog post (assigned to)
  • Twitter (@steveoh)
    • Intent
    • Completed

Old AGOL Items: UtahAGRC

I've found the following items in AGOL that are owned by the UtahAGRC user that look old, unused, and/or broken. After the list is completed, we will triage it to figure out who knows it best and can determine if they can be deprecated/deleted. If they are part of the SGID or some other major project, consider opening a new issue using the full deprecation checklist/process.

I don't mean to call anyone out for their old data. I just wanted to have a place to track these things as I found them as part of the HTTP/HTTPS update process.

Everyone will look through and check items that should be saved. Tag the item with your name (@user) if you take care of it. After you've looked through it all, make a comment at the bottom stating so. If you deleted it, strike through the item.

Deprecate grantreporting.udaf.utah.gov/public

Summary

The web app needs to be shut down and the data archived.

Is the data removal temporary or permanent?

  • Replaced with newer data (intials)
  • Historical data for archive (intials)
  • No longer relevant (sd)

Where does the data live?

  • ArcGIS Online (intials)
    • Action taken (intials)
  • Internal SGID (intials)
    • Action taken (intials)
  • External SGID (sd)
    • Action taken - database backup uploaded to drive(sd)
    • Request shut down of sql server database (initials)
  • Google Drive (intials)
    • Action taken (intials)
  • Open data (intials)
    • Action taken (intials)
  • Mapserv (intials)
    • Action taken (intials)
  • gis.utah.gov data pages (intials)
    • Action taken (intials)
  • Stewardship doc and sgid-index (intials)
    • Action taken (intials)

Is there a website?

http://grantreporting.udaf.utah.gov/

  • Is the source code on GitHub? (sd)
  • Should it be archived? yes (sd)
    • Action taken - archived (sd)
  • Should it be removed from the web server or show a static page with information? (sd)
    • Action taken - shut down app pools related to this site on .126 (sd)
  • Should it redirect somewhere else? (intials)
    • Action taken (intials)

Is there a map service?

  • Should it be stopped or deleted? (sd)
    • Action taken - map service deleted from mapserv (sd)

Is there a forklift pallet?

  • Should it continue to run or be removed? (sd)
    • Removed pallet from production forklift (sd)
  • Should stale data be removed from forklift hashing and receiving? (sd)
    • Action taken (sd) - removed from production servers as well

Are there service dependencies?

  • Does the web api query it? (intials)
    • Action taken (intials)
  • Do AGRC or applications widgets reference it? (intials)
    • Action taken (intials)

Remove duplicate state fuel site from arcgis online

Summary

It looks like there are two state fuel site items. Please determine which is the maintained version and deprecate the other.

  1. StateFuelSites (item id: bbad0291cb754be48ae91dc7d82f6f5c)
  2. Utah State Fuel Sites (item id: 34fbc5c654ee44c4bfb14c8d9fc73fc5)

UPDATE
We have gotten new data from the fleet folks. This will be used to replace the existing layer's per @gregbunce's comment on 15 Dec.

Triage

Remove StateFuelSites from the following areas

Deprecate/brownout Utah State Fuel Sites from the following areas:

Add new data to the following areas:

Update information to reflect the new data in the following areas

Verify the new data is live in the following areas:

Notification

sign off initials

Issue description

Describe the problem you are having

I would like to know who checked off on what part of the checklist. What do you all think about updating the issue template to contain an (author) piece at the end that we can put our initials in?

for instance,

  • Is the source code on GitHub? (sg)

@stdavis @ZachBeck @MichaelAGRC @gregbunce

Old AGOL Items: Jake

I've found the following items in AGOL that are owned by you that look old, unused, and/or broken. Please take a look at them and see if they can be deprecated/deleted. If they are part of the SGID or some other major project, consider opening a new issue using the full deprecation checklist/process.

I don't mean to call anyone out for their old data. I just wanted to have a place to track these things as I found them as part of the HTTP/HTTPS update process.

This will be a living issue while we track down http links. The list may be edited from time to time.

  • Election Results (Dashboard): (not publicly shared, search by name)

Old AGOL Items: Zach

I've found the following items in AGOL that are owned by you that look old, unused, and/or broken. Please take a look at them and see if they can be deprecated/deleted. If they are part of the SGID or some other major project, consider opening a new issue using the full deprecation checklist/process.

I don't mean to call anyone out for their old data. I just wanted to have a place to track these things as I found them as part of the HTTP/HTTPS update process.

This will be a living issue while we track down http links. The list may be edited from time to time.

[ ] Utah ILEC Telephone and DSL Exchange Boundaries and Territories (Web Map): http://utah.maps.arcgis.com/home/item.html?id=cea1805ebeac4072a270192d0285b12f
[ ] July 2015: BLM Comm Sites (Web Mapping Application): http://utah.maps.arcgis.com/home/item.html?id=8ec0737321f24e3c9e0b6f0c1731ce09 (and webmap: http://utah.maps.arcgis.com/home/item.html?id=4e4d355f50e94728b7c0b69470314674)
[ ] October 2016 Map of the Month: State Facilities (Web Mapping Application): http://utah.maps.arcgis.com/home/item.html?id=7723c9bb92e9442b8794a6bdad73d01f (and webmap: http://utah.maps.arcgis.com/home/item.html?id=7824facee8b2452a9d64ad3baac2a6ca)
[ ] Active DABC Licensees (Web Mapping Appliction): http://utah.maps.arcgis.com/home/item.html?id=aeff272ef1fe4e9892f9ffbd29715867
[ ] GOED Broadband Planning Web App (Web Mapping Application): http://utah.maps.arcgis.com/home/item.html?id=60ef82117a594d858332e2624eabff55
[ ] Interactive Residential Map (Web Mapping Application): http://utah.maps.arcgis.com/home/item.html?id=d250e652c876464eaa547d17e783bd92
~ [ ] Business Fiber Service (Web Mapping Application): http://utah.maps.arcgis.com/home/item.html?id=50c5a1727d9a432fba003a80048d4486 (This and the previous item appear to be linked to broadband stuff, but only have a couple dozen views each)~
[ ] Utah Ski Areas (Web Map): (not publicly shared, search by name)
[ ] UT Broadband Verification Map August Fall 2013 (Web Map): http://utah.maps.arcgis.com/home/item.html?id=6e926e19fc674b45a8b5edbdd2fcfa7b
[ ] UT Broadband Address Pnt Verification Map August Fall 2013-Copy (Web Map): http://utah.maps.arcgis.com/home/item.html?id=d702dcd19f034044b78069f0e7464d6a
[ ] sbi all test (Web Map): (not publicly shared, search by name)
[ ] Mission Bay Reserve (geotagged) (Web Map): (not publicly shared, search by name)
[ ] Hazard_Faults_Quaternary (Map Image layer): (not publicly shared, search by name)
[ ] SBI template (Web Mapping Application): (not publicly shared, search by name)
[ ] test (Web Mapping Application): (not publicly shared, search by name)

ECONOMY.TaxAreas2018

Summary

ECONOMY.TaxAreas2018 has been replaced with ECONOMY.TaxAreas2019

Triage

Remove data from the following areas

- [ ] ArcGIS Online (@jacobdadams )

Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (@jacobdadams )

  • Move existing AGOL item to AGRC_Shelved AGOL folder (@jacobdadams )
    - [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

Is there a website?

  • [ ] Archive source code repository (assigned to)
  • [ ] Remove from the web server (assigned to)
    or
  • [ ] Replace app with a static page with information (assigned to)
    or
  • [ ] Redirect somewhere else (assigned to)

Is there a map service?

  • [ ] Stop (assigned to)
  • [ ] Delete (assigned to)

Is there a forklift pallet?

  • [ ] Remove repo (assigned to)
    findstr /SIN /d:c:\forklift\warehouse /C:"taxarea" *.py had no results
  • Remove stale data from forklift hashing and receiving (@stdavis)

Are there service dependencies?

  • Validate that the web api does not query it (@steveoh - searched bigquery logs and no queries made)
  • Validate that AGRC or applications widgets do not reference it (@steveoh)

Notification

  • Blog post (assigned to)
  • Twitter (@steveoh)
    • Intent
    • Completed

Add Society.Schools HigherEducation to SGID

Summary

This dataset contains point locations of higher education institutions in Utah: colleges and universities. It's one of two new layers (the other being Society.Schools_PreKto12) that will replace Society.Schools.

  • Proposed Dataset Name: Schools_HigherEducation
  • Proposed ArcGIS Online Name: Utah Schools Higher Education
  • Proposed ISO Category: Society
  • Data Description: This layer contains higher education institutions in the state of Utah: colleges and universities.
  • Source Agency/Entity: AGRC, USHE, and USBE
  • Contact: AGRC
  • Update Frequency: Annually

Triage

  • Data Team Triage (@ZachBeck)
  • Dev Team Triage (@steveoh)
    - [ ] Cadastre Team Triage ()

We are introducing data

The data was or will be added TBD (week of 8/24 or 8/31) to the following areas

  • Internal SGID
  • SGID10
  • ArcGIS Online

The data is high quality

The data should propagate automatically to

  • ArcGIS Online
  • SGID10
  • Open SGID
  • Open data
  • SGID.META.ChangeDetection

References to the data need to be manually added to

We have verified the data is live

Notification

Removing printproxy from cloud function dns

Summary

This is to inform you that the print proxy has been upgraded to support a more permanent and descriptive DNS: print.agrc.utah.gov and the https://us-central1-utahkoopserver.cloudfunctions.net/printproxy DNS is being deprecated on September 1.

The new DNS is active and ready for production use.

Please update your AGOL organization default print service (Settings -> Utility services) and any other apps that use the print proxy to use this new DNS by Sept 1st.

Here is an example of what the upgrade would look for account number 7:

Old (planned shut off date of Sept 1st):

  • https://us-central1-utahkoopserver.cloudfunctions.net/printproxy/7/arcgis/rest/services/GPServer/export

New:

  • https://print.agrc.utah.gov/7/arcgis/rest/services/GPServer/export

Notification

Duplicate Utah County LIR Parcels AGOL Items

Summary

  1. http://utah.maps.arcgis.com/home/item.html?id=62b0357b8d1646cc919a91423b5fa15d
  2. http://utah.maps.arcgis.com/home/item.html?id=69477c1143924bc9990cdb930b033fb5

Item 2 seems to be the one in the metatable (it's being updated by auditor) and is shared via OpenData. It seems to have come into existence back in November when we started the new AGOL/OpenData push.

Item 1 reports last being updated on July 27, but my auditor logs show that auditor fixed its tags on that date (which it does for any feature service, not just ones in the metatable) but didn't fix anything else (consistent with it not being in the metatable).

This process is a little non-standard for this template; triagers, as part of your triage please identify which of these layers you are using and if either can be deleted. Once that is determined, go through the normal checks below for the one to be deleted.

Triage

  • Data Team Triage (@rkelson )
  • Dev Team Triage (@steveoh)
    - [ ] Cadastre Team Triage

Remove data from the following areas

  • ArcGIS Online (@jacobdadams)
    - [ ] Internal SGID (assigned to)
    - [ ] SGID10 (assigned to)
    - [ ] Open SGID (assigned to)
    - [ ] Google Drive (assigned to)
    - [ ] Open data (assigned to)
    - [ ] Mapserv (assigned to)
    - [ ] Retire application-specific prod and test SQL Databases (assigned to)

Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
- [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
- [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

- [ ] gis.utah.gov data pages (assigned to)
- [ ] Stewardship doc and sgid-index (assigned to)
- [ ] SGID.META.AGOLItems (assigned to)
- [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
- [ ] SGID.META.ChangeDetection (assigned to)

Is there a website?

- [ ] Archive source code repository (assigned to)
- [ ] Remove from the web server (assigned to)
or
- [ ] Replace app with a static page with information (assigned to)
or
- [ ] Redirect somewhere else (assigned to)

Is there a map service?

- [ ] Stop (assigned to)
- [ ] Delete (assigned to)

Is there a forklift pallet?

- [ ] Remove repo (assigned to)
- [ ] Remove stale data from forklift hashing and receiving (assigned to)
- [ ] Remove row from data/hashed/changedetection.gdb/TableHashes

Are there service dependencies?

- [ ] Validate that the web api does not query it (assigned to)
- [ ] Validate that AGRC or applications widgets do not reference it (assigned to)

Notification

- [ ] Blog post (assigned to)

Deprecate SGID.HISTORY.ArcheologySites

Summary

A short summary of the situation... State History, has some partners that feel like the hexagons are not appropriate, that 1 km is too detailed. They would like to shut that service down. I am a little unsure what it is connected to, It may take a bit of time to find what it is connected to

I will just try to locate some of this

Remove data from the following areas

  • ArcGIS Online (zb)
  • Internal SGID (zb)
  • External SGID (zb)
  • Google Drive (zb)
  • Open data (zb)
  • gis.utah.gov data pages (sg)
  • Stewardship doc and sgid-index (sg)
  • SGID.META.AGOLItems (sd)

Is there a forklift pallet?

  • Remove repo (sd)
  • Remove stale data from forklift hashing and receiving (sd)

Are there service dependencies?

  • Validate that the web api does not query it (sg)
  • Validate that AGRC or applications widgets do not reference it (sg)

Add internal sgid data propagation

very helpful...a possible addition to the readme?

Yes so this should be helpful for everyone.

Data in the internal sgid will be added to the sgid10 with swapper

If there is a record in the agol items table it will be added to

  • the open sgid with cloudb
  • arcgis online with forklift
  • open data with the agol validator

Did I miss anything?

Originally posted by @nathankota in #42 (comment)

Remove UtahEM service and UDES database

Summary

Utah DEM has replaced all links to the UtahEM map service layers in their WebEOC software. The service can be stopped immediately and will remain unavailable during a "brown out" period while DEM tests WebEOC mapping capabilities with the replacement services. A testing schedule will be determined in conjunction with DEM and a reminder will be set within this issue to delete the service, based on the testing schedule.

Once the service is deleted the UDES SQL database, upon which the UtahEM service relies, can then be removed.

Triage

- [x] Data Team Triage (@gregbunce)

Remove data from the following areas

- [ ] ArcGIS Online (assigned to)
- [ ] Internal SGID (assigned to)
- [x] SGID10 (assigned to)
- [x] Open SGID (assigned to)
- [x] Google Drive (assigned to)
- [x] Open data (assigned to)

  • Mapserv (assigned to)
  • Retire application-specific prod and test SQL Database (@MichaelAGRC )

# Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
- [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
- [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

# Update information in the following areas

- [ ] gis.utah.gov data pages (assigned to)
- [ ] Stewardship doc and sgid-index (assigned to)
- [ ] SGID.META.AGOLItems (assigned to)
- [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
- [ ] SGID.META.ChangeDetection (assigned to)
- [ ] Backseat Driver (assigned to)

# Is there a website?

- [ ] Archive source code repository (assigned to)
- [ ] Remove from the web server (assigned to)
or
- [ ] Replace app with a static page with information (assigned to)
or
- [ ] Redirect somewhere else (assigned to)

Is there a map service?

Is there a forklift pallet?

  • Remove repo (assigned to @steveoh)
  • Remove stale data from forklift hashing and receiving (assigned to @stdavis)
  • Remove row from data/hashed/changedetection.gdb/TableHashes (assigned to @stdavis)

# Are there service dependencies?

- [ ] Validate that the web api does not query it (assigned to)
- [ ] Validate that AGRC or applications widgets do not reference it (assigned to)

Notification

- [ ] Blog post (assigned to)
- [ ] Twitter (@steveoh)
- [ ] Intent
- [ ] Completed

Add TrailsAndPathways to SGID

Summary

  • Proposed Dataset Name: TrailsAndPathways
  • Proposed ISO Category: Recreation
  • Data Description: Utah Trails and Pathways
  • Source Agency/Entity: AGRC
  • Contact: Greg Bunce
  • Update Frequency: Monthly

Triage

  • Data Team Triage Complete
  • Dev Team Triage Complete (assigned to)
  • Cadastre Team Triage Complete

We are introducing data

The data was or will be added on 2020/06/25 to the following areas

  • Internal SGID
  • [ ] SGID10
  • [ ] ArcGIS Online

The data is high quality

  • Sweeper checks have run and passed
  • The minimum requirements for metadata are populated
  • The data complies with our domain rules

The data should propagate automatically to

  • ArcGIS Online
  • SGID10
  • Open SGID
  • Open data
  • SGID.META.ChangeDetection

References to the data need to be manually added to

  • gis.utah.gov data pages
  • Stewardship doc and sgid-index
  • SGID.META.AGOLItems

We have verified the data is live

Notification

Remove Society.Schools from SGID

Summary

NOTE: WAIT TO REMOVE THIS LAYER until after the new higher ed layer has been added to SGID.

The SGID Society.Schools layer can be deprecated as it has been replaced by Society.Schools_PreKto12 and the soon to be added higher education schools layer. The data and attributes in this existing school layer are represented in the new data, so this layer can be removed and deleted: it has no added value.

Here's the AGOL Item ID: 9e700ba2de90451d9c16c176d58e0b68
AGOL Name: Utah Schools
http://utah.maps.arcgis.com/home/item.html?id=9e700ba2de90451d9c16c176d58e0b68

Triage

Remove data from the following areas

  • ArcGIS Online (assigned to @gregbunce )
  • Internal SGID (assigned @ZachBeck )
  • SGID10 (assigned @ZachBeck )
  • Open SGID (assigned to @steveoh )
  • Google Drive (assigned to @gregbunce )
  • Open data (assigned to @gregbunce )
    - [ ] Mapserv (assigned to)
    - [ ] Retire application-specific prod and test SQL Databases (assigned to)
  • Backseat Driver (@stdavis)
  • Update Base Map Cache MXDs (@ZachBeck)

Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
- [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
- [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

- [ ] gis.utah.gov data pages (assigned to)

  • Stewardship doc and sgid-index (@steveoh)
  • SGID.META.AGOLItems (assigned to @ZachBeck )
    - [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
  • SGID.META.ChangeDetection (assigned to @ZachBeck or @steveoh )

Is there a website?

- [ ] Archive source code repository (assigned to)
- [ ] Remove from the web server (assigned to)
or
- [ ] Replace app with a static page with information (assigned to)
or
- [ ] Redirect somewhere else (assigned to)

Is there a map service?

  • [ ] Stop (assigned to)
  • [ ] Delete (assigned to)
  • Update existing map service (@stdavis)

Is there a forklift pallet?

  • Remove repo (@stdavis)
  • Remove stale data from forklift hashing and receiving (@stdavis)
  • [ ] Remove row from data/hashed/changedetection.gdb/TableHashes

Are there service dependencies?

  • Validate that the web api does not query it (@steveoh
  • Validate that AGRC or applications widgets do not reference it (@steveoh)

Notification

  • [ ] Blog post (assigned to)
  • Twitter (@steveoh )
    • Intent (though I think we already did this, right?)
    • Completed

Deprecate SGID10.ENVIRONMENT.DWQMonitoredLakes132

Summary

This layer is a duplicate of SGID10.ENVIRONMENT.DWQAssessedLakes and needs to be removed.

From Mark Stanger

Yes, you should delete SGID10.ENVIRONMENT.DWQMonitoredLakes132 from the SGID as it is old and not as accurate regarding the lakes we (DWQ) monitor and assess for water quality.

Remove data from the following areas

Are there service dependencies?

  • Validate that the web api does not query it (@steveoh)

Deprecate mapserv.utah.gov/oilgasmining

We've had a redirect to https://datamining.ogm.utah.gov for some time now. I think that it's time to remove everything related to this app.

Identify places where the data lives

  • Mapserv

Is there a website?

  • Is the source code on GitHub?
  • Should it be archived?
  • Should it be removed from the web server or show a static page with information?
  • Should it redirect somewhere else?

Is there a map service?

  • Should it be stopped or deleted?

Is there a forklift pallet?

  • Should it continue to run or be removed?

Old AGOL Items: Steve

I've found the following items in AGOL that are owned by you that look old, unused, and/or broken. Please take a look at them and see if they can be deprecated/deleted. If they are part of the SGID or some other major project, consider opening a new issue using the full deprecation checklist/process.

I don't mean to call anyone out for their old data. I just wanted to have a place to track these things as I found them as part of the HTTP/HTTPS update process.

This will be a living issue while we track down http links. The list may be edited from time to time.

  • Service Proxy (Application): (not publicly shared, search by name)

ECONOMY.TaxEntities2018

Summary

ECONOMY.TaxEntities2018 has been replaced with ECONOMY.TaxEntities2019

Triage

Remove data from the following areas

- [ ] ArcGIS Online (@jacobdadams )

Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (@jacobdadams )

  • Move existing AGOL item to AGRC_Shelved AGOL folder (@jacobdadams )
    - [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

Is there a website?

- [ ] Archive source code repository (assigned to)
- [ ] Remove from the web server (assigned to)
or
- [ ] Replace app with a static page with information (assigned to)
or
- [ ] Redirect somewhere else (assigned to)

Is there a map service?

- [ ] Stop (assigned to)
- [ ] Delete (assigned to)

Is there a forklift pallet?

- [ ] Remove repo (assigned to)
- [ ] update pallet in locate (@stdavis)

  • Remove stale data from forklift hashing and receiving (@stdavis)

Are there service dependencies?

  • Validate that the web api does not query it (@steveoh)
  • Validate that AGRC or applications widgets do not reference it (@steveoh)

Notification

  • Blog post (assigned to)
  • Tweet (@steveoh)
    • Intent Tweet
    • Completed Tweet

yes or no checkboxes

Describe the problem you are having

I cannot tell from the checkboxes if the answer is yes or no or if it's been taken care of. Do we need to make that more clear?

for instance, when a deprecation doesn't have a github, website etc, do one of us check them off anyway since we looked?

are we conveying that we identified the places that need work or that the work has been done.

Deprecate SGID.ECONOMY.TaxEntities2018

Summary

SGID.ECONOMY.TaxEntities2018 is being replaced by ECONOMY.TaxEntities2019

Remove data from the following areas

  • ArcGIS Online (intials)
  • Internal SGID (intials)
  • SGID10 (intials)
  • Open SGID (initials)
  • Google Drive (intials)
  • Open data (intials)
  • Mapserv (intials)
  • gis.utah.gov data pages (intials)
  • Stewardship doc and sgid-index (intials)
  • SGID.META.AGOLItems (initials)
  • SGID.META.ChangeDetection (initials)

Is there a map service?

  • Stop (intials)
  • Delete (initials)

Is there a forklift pallet?

  • Remove repo (intials)
  • Remove stale data from forklift hashing and receiving (initials)

Are there service dependencies?

  • Validate that the web api does not query it (intials)
  • Validate that AGRC or applications widgets do not reference it (intials)

Streamlining the SGID Data Introduction Process

We've had a couple different conversations about creating a better process for guiding people who want to add data to the SGID, so I'm putting down our notes in this issue. In the future we can branch out to a separate repo if necessary and close this issue.

Goal:
A streamlined way to screen requests for data to be added to the SGID (adding data to the Open SGID, sharing an AGOL item through the SGID Open Data site, or adding a link or other type of entry to the SGID Index) with as much automation as possible.

Benefits:

  • More clear direction for people who want to share data
  • A chance to ensure datasets meet our metadata, quality, and applicability standards
  • Automatically capturing data for the SGID Index for Open SGID/Open Data datasets, ensuring every new dataset is in the Index and reducing fragmentation (helps keep the Index the primary list of SGID datasets).
    • This wouldn't solve the problem of keeping it updated, however.

Components:

  • Some sort of form or automated way to request data to be added to the SGID. The form would include required fields for the necessary tidbits for the Index.
    • If we use github issues, could we use github actions to push data from the issue text into the db discussed below?
    • Some form of notification when new requests come in - Slack, email, carrier pigeon, etc.
  • Revamping the the stewardship tab into a proper DB as we've discussed in the past. This gives us a solid end point for the data coming from the request.
    • Possibly extending this db to hold the metadata as well, so that this one db becomes the source of truth for the Open SGID, AGOL, and the SGID Index?
  • A staging group in AGOL for items that people want to share via Open Data.
    • This should be public so anyone can start the process without first asking for access.
    • A policy regarding how long people have to make any required metadata updates before we remove them from the group
    • A policy for removing items from the Open Data groups that haven't gone through the screen process.
    • A nagger bot to check for new or stale items in the staging group
  • A link checker for the SGID Index db to at least tell us if links to external datasets are totally dead

Process Outline:

  1. Someone requests an addition via the form/issue
    • SGID Index links: link submitted via the form
    • Open SGID layers: email a copy/download link separately
    • Open Data items: share item with the staging group
  2. We review the request against our policies
    • SGID Index links: state agency?
    • Open SGID layers: SGID qualifications and metadata
    • Open Data items: metadata and Open Data presentation tips
  3. Open a Porter issue to add the data and perform the necessary steps
    • SGID Index links: pull the data straight from the issue into the Index db
    • Open SGID layers: sweeper, add data to internal, push out from internal to AGOL and Open SGID; pull data from issue into Index db
    • Open Data items: have user share with appropriate SGID AGOL group, remove from staging group; pull data from issue into Index db.

Deprecate fiberediting.mapserv.utah.gov

Deprecate fiberediting app due to under-utilization. The app has only been used by 1 provider in the past year (on 3/20/2020)

FiberVerification database should remain for the time being.

Is there a website?

Is there a map service?

Is there a forklift pallet?

  • Remove repo (@steveoh)
    • no pallet
  • Remove stale data from forklift hashing and receiving (@steveoh)
    • nothing to remove

Are there service dependencies?

  • Validate that the web api does not query it (@steveoh)
    • none
  • Validate that AGRC or applications widgets do not reference it (@steveoh)
    • none

Deprecate SGID10.PLANNING.QLTYGROWTH[...] rasters

Summary

The three QLTYGROWTH rasters in SGID10 are apparently from a planning scenario/forecast tool from 1998. They are out of date and, from a modern land use modelling perspective, of limited utility. We've got them marked for shelving in AGOL, but it's probably better to just let them float off into the sunset as another wrong model (rule # 1 in modelling: All models are wrong, some models are useful).

Remove data from the following areas

  • Internal SGID (ZB)
  • (?) Google Drive (ZB)
  • (no action) Mapserv (@steveoh)

Is there a map service?

Is there a forklift pallet?

  • (no action) Remove repo (@steveoh)
  • (no action) Remove stale data from forklift hashing and receiving (@steveoh)

Are there service dependencies?

  • (no action) Validate that the web api does not query it (@steveoh)
  • (no action) Validate that AGRC or applications widgets do not reference it (@steveoh)

Deprecate SGID.ECONOMY.TaxAreas2018

Summary

SGID.ECONOMY.TaxAreas2018 is being replaced by ECONOMY.TaxAreas2019

Remove data from the following areas

  • ArcGIS Online (intials)
  • Internal SGID (intials)
  • SGID10 (intials)
  • Open SGID (initials)
  • Google Drive (intials)
  • Open data (intials)
  • Mapserv (intials)
  • gis.utah.gov data pages (intials)
  • Stewardship doc and sgid-index (intials)
  • SGID.META.AGOLItems (initials)
  • SGID.META.ChangeDetection (initials)

Is there a map service?

  • Stop (intials)
  • Delete (initials)

Is there a forklift pallet?

  • Remove repo (intials)
  • Remove stale data from forklift hashing and receiving (initials)

Are there service dependencies?

  • Validate that the web api does not query it (intials)
  • Validate that AGRC or applications widgets do not reference it (intials)

Deprecate SGID.POLITICAL.UtahSchoolBoardDistricts_Members

Summary

In an email from @mheagin on 12/3/19:

I was updating some data and noticed our SGID.POLITICAL.UtahSchoolBoardDistricts_Members is the same as SGID.POLITICAL.UtahSchoolBoardDistricts2015.
I thought the "_Members" was created because the Board members names were not part of the original "..Districts2015 data, it may have been the "2012" version.
Any way since they are now both identical I believe we can eliminate the "_Members" version (see attachment).
Since that was the one I had been updating we need to push the button to get UtahSchoolBoardDistricts2015 (855c45da6d2e4386b06cfa27229f9685 ) updated in AGOL too. Everything is updated in the ...Distircts2015 on SGID now.

Remove data from the following areas

  • ArcGIS Online (mf)
  • Internal SGID (mf)
  • External SGID (mf)
  • Google Drive (intials)
  • Open data (mf)
  • gis.utah.gov data pages (sg)
  • Stewardship doc and sgid-index (sg)
  • Remove from SGID.META.AGOLItems (mf)

Are there service dependencies?

  • Validate that the web api does not query it (sg)
  • Validate that AGRC or applications widgets do not reference it (sd)

Deprecate Utah Water Chemistry

Summary

UGS has decided to deprecate the Utah Water Chemistry Database. There is a forklift process to sling some data for the application, but I am not sure if there are any associated SGID data sets. The application lives on a UGS server and I will coordinate with them so they can time their deprecation strategy.

Triage

Remove data from the following areas

- [ ] ArcGIS Online (assigned to)
- [ ] Internal SGID (assigned to)
- [ ] SGID10 (assigned to)
- [ ] Open SGID (assigned to)
- [ ] Google Drive (assigned to)
- [ ] Open data (assigned to)
- [ ] Mapserv (assigned to)

  • Retire SQL Server databases. We should probably confirm with Paul Inkenbrandt before doing this. (@nathankota)
    • Prod: SERVER=ugswaterchemistry.agrc.utah.gov;DATABASE=UGSWaterChemistry
    • Test: SERVER=itdb112sp.dts.utah.gov\mspd14;DATABASE=UGSWaterChemistry

Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
- [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
- [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

- [ ] gis.utah.gov data pages (assigned to)
- [ ] Stewardship doc and sgid-index (assigned to)
- [ ] SGID.META.AGOLItems (assigned to)
- [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
- [ ] SGID.META.ChangeDetection (assigned to)

Is there a website?

Is there a map service?

- [ ] Stop (assigned to)
- [ ] Delete (assigned to)

Is there a forklift pallet?

  • Remove repo (@stdavis)
  • Remove stale data from forklift hashing and receiving (@stdavis)

Are there service dependencies?

- [ ] Validate that the web api does not query it (assigned to)
- [ ] Validate that AGRC or applications widgets do not reference it (assigned to)

Notification

- [ ] Blog post (assigned to)
- [ ] Twitter (@steveoh)
- [ ] Intent
- [ ] Completed

Remove CADASTRE.LandOwnership_WeeklyUpdate from SGID

Summary

Since we are now pulling LandOwnership data directly from the SITLA service via forklift, we no longer need to have Barry run his script to update SGID. I've let Barry know that he can stop running the script. We just need to clean up LandOwnership_WeeklyUpdate.

Note that this dataset is only visible to the Cadastre user so far as I can tell...

Triage

Remove data from the following areas

  • [ ] ArcGIS Online (assigned to) (taken care of in #55)
  • Internal SGID (assigned to @ZachBeck '9/17/2020' )
  • SGID10 (assigned to @ZachBeck '9/17/2020' )
  • [ ] Open SGID (assigned to)
  • [ ] Google Drive (assigned to)
  • [ ] Open data (assigned to)
  • [ ] Mapserv (assigned to)
  • [ ] Retire application-specific prod and test SQL Databases (assigned to)

Copy data to the following areas

  • [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
  • [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
  • [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

  • [ ] gis.utah.gov data pages (assigned to)
  • [ ] Stewardship doc and sgid-index (assigned to)
  • [ ] SGID.META.AGOLItems (assigned to)
  • [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
  • [ ] SGID.META.ChangeDetection (assigned to)
  • [ ] Backseat Driver (assigned to)

Is there a website?

  • [ ] Archive source code repository (assigned to)
  • [ ] Remove from the web server (assigned to)
    or
  • [ ] Replace app with a static page with information (assigned to)
    or
  • [ ] Redirect somewhere else (assigned to)

Is there a map service?

  • [ ] Stop (assigned to)
  • [ ] Delete (assigned to)

Is there a forklift pallet?

  • [ ] Remove repo (assigned to)
  • [ ] Remove stale data from forklift hashing and receiving (assigned to)
  • [ ] Remove row from data/hashed/changedetection.gdb/TableHashes

Are there service dependencies?

  • [ ] Validate that the web api does not query it (assigned to)
  • [ ] Validate that AGRC or applications widgets do not reference it (assigned to)

Notification

  • [ ] Blog post (assigned to)
  • [ ] Twitter (@steveoh)
    • [ ] Intent
    • [ ] Completed

Remove SGID.ENVIRONMENT.DAQAirOilGasEmissionsPt from SGID and DEQ Interactive Map

Summary

This dataset is essentially static and hasn't been updated in years. It participates as a query layer in enviro.deq.utah.gov. I asked Michelle Horning about it and she said to just remove it from the app and SGID. I'm guessing it was added to SGID in the first place only because Harold pushed for it.

This is the exact same situation at #49...

Triage

Remove data from the following areas

  • ArcGIS Online (@gregbunce on 8/21/2020) (item: 34368daa7b2d45b4906b7023640d3ce3)
  • Internal SGID (@ZachBeck )
  • SGID10 (@ZachBeck )
  • Open SGID (@gregbunce verified it's gone on 8/21/2020 )
  • Google Drive (@ZachBeck )
  • Open data (@gregbunce on 8/21/2020)
  • Mapserv (@stdavis)
    - [ ] Retire application-specific prod and test SQL Databases (assigned to)

Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
- [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
- [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

- [ ] gis.utah.gov data pages (assigned to)

  • Stewardship doc and sgid-index (@nathankota )
  • SGID.META.AGOLItems (@stdavis)
    - [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
  • SGID.META.ChangeDetection (@stdavis)

Is there a website?

- [ ] Archive source code repository (assigned to)
- [ ] Remove from the web server (assigned to)
or
- [ ] Replace app with a static page with information (assigned to)
or
- [ ] Redirect somewhere else (assigned to)

  • Remove query layer from enviro.deq.utah.gov (@stdavis)

Is there a map service?

- [ ] Stop (assigned to)
- [ ] Delete (assigned to)

Is there a forklift pallet?

- [ ] Remove repo (assigned to)

  • Remove stale data from forklift hashing and receiving (@stdavis)
  • Remove row from data/hashed/changedetection.gdb/TableHashes (@stdavis)
    Layers will be removed from pallet automatically when they are removed from the app.

Are there service dependencies?

  • Validate that the web api does not query it (@steveoh)
  • Validate that AGRC or applications widgets do not reference it (@stdavis)

Notification

- [ ] Blog post (assigned to)

Remove SGID.ENVIRONMENT.DAQAirOilGasEmissions from SGID and DEQ Interactive Map

Summary

This dataset is essentially static and hasn't been updated in years. It participates as a query layer in enviro.deq.utah.gov. I asked Michelle Horning about it and she said to just remove it from the app and SGID. I'm guessing it was added to SGID in the first place only because Harold pushed for it.

This is the exact same situation as #50.

Triage

Remove data from the following areas

  • ArcGIS Online (@gregbunce on 8/21/2020) (item: 97e144bdd84c45bf95041e4f50ec09ef)
  • Internal SGID (@ZachBeck )
  • SGID10 (@ZachBeck )
  • Open SGID (@gregbunce verfied it's gone on 8/21/2020 )
  • Google Drive (@ZachBeck )
  • Open data (@gregbunce on 8/21/2020)
  • Mapserv (@stdavis)
    - [ ] Retire application-specific prod and test SQL Databases (assigned to)

Copy data to the following areas

- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
- [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
- [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

- [ ] gis.utah.gov data pages (assigned to)

  • Stewardship doc and sgid-index (@nathankota )
  • SGID.META.AGOLItems (@stdavis)
    - [ ] AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
  • SGID.META.ChangeDetection (@stdavis)

Is there a website?

- [ ] Archive source code repository (assigned to)
- [ ] Remove from the web server (assigned to)
or
- [ ] Replace app with a static page with information (assigned to)
or
- [ ] Redirect somewhere else (assigned to)

  • Remove query layer from enviro.deq.utah.gov (@stdavis)

Is there a map service?

- [ ] Stop (assigned to)
- [ ] Delete (assigned to)

Is there a forklift pallet?

- [ ] Remove repo (assigned to)

  • Remove stale data from forklift hashing and receiving (@stdavis)
  • Remove row from data/hashed/changedetection.gdb/TableHashes (@stdavis)
    Layers will be removed from pallet automatically when they are removed from the app.

Are there service dependencies?

  • Validate that the web api does not query it (@steveoh)
  • Validate that AGRC or applications widgets do not reference it (@stdavis)

Notification

- [ ] Blog post (assigned to)

Add Geochronology layers from UGS to agol

Summary

  • Proposed Dataset Name: NA
  • Proposed ArcGIS Online Name: Utah Geochronology Cosmogenic, Utah Geochronology Fission Track, Utah Geochronology Rubidium Strontium, Utah Geochronology Tephrochronology, Utah Geochronology Tritium, Utah Geochronology Uranium Thorium Lead
  • Proposed ISO Category: Geoscience
  • Data Description: Geochronology dating methods
  • Source Agency/Entity: UGS
  • Contact: Gordon Douglass
  • Update Frequency: As requested

Triage

  • Data Team Triage ()
  • Dev Team Triage Complete (assigned to)
  • Cadastre Team Triage ()

We are introducing data

The data was or will be added on 2020/09/01 to the following areas

- [ ] Internal SGID
- [ ] SGID10

  • ArcGIS Online

The data is high quality

  • Sweeper checks have run and passed
  • The minimum requirements for metadata are populated
  • The data complies with our domain rules

The data should propagate automatically to

  • ArcGIS Online
  • [ ] SGID10
  • [ ] Open SGID
  • Open data
    - [ ] SGID.META.ChangeDetection

References to the data need to be manually added to

We have verified the data is live

Notification

Deprecate BEMS

Is the data removal temporary or permanent?

  • Replaced with newer data
  • Historical data for archive
  • No longer relevant

Identify places where the data lives

  • ArcGIS Online
  • Internal SGID
  • External SGID
  • Google Drive
  • Open data
  • Mapserv
  • gis.utah.gov data pages
  • Stewardship doc and sgid-index

Is there a website?

http://mapserv.utah.gov/BEMS/

  • Is the source code on GitHub?
    https://github.com/agrc/BEMS
  • Should it be archived?
  • Should it be removed from the web server or show a static page with information?
  • Should it redirect somewhere else?

Is there a map service?

  • Should it be stopped or deleted?

Is there a forklift pallet?

  • Should it continue to run or be removed?

Are there service dependencies?

  • Does the web api query it?
  • Do AGRC or applications widgets reference it?

Remove "Utah Land Ownership (SITLA)" from AGOL (AGRC org)

Summary

Now that we have added SITLA's AGOL Item to our Open Data site it's time to deprecate our item which actually just points at SITLA's feature service.

One possible issue: Is it a big deal that when someone searches for "Land Ownership" in just our content, they would get nothing? For example https://utah.maps.arcgis.com/home/search.html?q=land%20ownership

Triage

Remove data from the following areas

  • ArcGIS Online (assigned to)
    - [ ] Internal SGID (assigned to)
    - [ ] SGID10 (assigned to)
    - [ ] Open SGID (assigned to)
    - [ ] Google Drive (assigned to)
    - [ ] Open data (assigned to)
    - [ ] Mapserv (assigned to)
    - [ ] Retire application-specific prod and test SQL Databases (assigned to)

Copy data to the following areas

  • Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
  • Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
  • Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

  • gis.utah.gov data pages (assigned to)
  • Stewardship doc and sgid-index (assigned to)
  • SGID.META.AGOLItems (@stdavis)
  • AGRC_Shelved/AGOLItems_Shelved (in AGOL) (assigned to)
    - [ ] SGID.META.ChangeDetection (assigned to)
    - [ ] Backseat Driver (assigned to)

Notification

  • Blog post (assigned to)
  • Twitter (@steveoh)
    • Intent
    • Completed

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.