Description: This data is built from a query of Accela data related to hearing records. The polygons are either from our own subdivision layer we keep in-house for modelling and other purposes; or from a layer with the legal descriptions of annexations and rezones, or from a layer called App History that contains other polygons for planning related applications. If no polygon is found matching an Accela record in any of those layers, the record is assigned a generic polygon (giant question mark) so that it can still show up without causing errors when publishing. You can see all those that we don't have a shape for by selecting the giant question mark. It is anticipated that we will be able to improve the completeness of this over time. Not only by the number of records having an actual polygon increasing but by better data entry in Accela that will provide better counts of lots etc. NOTE: the lot and unit counts are from the original record in Accela. No math is being done to reduce the number of lots and units from the original plat as we cut small chunks out of it with final plats and other applications. That's why whis is called "SOURCE". It is to be used as a visual method for a human doing that kind of analysis since we don't have a programmatic way to do it at this point. We also don't yet have a way to determine which ones are expired. It is simply intended that this would reduce the amount of time needed to research and produce a valid entitlements layer.
Description: This information is intended to provide stakeholders with access to development information for projects with hearing level applications. This layer serves as a simple nexus between stakeholders understanding of a pending projects general area, and a means to find additional information without knowing a project ID or name. The shapes shown are simple polygons that represent impacted parcels, and are not surveys or legal descriptions.Important fields are:App_ID - The project ID for which noticing is shown and a means to search for additional information in the City's online database (Searchable Documents).Name - This is the official name of the project.Planner Name - This is the name of the staff planner assigned to the project.Weblink - This is a direct link to the project folder where all relevant information is stored. Applications, public comments, public notices, resolutions, and all other information is included.App Level - This indicates whether an application is a public hearing or staff level approval. Initiatlly at least, staff level approvals are not shown.Active Project - A "Y" indicates that an application has not been approved or denied. A 'N" indicates the project has been approved or denied. The final determination may be found in the project folder.
Description: Polygons are created using COGO tools based on legal descritions provided by Surveyors. Items are entered here prior to being recorded. Any record here without a Recorded Number and Ordinance Number is not a valid ordinance record. Even after the