2017 ORS 368.081¹
Requirements for petition to initiate road proceedings
  • fees

(1) A petition to initiate proceedings under ORS 368.073 (Initiation of proceedings to acquire property for road purposes) must contain all of the following:

(a) A statement of the public necessity for the public road.

(b) A description of the proposed public road.

(c) A list containing the names and mailing addresses of any owner of property that:

(A) Is proposed to be acquired for the public road;

(B) Abuts the proposed public road; or

(C) Would otherwise be affected by the proposed acquisition of property for the public road.

(d) The signatures and mailing addresses of a majority of the owners of property that would abut the proposed road.

(2) The petition described under this section is subject to the following:

(a) Where a signature from an owner is required, the signature of an owner of property that has multiple ownership is valued as a fraction of an owner signature for that property in the same proportion as that owner’s interest in the property bears to the interest of all other owners of the same property.

(b) Any person signing the petition may withdraw the signature by filing a written withdrawal with the county governing body.

(c) A signature that is required on the petition does not qualify for purposes of the petition if the signature is withdrawn or if the person whose signature appears on the petition files an objection under ORS 368.091 (Owners’ rights to terminate road proceedings).

(3) A county governing body may establish and require payment of a fee for the filing of a petition under this section. [1981 c.153 §11]

1 Legislative Counsel Committee, CHAPTER 368—County Roads, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors368.­html (2017) (last ac­cessed Mar. 30, 2018).
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.