Alley widths/ street frontages were captured during the vector property effort and reside in their own feature class. 99% of the time, these features should be coincident with the square boundary. The exceptions to this are internal alley’s that might be overlaid by a tax lot. They were captured largely to enable continuity within each square.
Alley Polygon does not exist. They could be created with this data by using an automated routine which searches linear feature of the Record, Tax and Parcel Lots feature classes where Line_Classification = 3, 4 and 6, then turning these selected lines into poly’s, another method would be clipping a square boundary with the tax and record lots.
These are lines beyond which property owners or others have no legal or vested rights to extend a building or any part thereof without approval of the proper authorities; ordinarily a line of demarcation between public and private property, but also applied to a building restriction line, when recorded in the records of the Surveyor.
**These features were captured only if they appeared on subdivision plats of active record lots. It is known that not all building restriction lines were capture during this effort.
There are lines that occurred on the city’s 1901-1905 set of master plans for all proposed roads. If a highway planning line crosses a particular property, that land cannot become a Record Lot by subdivision, even if the proposed street is no longer needed or will never be built. However there is a procedure through which a proposed road can be removed from the Highway Plan freeing up affected land for subdivision or development.**These features were captured only if they appeared on subdivision plats of active record lots. It is known that not all highway planning lines were captured during this effort and their accuracy can not be verified.
These are not to be confused with utility or private easements. They are often placed after an alley closing for traffic or access.**These features were captured only if they occurred on subdivision plats of active record lots. It is known that very few of these were captured during this effort and their accuracy can not be verified.
Integrated Tax System (ITS) - * this is a database of OTR-RPTA, not a layer in the Vector Property GDB
A database used for sending tax bills, also known as tax assessment roll. ITS stores comprehensive tax information such as ownership, mailing addresses etc of record lots, tax lots, parcels, condominiums and federally owned lands such as reservations and appropriations. The ITS database also processes notices and tax bills. The linkage from the Vector Property layers to this database is SSL (Square, Suffix, and Lot).
It should be noted that not all record lots have a direct 1:1 relationship to information in this database. The most obvious examples would be when a tax lot was created from existing record lots. In this case, only the tax lot would have linkage to the ITS database, not the underlying record lots (although they still exist). Another example would be reservations that have been converted into tax lots. The reservation still exists, however for taxation purposes it is referred to as a tax lot and has corresponding linkage to ITS.
Computer Assisted Mass Appraisal (CAMA) System - * this is a database of OTR-RPTA, not a layer in the Vector Property GDB
This system is comprised of an oracle database and software (Vision Appraisal) that assists with appraising properties. CAMA system stores characteristics of properties such as use code, assessor number and valuation information (income, cost and market value). It was installed and taken live in year 2001. Linkage from CAMA to Vector Property layers is by SSL (Square, Suffix, and Lot). CAMA also interacts nightly with ITS for updates.