[gis_info] March 2016 Oregon GIS Framework Newsletter

BURCSU Theresa * DAS Theresa.BURCSU at oregon.gov
Mon Mar 28 13:58:06 PDT 2016


This quarter's newsletter is available. If you have trouble viewing it here, please find it on the GEO website:
http://www.oregon.gov/geo/FIT%20Documents/March%2c%202016%20Framework%20Newsletter.pdf




[cid:image001.jpg at 01D188F8.C7443CE0]


[cid:image002.jpg at 01D188F8.C7443CE0]

[cid:image003.jpg at 01D188F8.C7443CE0]


[cid:image004.jpg at 01D188F8.C7443CE0]

[image005.jpg at 01D188F8]
Oregon GIS Framework Newsletter



March 2016                                                                                                                                  Volume 2, Number 1



Welcome to the Spring 2016 issue of the Oregon GIS Framework Newsletter. This quarterly newsletter presents a summary of recent GIS Framework related activities as well as a schedule of upcoming events.







In This Issue...





* GEO website redesign

* Framework Forum recap

* Recently added/updated data to OSDL


* Defining authoritative data

* Recent FIT activities




* Upcoming FIT meetings

* A few words from the coordinator










Featured: GEO Website Redesign




[The Geospatial Enterprise Office (GEO) rolled out a new website on March 16 as part of the Department of Administrative Services' (DAS) new public website. More than a design update, the new site was organized around the tasks visitors can accomplish using the site. Accessibility and mobile device connectivity were also improved.  The new site resulted from nearly a year of work by staff from GEO and other DAS divisions. Josh Tanner led the GEO effort, participating in a cross-functional team that analyzed web traffic on the old site, determined what information to keep and what to archive, wrote fresh content in plain language, and reorganized content from the user's perspective. The resulting site has fewer pages and improved access to pages with the heaviest traffic. One change to the site is how meeting notes are accessed by site users. In the past, links for meeting notes led directly to the document, in most cases. We have reorganized meeting notes on the storage side, and links to meeting notes now lead to an FTP directory that is organized by group, such as Elevation FIT, and by year.  There was a hiccup in the routing of our http://gis.oregon.gov domain, so if you have troubles accessing the site, please try the permanent URL, http://www.oregon.gov/GEO. Also, please know that the underlying directory structure for the website has been completely overhauled, so old links will need to be checked and refreshed on your sites and in documents. We have worked to move the highest traffic and most important information to the new site, but if you find that something is missing or you simply cannot find what you are looking for, please let us know]

[The Geospatial Enterprise Office (GEO) rolled out a new website on March 16 as part of the Department of Administrative Services' (DAS) new public website. More than a design update, the new site was organized around the tasks visitors can accomplish using the site. Accessibility and mobile device connectivity were also improved.  The new site resulted from nearly a year of work by staff from GEO and other DAS divisions. Josh Tanner led the GEO effort, participating in a cross-functional team that analyzed web traffic on the old site, determined what information to keep and what to archive, wrote fresh content in plain language, and reorganized content from the user's perspective. The resulting site has fewer pages and improved access to pages with the heaviest traffic. One change to the site is how meeting notes are accessed by site users. In the past, links for meeting notes led directly to the document, in most cases. We have reorganized meeting notes on the storage side, and links to meeting notes now lead to an FTP directory that is organized by group, such as Elevation FIT, and by year.  There was a hiccup in the routing of our http://gis.oregon.gov domain, so if you have troubles accessing the site, please try the permanent URL, http://www.oregon.gov/GEO. Also, please know that the underlying directory structure for the website has been completely overhauled, so old links will need to be checked and refreshed on your sites and in documents. We have worked to move the highest traffic and most important information to the new site, but if you find that something is missing or you simply cannot find what you are looking for, please let us know]


[The Geospatial Enterprise Office (GEO) rolled out a new website on March 16 as part of the Department of Administrative Services' (DAS) new public website. More than a design update, the new site was organized around the tasks visitors can accomplish using the site. Accessibility and mobile device connectivity were also improved.  The new site resulted from nearly a year of work by staff from GEO and other DAS divisions. Josh Tanner led the GEO effort, participating in a cross-functional team that analyzed web traffic on the old site, determined what information to keep and what to archive, wrote fresh content in plain language, and reorganized content from the user's perspective. The resulting site has fewer pages and improved access to pages with the heaviest traffic. One change to the site is how meeting notes are accessed by site users. In the past, links for meeting notes led directly to the document, in most cases. We have reorganized meeting notes on the storage side, and links to meeting notes now lead to an FTP directory that is organized by group, such as Elevation FIT, and by year.  There was a hiccup in the routing of our http://gis.oregon.gov domain, so if you have troubles accessing the site, please try the permanent URL, http://www.oregon.gov/GEO. Also, please know that the underlying directory structure for the website has been completely overhauled, so old links will need to be checked and refreshed on your sites and in documents. We have worked to move the highest traffic and most important information to the new site, but if you find that something is missing or you simply cannot find what you are looking for, please let us know]


[The Geospatial Enterprise Office (GEO) rolled out a new website on March 16 as part of the Department of Administrative Services' (DAS) new public website. More than a design update, the new site was organized around the tasks visitors can accomplish using the site. Accessibility and mobile device connectivity were also improved.  The new site resulted from nearly a year of work by staff from GEO and other DAS divisions. Josh Tanner led the GEO effort, participating in a cross-functional team that analyzed web traffic on the old site, determined what information to keep and what to archive, wrote fresh content in plain language, and reorganized content from the user's perspective. The resulting site has fewer pages and improved access to pages with the heaviest traffic. One change to the site is how meeting notes are accessed by site users. In the past, links for meeting notes led directly to the document, in most cases. We have reorganized meeting notes on the storage side, and links to meeting notes now lead to an FTP directory that is organized by group, such as Elevation FIT, and by year.  There was a hiccup in the routing of our http://gis.oregon.gov domain, so if you have troubles accessing the site, please try the permanent URL, http://www.oregon.gov/GEO. Also, please know that the underlying directory structure for the website has been completely overhauled, so old links will need to be checked and refreshed on your sites and in documents. We have worked to move the highest traffic and most important information to the new site, but if you find that something is missing or you simply cannot find what you are looking for, please let us know]









Framework Forum Held in Portland in December




As a result of Bob DenOuden's departure as Framework Coordinator, there were only a few major happenings in the Framework Program during the fall and winter. Despite the huge void left by Bob, the Framework Forum was held on December 14, 2015 in Portland at Metro. Don Pettit discussed the Preparedness FIT's ongoing work to populate a geodatabase of over 250 data sets. A review of the team's data catalog suggested that some data sets should be considered restricted, for official use only. Tanya Haddad reviewed a proposal by the newest FIT, the Coastal/ Marine FIT, for a mean high water shoreline Framework data element. Eric Brandt and Steve Lucker discussed their ideas for producing a land use Framework data element, and Janine Salwasser, David Mather, and Nick Seigel reviewed some potential out

comes of the Oregon Spatial Data Library redesign effort funded through the Framework Data Development program.
In the second half of the day, Randy Sounhein presented the latest iteration of the Authoritative Data white paper. See "Defining Authoritative Data" below for more on this topic. Cy Smith, State Geospatial Information Officer, reviewed efforts from 2015 to prioritize Framework data. Cy also reviewed the data sharing legislative concept that became House Bill 4056 in the 2016 legislative session. See "Other Recent Framework Activities" below for more information. Bob Harmon briefed the forum participants on vertical integration of transportation and hydrography Framework data and where work is needed from the perspective of the Hy

drography FIT.  Cy once again took the stage, this time filling in for Brady Callahan, the new Imagery FIT lead, to review statewide aerial imagery requirements identified through a survey of local, county, and state governments and agencies. The survey was still out at the time. Please see "Other Recent Framework Activities" for more information on the state imagery contract work effort. Cy also discussed Framework data stewardship, emphasizing the need for horizontal and vertical stewardship for the full data life cycle. Efforts to develop Framework data stewardship plans have so far resulted in only about a handful of plans. However, stewardship is essential to sustaining the excellent Framework data developed to date.
The next forum will be held in June.











Framework Data Recently Added or Updated to OSDL




* Oregon Urban Growth Boundaries (2015)<http://spatialdata.oregonexplorer.info/geoportal/catalog/search/resource/details.page?uuid=%7B394740B8-FFFC-44A7-8B37-47CA03ACB34A%7D>
* Oregon City Limits (2015)<http://spatialdata.oregonexplorer.info/geoportal/catalog/search/resource/details.page?uuid=%7B53E5B569-191F-48D2-8BE9-CD4EE7C23F4B%7D>
* Oregon Mileposts (2014)<http://spatialdata.oregonexplorer.info/geoportal/catalog/search/resource/details.page?uuid=%7B35DEFD13-0A39-4981-ACEE-60DBEB2E469A%7D>

* Oregon Highway Network (2014)<http://spatialdata.oregonexplorer.info/geoportal/catalog/search/resource/details.page?uuid=%7B4A853763-4514-4876-AC91-35AEC76EB0DE%7D>
* Oregon Railroads (2015)<http://spatialdata.oregonexplorer.info/geoportal/catalog/search/resource/details.page?uuid=%7BCFA08D7A-CE6A-4467-89C2-ACB987967549%7D>
* Oregon Signed Routes (2014)<http://spatialdata.oregonexplorer.info/geoportal/catalog/search/resource/details.page?uuid=%7B5C0DF072-6A99-4613-ACAF-600C630A5109%7D>










Defining Authoritative Data




The GIS Program Leads (GPL) produced a white paper in 2015 to help define the concept of authoritative data within the GIS community. The paper identified three flavors of authoritative data: Framework data, rational authoritative data, and expert authoritative data. It also discussed the concept of trusted data. Each of these types of data are used for conducting business in many organizations and government levels. The reasons for their widespread use and authority vary.
In the white paper, Framework data was described as being accepted as authoritative due to the standards and stewardship of the data. Rational authoritative data are accepted and used as a result of formal vehicles such as origination from an authority (like a professional agent or agency) recognized in statute, ordinance or other legal vehicle. Expert authoritative data are accepted and used based on normative processes like trust in the expertise of the originators. Trusted data are compiled data sets that may originate from a variety of data sources, including

authoritative sources, and have gained acceptance and use through trust in the compiler and other norms. Framework data may also be rational or expert authoritative data, and may also fall into the category of trusted data.
GEO has been working to more clearly identify Framework data sets as authoritative data and increase their visibility. One approach GEO is taking to address these goals is to develop a process that provides the Oregon Geographic Information Council (OGIC) with the opportunity to officially identify and accept Framework data sets as authoritative. GEO put together a proposed process for identifying and accepting Framework data as authoritative. This acceptance approach includes multiple opportunities to review similar data sets and sources to land on the right data set. The Policy Advisory Committee (PAC) and OGIC have reviewed the proposed process. If you would like to review the process, please contact Theresa Burcsu (theresa.burcsu at oregon.gov<mailto:theresa.burcsu at oregon.gov>) or Cy Smith (cy.smith at oregon.gov<mailto:cy.smith at oregon.gov>).
The second approach to increase the

clarity of Framework data as authoritative relies on the Oregon Spatial Data Library (OSDL) and its role in connecting data seekers to data. In particular, GEO and OSDL have been working to distinguish among authoritative data sources, especially Framework data, and other data sources through a symbol or rating system on OSDL. Some of this work is being accomplished as part of the Framework Data Catalog Work Group (see "Other Recent Framework Activities" below).
At the recent Framework Forum, a lively conversation about the term "authoritative" took place and whether it conflicts with current state statutes defining professional surveyors and engineers as authorities and therefore authoritative data originators. Forum participants made it clear that more conversations were needed to understand the use of the term in the context of Framework data, so that the concept of authoritative data could be drawn upon and expanded as needed.










Other Recent Framework Activities



Work on the State of Oregon's imagery contract has continued under the lead of the Imagery FIT, and in fall 2015, user input and requirements were gathered. Through that process it became apparent that there is a need for both statewide medium resolution data, nominally at 1-ft resolution, and regional high resolution data at 6-in resolution. The Imagery FIT members have been discussing options for acquiring medium resolution data through vendors such as Hexagon, Google, Quantum, and Harris. They have also been exploring how to form regional partnerships that would make the acquisition of high resolution data easier. Oregon is scheduled to be part of the 2016 NAIP acquisition which will be 1-m resolution. After the data is available, the Imagery FIT will coordinate getting a copy of the data and providing it to users in Oregon Lambert.
The data sharing legislative concept was assigned House Bill number 4056 (HB 4056) and sponsored by Representative (and geographer) Nancy Nathanson. The bill is about sharing of geospatial Framework data with all public bodies. HB 4056 was introduced by Rep. Nathanson and sponsored by the Joint Legislative Committee on Information Management and Technology (JLCIMT). An informational hearing was held on February 26. Various sectors of the geospatial community raised significant concerns. To address the concerns, the JLCIMT and State CIO are establishing a joint work group to develop a revised legislative concept for

the 2017 session. The work group is composed of representatives from local, state, and federal organizations and will hold its first meeting April 8, 2016, with subsequent meetings approximately every 6 weeks until mid-November, 2016.
The Land Use Land Cover FIT hosted a scoping workshop to discuss the possible directions and participants in a Land Use Workgroup on February 29. Please contact Eric Brandt (ebrandt at lcog.org<mailto:ebrandt at lcog.org>) and Steve Lucker (stephen.lucker at state.or.us<mailto:stephen.lucker at state.or.us>) to join the effort or learn more.
The Hazards FIT met on March 4 and discussed the next steps for the team, including how to create a one-stop shop for hazards data and how to convey the best and most responsible use of available hazards geospatial data. Please contact Steve Lucker for more information.
The Preparedness FIT also met on March 4 and continued to work through issues related to public and 'official use only' data, as well as review its collaborative workspace on GovSpace. GovSpace is accessible to anyone, but requires a log in and password. For information on its use or the Preparedness FIT, please direct your questions to Don Pettit (PETTIT.Don at deq.state.or.us<mailto:PETTIT.Don at deq.state.or.us>).
The Framework Data Catalog Work Group met in February and on March 15. This work group is endeavoring to improve online access to Framework data on the Oregon Spatial Data

Library (OSDL) through a redesign of the web site. As part of the redesign, the OSDL team will be constructing data collections. Data collections are curated groupings of data and information that are anticipated to be excellent organizational and data-serving tools for the data elements in Framework themes as well as related, but non-Framework data. The group's work also relates to several other projects, including the Voyager pilot project, work by Lane Council of Governments on metadata tools, and improving geospatial data management between GEO and OSDL. The work group has determined that it will continue to use Esri's Geoportal for Framework data management and access as an interim solution. A more thorough review of other solutions will be completed in the next 18 to 24 months. Please contact Janine Salwasser (Janine.Salwasser at oregonstate.edu<mailto:Janine.Salwasser at oregonstate.edu>) to discuss FIT data collections or other aspects of the work group.
OGIC met on March 16.
Notes from the meetings mentioned above will be posted on the new GEO website using the new FTP format. Find links to them on the groups' new GEO web pages.

Upcoming FIT Meeting
FIT Leads
March 31
1:00 to 3:00 PM
635 Capitol St. NE
Salem, OR 97301









A few words from the coordinator...



Since my introduction at the Framework Forum in December and my full-time start in January, I have spent considerable time studying the Framework program: getting to know its vision and goals, meeting many of the movers and shakers, working to understand how the program's important work is accomplished, and understanding the broader, national framework context. The journey has shown me an expansive effort that includes many people and many geospatial data needs, and is heavily dependent on the dedication of everyone involved.
Among my first tasks on the job was to meet all of the FIT leads in person or by telephone. My intention for those meetings was to get to acquainted with these

leaders and learn about the challenges and opportunities of each FIT. Each leader shared useful and creative ideas. For example, one leader identified interest in holding a data forum or fair to help users connect with data originators. It is my hope that we will identify more opportunities and chart out how to take advantage of them when the leaders and I meet on March 31.
During my first year, I look forward to focusing a majority of my time on the work my predecessors started by collaborating with the FIT leads. Together I hope we will formulate strategies and plans for accomplishing the priority work needed; move forward fundamental aspects of the Framework Program, such as stewardship; and identify new

opportunities for growth. I will also begin to take over the Framework Development Program contracts and work with the JLCIMT data sharing work group. One of my first year goals is to meet as many of you as possible and learn your thoughts on Framework. As I may not know who you are, please introduce yourself when the opportunity arises. I will be at the GIS in Action conference in Portland in April, and other meetings and events throughout the year. I very much look forward to meeting you and having a very interesting first year.
Theresa Burcsu
Oregon Framework Coordinator












Contact Us






Geospatial Enterprise Office URL: http://gis.oregon.gov<http://gis.oregon.gov/>


Framework Coordinator: theresa.burcsu at oregon.gov<file:///C:\local_files\work\FIT\newsletters\bob.denouden@oregon.gov>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1021 bytes
Desc: image001.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1224 bytes
Desc: image002.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 2199 bytes
Desc: image003.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 2048 bytes
Desc: image004.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 1790 bytes
Desc: image006.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 1892 bytes
Desc: image007.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 69884 bytes
Desc: image008.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.jpg
Type: image/jpeg
Size: 9072 bytes
Desc: image009.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 48836 bytes
Desc: image010.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.jpg
Type: image/jpeg
Size: 18754 bytes
Desc: image011.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0009.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.jpg
Type: image/jpeg
Size: 1911 bytes
Desc: image013.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0010.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.jpg
Type: image/jpeg
Size: 1895 bytes
Desc: image015.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0011.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.jpg
Type: image/jpeg
Size: 1669 bytes
Desc: image016.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0012.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image017.jpg
Type: image/jpeg
Size: 1655 bytes
Desc: image017.jpg
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment-0013.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 923 bytes
Desc: image005.png
URL: <https://omls.oregon.gov/pipermail/gis_info/attachments/20160328/a11248b0/attachment.png>


More information about the gis_info mailing list