2007 ORS 390.065¹
Findings
  • use of Oregon State Lottery proceeds

The Legislative Assembly finds that:

(1) Expenditures by visitors to Oregon state parks and by employees of the State Parks and Recreation Department currently contribute approximately $549 million each year to local economies throughout Oregon. The acquisition, development, improvement, upgrading, preservation and expansion of the capacity of facilities of the system of state parks, including parks, park facilities, ocean shores, scenic waterways, trails and historic sites in the State of Oregon, do and will accomplish the purpose of creating jobs and furthering economic development in Oregon by:

(a) Increasing the capacity, usefulness and attractive qualities of public recreational facilities, thereby promoting travel and tourism in Oregon;

(b) Generating business for and supporting the operations and prosperity of businesses located in the areas of the public recreational facilities; and

(c) Creating employment opportunities within this state through the funding of development and improvement projects on which workers will be employed.

(2) Based on the findings made in this section, the use of the net proceeds from the operation of the Oregon State Lottery to fund state park projects and to pay state park lottery bonds described in ORS 390.063 (Lottery bonds for state park projects) is an appropriate use of state lottery funds under section 4, Article XV of the Oregon Constitution, and ORS 461.510 (State Lottery Fund). [1997 c.800 §2; 1999 c.44 §23]

Note: See note under 390.060 (Definitions for ORS 390.060 to 390.067).

1 Legislative Counsel Committee, CHAPTER 390—State and Local Parks; Recreation Programs; Scenic Waterways; Recreation Trails, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­390.­html (2007) (last ac­cessed Feb. 12, 2009).
 
2 OregonLaws.org contains the con­tents of Volume 21 of the ORS, inserted along­side the per­tin­ent statutes. See the preface to the ORS An­no­ta­tions for more information.
 
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.