Laserfiche WebLink
<br />. Data from field observation. <br /> <br />The data identified as coming from existing internal databases are of low <br />cost and high value to the project. These data were generally obtained as exported <br />tables from the Regional Land Information Database (RLID) or Assessment and <br />Taxation (A&T) database. <br /> <br />The data identified as coming from existing external databases include data <br />from the State of Oregon Employment Department and other potential sources <br />including EWEB. Information that may come from existing external databases <br />include "onsite services." The T AC decided to not include any of these variables <br />due to a range of issues related to the data. <br /> <br />Both the internal and external databases are electronic compilations of data in <br />formats that can be readily imported. The main distinction we are making is that <br />the internal data comes from LCOG (internal in the sense that LCOG has already <br />compiled it and vetted it to a certain degree for Lane County), while the external <br />data could come from other agencies or even private sources. <br /> <br />The data identified as coming from GIS analysis range from low-medium to <br />high cost and are generally of high value to the project. Data coming by way of <br />GIS analysis required combining several existing GIS datasets using spatial <br />analysis methods to produce new datasets. The distinction here is that we had to <br />do some processing (GIS analysis) of internal or external data to create derived <br />data. For example, data addressing a development consideration like wetlands was <br />intersected with tax-lot polygon data with wetland polygon data to produce tables <br />identifying which lots contain wetland constraints, the size of the constraint, the <br />percentage of the lot constrained, etc. Data addressing proximity questions was <br />calculated using distance deriving methods that relate tax-lot polygon data to <br />transportation corridors. <br /> <br />The data identified as coming from field observation will require either field <br />verification or possibly air photo interpretation. The T AC decided to skip the two <br />field observation data variables. <br /> <br />Table 2-1 summarizes the requested data characteristics, their sources, and <br />whether they were included in the database system. <br /> <br />DRAFT: Commercial and Industrial Lands Database <br /> <br />ECONorthwest <br /> <br />July 2006 <br /> <br />Page 9 <br />