City Council Work Session - CANCELLED for technical issues


Return to the Search Page Return to the Agenda
  8.       
Meeting Date: 06/09/2020  
From: Dan Symer, Zoning Code Manager

TITLE
Case No. PZ-19-00124 Updates to Zoning Code 2019 - High Occupancy Housing Land Use Zoning Code Amendment.
STAFF RECOMMENDED ACTION:
Hold a work session to allow the City Council and the public to ask questions, seek clarification, have discussions, and provide comments and direction to staff on the proposed amendment.
EXECUTIVE SUMMARY:
The purpose of the work session is to discuss and receive comments and direction on three considerations for the High Occupancy Housing (HOH) Zoning Code Text Amendment. Below is a summary of these considerations
  1. Definitions.  In accordance with the High Occupancy Housing Specific Plan (HOH Plan), staff is proposing to replace the Rooming and Boarding land-use with two new land-uses (Bullet 2 Page 102 of the HOH Plan). These proposed land-use definitions are the High Occupancy Housing Development (HOHD) and Mixed-Use High Occupancy Housing Development (MHOHD). A HOHD is a 100 percent residential development, and a MHOHD is a mixed-use development that contains residential and non-residential uses. According to the City Council direction received on October 8, 2019, these definitions describe which single-family, two-unit/duplex, multiple-family (including triplex) and mixed-use developments would be considered HOH. Refer to the Information I.A. section of this report for a list of questions that staff would like the City Council to consider regarding the proposed definitions. Staff’s explanation of the proposed HOHD and MHOHD is incorporated in the Information III. Discussion section of this report.
  2. Zones that the HOHD and MHOHD are proposed to be allowed.  To accommodate both small- and large-scale HOH development, and to replace the Rooming and Boarding land use throughout the Zoning Code, the HOHD and MHOHD land uses are proposed to be allowed in multiple zones. The HOHD land use is proposed to be allowed in all residential and commercial zones, and the T3 Neighborhood I (T3N.1) through, and including, the T6 Downtown (T6) zones. The MHOHD land-use is proposed in all commercial zones and the T5 Main Street (T5) and T6 Downtown (T6) zones. Refer to Information I.B. section of this report for a list of questions that staff would like the City Council to consider regarding the zones that the proposed land-uses would be allowed. Staff’s explanation pertaining to which zones the proposed HOHD and MHOHD land-uses are incorporated, is included in Information IV. HOHD and MHOHD Land-use By Zone section of this report.
  3. Required and Maximum dwelling unit types.  Staff is seeking City Council direction regarding considerations received pertaining to the incorporation of provisions that would require a multiple-family (three dwelling units or more) HOH development to have a minimum number of studio and one-bedroom dwelling units and a maximum number of four-bedrooms or more dwelling units.  For example, a minimum of 20% of the total dwelling units shall be studio and one-bedroom units, and a maximum of 30% of the dwelling units shall be four-bedrooms or greater. Refer to the Information I.C. section of this report for a list of questions that staff would like the City Council to consider regarding this topic.
INFORMATION:
I. City Council Questions:
For your reference, below is a general overview of the questions that staff is seeking the City Council’s comments and direction.
A. Questions regarding the definitions: 
  • Are the proposed definitions clear and easily understood?
  • Do the proposed definitions satisfactorily define a HOH development?
  • Do the proposed definitions address the Council’s concerns regarding developments with units that contain a high number of bedrooms, and a bedroom-to-sanitation facility (bathroom see definition below) ratio of 1:1?
  • Should there be a maximum bedroom limit on any one dwelling unit without obtaining a Conditional Use Permit for a High Occupancy Housing Development?
  • Is the total number of bedrooms, six, in a two-unit development appropriate, or should it be increased?
  • Does the City Council have any recommended modifications or considerations?
B. Questions pertaining to the Zones that the HOH land-uses are proposed to allowed
  • Should the HOH land-uses be excluded from any zone?
  • Does the City Council have any recommended modifications or considerations?
C. Questions pertaining to requiring a minimum and maximum number of dwelling unit types (e.g., studio, one-bedroom, four-bedrooms, etc.)
  • Does the City Council desire to incorporate a minimum number of studio and one-bedroom dwelling units, and maximum number four-bedrooms and greater dwelling units?
  • If the City Council desires to incorporate the aforementioned provisions, which type(s) of HOH developments should these provide apply to? For example, should the provisions apply to developments that exceeds 29 dwelling units per acre and/or 72.5 bedrooms per acre. 
For your convenience, the relevant questions have been restated within the staff’s discussion below. Some have been slightly modified to address the discussion topic specifically.
 
II. Background Summary:
In February 2018, the City Council adopted the citywide High Occupancy Housing Specific Plan (HOH Plan). The HOH plan was developed in response to the community's dialogue about previously proposed high intensity, mid-rise developments near historic neighborhoods that primarily catered to college students. The plan is intended to provide direction in the form of goals and policies to accommodate a variety of housing options in areas of the city that can support infill, redevelopment, and mixed-use activities.  In addition, the plan’s goals and policies address enhancing and maintaining the city’s character and provide guidance for future developments that would be considered High Occupancy Housing (HOH). It should be noted that the HOH Plan’s listed implementation strategies pertaining to the Zoning Code amendments (Pages 102, 103, 105 and 106 of the HOH Plan) “…may be accomplished through another method...” to achieve “…the goals and policies of the HOH Specific Plan and the Regional Plan.” (Page 99 of the HOH Plan). 
 
After the HOH Plan’s adoption, staff received direction and affirmation from the City Council on October 8, 2019, to address smaller developments that may also be considered as HOH developments. The smaller HOH developments that staff was directed to incorporate are single-family, two-unit (duplex), three-unit (triplex), and multiple-family developments that were not addressed in the HOH Plan. Typically, these smaller HOH developments have a high bedroom-to-dwelling unit ratio, a bedroom-to-sanitation facility ratio of close to 1:1, and are on small lots. A summation of the comments and information conveyed from staff, the public, City Council members, and Planning and Zoning Commission members is that these smaller HOH developments have an equal or greater impact on neighborhoods as the large-scale HOH developments have. Also, it was opined that the scale of these developments are inconsistent with the character of many of the existing neighborhoods and have a negative impact on the available public street parking. It should be noted that these structures are primarily near to downtown and Northern Arizona University, but a few have been constructed in other neighborhoods. 
 
For your reference, public input was received at the public meetings held on August 19, 2019, February 13 and 14, 2020, and through the City’s online Community Forum (https://www.opentownhall.com/portals/227/Issue_7685) (Attachment 4). In addition, staff received several comments regarding HOH developments from the Southside stakeholders group that was formed to assist in the development of the conceptual Southside specific plan. These meetings were held over the past year.
 
It should be noted that the HOH Plan did not contemplate addressing smaller HOH developments. For context, the HOH Plan defined a HOH development as any development that has at least 30 units or 75 bedrooms per acre (Page 2 and 110 of the HOH Plan).  When the HOH Plan was developed, the plan primarily focused on large scale developments.  Developments that were included in the HOH Plan analysis are the HUB, The Standard, Village at Aspen Place, Fremont Station, etc.

III. Discussion:
To address both large and small scale residential and mixed-use HOH developments, staff is in the process of developing two land-use definitions. These land-use definitions are titled High Occupancy Housing Development (HOHD) and Mixed-Use High Occupancy Housing Development (MHOHD). A HOHD is a 100 percent residential development, and a MHOHD is a mixed-use development that contains residential and non-residential uses. 
 
The primary purpose of the proposed definitions is to define the HOHD and MHOHD land-uses based on a development’s physical characteristics.  The physical characteristics approach is being considered due to the difficulties associated with enforcing the existing land-use definitions of the Zoning Code that include references to separate rental or lease agreements (Room and Boarding Facility), or separate sleeping and bathroom facilities that are rented for extended periods (Single Room Occupancy (SRO)). 
 
Below is the proposed definition of the bedroom-to-sanitation facility ratio and the existing Zoning Codes definition of the Sanitation Facility(ies).  These terms are utilized in the proposed HOHD and MHOHD.
  • Bedroom-to-Sanitation Facility Ratio: Is the total number of bedrooms divided by the total number of sanitation facilities in a dwelling unit.
Example:    1.    A dwelling unit has five bedrooms and four sanitation facilities.  The bedroom-to-sanitation facility ratio is:
5 bedrooms              
4 sanitation facilities = 1.25
  • Sanitation Facility(ies): A bathroom that contains any combination of, or individually, a toilet, shower, sink, tub, or related bathing and sanitation fixtures.
A. High Occupancy Housing Development (HOHD):
Due to the need to address different large and small HOH development types, similar land-uses, and different building forms, the proposed HOHD definition is split into separate sections.  These sections address: single-family, two-unit (duplex), three-unit (triplex), and four-units or greater developments.  The single-family, two-unit (duplex), and three-unit (triplex) would be allowed in any location within the City, and the proposed four-units or greater HOHD developments would only be allowed in the pedestrian shed of an activity center.
 
1. Single-Family Attached or Detached Dwelling Units
Based on the review of the known single-family developments that have a high bedroom-to-dwelling unit ratio, bedroom-to-sanitation facility ratio of 1:1, and are on small lots, it was determined that lots smaller than 10,000 square feet have a greater potential of the inability to provide sufficient parking if all individuals living in the dwelling unit have vehicles.  With the exception of older neighborhoods, most of the smaller lots may accommodate up to four cars parked in a garage and driveway.  Also, it should be noted that new single-family dwellings on smaller lots with more than four bedrooms are typically out of scale with the many existing neighborhoods.  The parking requirements for a typical single-family home is two spaces. For your reference, the conceptual Zoning Code parking requirements for a HOHD and MHOHD are included as Attachment 1.
 
Below is the proposed definition to determine if a single-family development would be considered a single-family HOHD.
 
a. A single-family attached or detached dwelling unit with five bedrooms or more:
i. On a lot or parcel containing 10,000 square feet or less; and
ii. Has a bedroom-to-sanitation facility ratio less than 1.2.
 

For your reference, a bedroom-to-sanitation facility ratio of 1.2 is a five-bedroom dwelling unit with four sanitation facilities.
 

Note:  Currently, the City’s process for applications for new single-family homes, additions, and modifications to existing homes do not require prior City review before the permit application is submitted.  Therefore, there will be a potential that an applicant will be informed of the Conditional Use Permit requirements and related provisions, such as parking, during the review of the permit application.  Since the Conditional Use Permit would need to be approved prior to staff approving a permit application, the process will be delayed.  Also, this information may occur after an applicant has spent money on construction documents and contractors.
 
City Council Questions:
  • Is the proposed definition clear and easily understood?
  • Does the proposed definition sufficiently address the Council’s concerns to include certain single-family developments with a high number of bedrooms and a bedroom-to-sanitation facility ratio of 1:1 as a single-family HOHD?
  • Does the Council have additional modifications or considerations?
2. A Lot or Parcel Containing Two or Three Dwelling Units (Inclusive of Duplexes and Triplexes).
Typically, small scale multi-dwelling unit developments have a higher number of bedrooms per dwelling unit.  As it pertains to two-unit and three-unit developments, staff’s analysis contemplates an allowance of 3 bedrooms per dwelling unit.  Therefore, a two-unit development would be allowed a total of six bedrooms, and a three-unit development would be allowed a total of nine bedrooms without a Conditional Use Permit. The proposed allowance is a slight increase (0.5 bedrooms per dwelling unit) over the bedrooms per dwelling unit contemplated in the HOH Plan for large scale HOH developments. 
 
In addition, staff’s analysis found that the bedroom-to-sanitation facility ratio of 1:1 is a common feature with one- and two-bedroom dwellings.  Also, the 1:1 ratio is prevalent in newer three-bedroom units of standard apartment developments.  This ratio is not common with units that contain four-bedrooms or greater in standard apartment developments.  But, the 1:1 ratio is common with developments either leased by the bedroom, by the unit with a “master” lease with multiple adult persons or are considered a HOH developments in accordance with the HOH Plan. Therefore, the proposed definition includes a provision that requires any two-unit, or three-unit development containing a four-bedroom or greater unit and has a bedroom-to-sanitation facility ratio less than 1.3 to be considered a HOHD.  For your reference, a four-bedroom unit with three sanitation facilities has a bedroom-to-sanitation facility ratio of 1:3.
 
a. Two-Dwelling Unit Developments
The following is the proposed definition to determine if a two-unit development would be considered a HOHD.
 
i. A lot or parcel containing two dwelling units, excluding an Accessory Dwelling Unit, with:
(a) More than a total of six bedrooms; or
(b) One or more dwelling units containing four or more bedrooms with a bedroom-to-sanitation facility ratio less than 1.3.

City Council Questions:
  • Is the proposed definition clear and easily understood?
  • Does the proposed definition address the Council's concerns to include a two-unit development with a bedroom-to-sanitation facility ratio of 1:1 and a high number of bedrooms in any one unit as a HOHD?
  • Should there be a maximum bedroom limit on any one unit without a Conditional Use Permit?  For example, no unit shall have more than five bedrooms without a Conditional Use Permit for a HOHD.
  • Two-unit developments are allowed in all residential zones, except the Manufactured Housing (MH) zone. The needs and concerns of the residents of one neighborhood may be different than another. For example, the residents of one neighborhood may have concerns regarding a two-dwelling unit development that contains more than six bedrooms; alternatively, to accommodate familial and/or economic needs, the residents of another neighborhood may be ok with a two-dwelling unit development containing eight bedrooms.  Is the total number of bedrooms, six, in a two-unit development appropriate, or should it be increased?
  • Does the proposed definition satisfactorily define a two-dwelling unit HOHD?
  • Does the Council have additional modifications or consideration? Please be advised that an accessory dwelling unit on a lot that contains a single-family dwelling unit is not considered a two-unit development.  This exclusion is intended to maintain an incentive to construct an accessory dwelling unit on all parts of a single-family development.
 
b. Three Dwelling Unit Developments
The following is the proposed definition to determine if a three-unit development would be considered a HOHD.
 
 
i.  A lot or parcel containing three dwelling units with:
(a) More than a total of nine bedrooms; or
(b) One or more dwelling unit(s) containing four or more bedrooms with a bedroom-to-sanitation facility ratio less than 1.3.

City Council Questions:
  • Is the proposed definition clear and easily understood?
  • Does the proposed definition address the Council's concerns to include a three-unit development with a bedroom-to-sanitation facility ratio of 1:1 and a high number of bedrooms in any one unit as a HOHD?
  • Should there be a maximum bedroom limit on any one unit without a Conditional Use Permit for a HOHD? i.e., For example, no unit shall have more than five bedrooms without a Conditional Use Permit for a HOHD.
  • Does the Council have any recommended modifications or considerations?
3. A Development Sites Containing Four or More Dwelling Units
The definition for a four or more dwelling units HOHD, contains three parts:
  1. The bedroom-to-sanitation facility ratio.
  2. The percentage of total dwelling units that contain four bedrooms or more.
  3. The total number of dwelling units per acre and bedrooms per acre that are allowed by a property’s zone. 
As it pertains to the bedroom-to-sanitation facility ratio, it was determined that the ratio that applies to two- and three-unit developments is also applicable to a development site containing four or more dwelling units.
 
Based on staff's Zoning Code scenario analysis of the HOH plan, it was determined that a development site containing four or more dwelling units could have a sizable bedroom-to-dwelling unit ratio and not require a Conditional Use Permit for a HOHD. Therefore, the proposed definition indicates that any development with more than 20 percent of the total dwelling units containing four-bedrooms or more would be considered a HOHD.
 
The maximum number of bedrooms, including the maximum number of dwelling units that these developments may have without a Conditional Use Permit for a HOHD, is addressed in the conceptual property development standards for each zone (Attachment 2) except for the Transect Zones.  Since the Transect Zones do not have the density and a maximum bedroom per acre development standards, and the HOH Plan does not specifically address the Transect Zones criteria, staff concluded that applicable HOH Plan criteria for High Density Residential (HR) zone also would apply to the Transect Zones. 
 
The following is the proposed definition to determine if a Development Site containing four or more dwelling units would be considered a HOHD.
 
a. A Development Sites containing four or more dwelling units where:
i. More than 20 percent of the total dwelling units have four bedrooms or more;
ii. One or more of the dwelling units containing four or more bedrooms has a bedroom-to-sanitation facility ratio that is less than 1.3; or
iii. The total number of dwelling units per acre, or bedrooms per acre, requires a Conditional Use Permit for a HOHD in accordance with the building form and property development standards of the property’s designated a Non-Transect Zone, or if the property has elected a Transect Zone the density is greater than 29 dwelling units per acre or 72.5 bedrooms per acre.
 
City Council Questions:
  • Is the proposed definition clear and easily understood?
  • Does the proposed definition address the Council's concerns to include four-unit developments with a large number bedroom-to-sanitation facility ratio of 1:1?
  • Should there be a maximum bedroom limit on any one unit without a Conditional Use Permit for a HOHD? i.e., For example, no unit shall have more than five bedrooms without a Conditional Use Permit for a HOHD.
  • Does the Council have additional modifications or considerations?
4. Other Similar Land-uses.
There are several land-uses that, based on their physical development characteristics, may be on occasion considered a HOHD, although they are separately regulated by the Zoning Code.  In addition, many of these land-uses have additional land-use specific regulations or defining characteristics that are different from a HOHD.  Therefore, the Congregate Care Facility, Dormitory, Fraternity or Sorority, Group Home, Single Room Occupancy, and Institutional Residential land-uses are expressly excluded from the HOHD definition.  This exclusion is intended to avoid conflicts and confusion.
 
The following is proposed to be included in the HOHD definition to exclude the above-referenced land-uses.
a.  A HOHD does not include a Congregate Care Facility, Dormitory, Fraternity or Sorority, Group Home, Single Room Occupancy, or any Institutional Residential Land-uses.
 
City Council Questions:
  • Is the proposed addition to the definition clear and easily understood?
  • Does the Council have additional modifications or considerations?
B. Mixed-Use High Occupancy Housing Development (MHOHD):
The use specific development standards of MHOHD are limited the to the pedestrian shed of any activity center. It should be noted that the Regional Plan anticipates that the pedestrian shed areas of an activity center are to be the most intensive commercial and residential areas within the city (RP 18.11 and 18.15). The location of the activity pedestrian shed areas are identified in Attachment 3. Due to the locational limitations and anticipated characteristics of the pedestrian shed of an activity center, staff concluded that the MHOHD definition does not need to include separate considerations based on the number of residential dwelling units.  
 
1. Mixed-Use developments
Except for the addition of non-residential uses and the number of dwelling units, the rationale to describe a HOHD containing four or more dwelling units (Information III.A.3.) also applies to the residential elements of a Mixed-Use Development.
 
The following is the proposed definition to determine if a Development Site containing a Mixed-Use Development would be considered a MHOHD.
 
a. A Mixed-Use development that contains:

i. More than 20 percent of the total dwelling units have four bedrooms or more;
ii. One or more of the dwelling unit(s) containing four or more bedrooms has a bedroom-to-sanitation facility ratio that is less than 1.3; or
iii. The total number of dwelling units per acre, or bedrooms per acre, requires a Conditional Use Permit for a MHOHD in accordance with the building form and property development standards of the property’s designated a Non-Transect Zone, or if the property has elected a Transect Zone the density is greater than 29 dwelling units per acre or 72.5 bedrooms per acre.
 
City Council Questions:
  • Is the proposed definition clear and easily understood?
  • Does the proposed definition address the Council's concerns to include four-unit developments with a large number bedroom-to-sanitation facility ratio of 1:1?
  • Should there be a maximum bedroom limit on any one unit without a Conditional Use Permit for a MHOHD? i.e., For example, no unit shall have more than five bedrooms without a Conditional Use Permit for a MHOHD
  • Does the Council have additional modifications or considerations?
IV. HOHD and MHOHD Land-use By Zone
As part of the HOH Plan strategies (Bullet 2 Page 102 of the HOH Plan), it was contemplated to remove the Rooming and Boarding land-use and incorporate the appropriate corresponding HOHD and MHOHD land-uses.  With the direction to incorporate smaller scale developments as part of the HOH Zoning Code Amendment, it is necessary to include the HOHD land-use in all of the residential zones that allows single-family developments on lots less than 10,000 square feet, two-unit/duplex developments, and multiple-family developments.  It should be noted that all HOHDs that contain four dwelling units or larger will be required to be in the pedestrian shed of an activity center.  MHOHDs will be allowed in all commercial zones.

The zones that the HOHD land-use is proposed to be allowed are identified below. High Occupancy Housing Developments and MHOHD are limited to the residential land-uses and associated requirements of the zone. These include single-family, two-unit/duplexes, and multiple-family developments. If one of the aforementioned uses is not a permitted use in the zone, then the associated HOHD would not be allowed.  For example, if a single-family development is not allowed by the property’s designated zone, then the single-family HOHD is not allowed.

A.    Proposed Zones That a HOHD Would Be Allowed.
Estate Residential (ER)
High Density Residential (HR)
Manufactured Housing (MH)
Medium Density Residential (MR)
Rural Residential (RR) 
Single-Family Residential (R1)
Single-Family Residential Neighborhood (R1N)
T3 Neighborhood I (T3N.1)
T3 Neighborhood 2 (T3N.2)
T4 Neighborhood 1 (T4N.1)
T4 Neighborhood 1 - Open (T4N.1-O)
T4 Neighborhood 2 (T4N.2)
T4 Neighborhood 2 - Open (T4N.2-O)
T5 Main Street (T5)
T6 Downtown (T6)
Central Business (CB)
Community Commercial (CC)
Commercial Service (CS)
Highway Commercial (HC)
Suburban Commercial (SC)

Notes:
  1. Single-family developments are allowed ihttps://agendaquick.flagstaffaz.gov/frs/agenda/images/save_text_box_off.gifn all the above residential zones, and the Community Commercial (CC), T3 Neighborhood I (T3N.1), T3 Neighborhood 2 (T3N.2), T4 Neighborhood 1 (T4N.1) T4 Neighborhood 2 (T4N.2), and T4 Neighborhood 2 - Open (T4N.2-O) zones.
  2. Two-unit/duplex developments are allowed in all the above residential and commercial zones (excluding Manufactured Housing (MH)), and in the T3 Neighborhood I (T3N.1), T3 Neighborhood 2 (T3N.2), T4 Neighborhood 1 (T4N.1), T4 Neighborhood 2 (T4N.2), and T4 Neighborhood 2 - Open (T4N.2-O) zones.
  3. Multifamily developments (three units or greater) are allowed in all the residential zones listed above, except the Single-Family Residential Neighborhood (R1N) and Manufactured Housing (MH) zones, in all commercial zones, and the above-listed transect zones.
B.    Proposed Zones That a MHOHD Would Be Allowed.
Central Business (CB)
Community Commercial (CC)
Commercial Service (CS)
Highway Commercial (HC)
Suburban Commercial (SC)
T5 Main Street (T5)
T6 Downtown (T6)
 
City Council Questions:
  • Should the HOH land-uses be excluded from any zone?
  • Does the Council have any recommended modifications or considerations?
V. Existing Developments with a Rooming and Boarding Conditional Use Permit
In accordance with the HOH Plan, the Rooming and Boarding land use will be a removed from the Zoning Code (Bullet 2 Page 102 of the HOH Plan).  Therefore, developments will no-longer be regulated by a lease structure.  In accordance with the HOHD and MHOHD land use definitions, developments will be regulated by their physical characteristics (e.g. density, bedrooms per acre, and bedroom-to-sanitation facility ratio).

Currently, there are two properties that have approved Conditional Use Permits for Rooming and Boarding.  These are located at 901 South O'Leary Street (The Commons at Sawmill) and 555 West Forest Meadows Street (Freemont Station).  Based on the location and the physical characteristics of the Commons at Sawmill, an 100% residential development, it will no-longer be regulated as a Rooming and Boarding development or a HOHD.  Also, Freemont Station will no longer be regulated as a Rooming and Boarding development, although its location and physical characteristics do conform to the provisions of MHOHD. Therefore, Freemont Station will be considered a “legal” non-conforming development.

VI. Required Minimum and Maximum Dwelling Unit Types.
Staff is seeking City Council direction regarding considerations received pertaining to the incorporation of provisions that would require a multiple-family (three dwelling units or more) HOH development to have a minimum number of studio and one-bedroom dwelling units and a maximum number of four-bedrooms or more dwelling units.  For example, a minimum of 20% of the total dwelling units shall be studio and one-bedroom units, and a maximum of 30% of the dwelling units shall be four-bedrooms or greater.

City Council Questions:
  • Does the Council desire to incorporate a minimum number of studio and one-bedroom dwelling units, and maximum number four-bedrooms and greater dwelling units?
  • If the Council desires to incorporate the aforementioned provisions, which type(s) of HOH developments should these apply to? For example, should the provisions apply to developments that exceeds 29 dwelling units per acre and/or 72.5 bedrooms per acre?

Attachments
Attachment 1 Conceptual High Occupancy Housing Parking Requirements
Attachment 2 Conceptual Property Development Standards
Attachment 3 Activity Center Map
Attachment 4 Public Comments
Staff Presentation


    

Level double AA conformance,
                W3C WAI Web Content Accessibility Guidelines 2.0

AgendaQuick ©2005 - 2024 Destiny Software Inc. All Rights Reserved.


Debugging Information
ColdFusion Server Standard 2016,0,16,320445
Template /agenda_publish.cfm
Time Stamp 19-May-24 09:03 AM
Locale English (US)
User Agent Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Remote IP 10.20.230.5
Host Name 10.20.230.5


Execution Time

Total Time Avg Time Count Template
266 ms 266 ms 1 D:/inetpub/PublicPages/agenda_publish.cfm
219 ms 219 ms 1 D:/inetpub/PublicPages/public/publish/agpub_agm_dsp.cfm
219 ms 219 ms 1 D:/inetpub/PublicPages/public/publish/ext_agpub_content.cfm
187 ms 187 ms 1 D:/inetpub/PublicPages/public/publish/include_ag_memo.cfm
62 ms 62 ms 1 D:/inetpub/PublicPages/public/publish/include_levels.cfm
31 ms 31 ms 1 D:/inetpub/PublicPages/public/publish/ext_agpub_top.cfm
16 ms 16 ms 1 CFC[ D:/inetpub/PublicPages/public/cfm_utilities/print_agenda.cfc | qryAI(4663, 0, Y) ] from D:/inetpub/PublicPages/public/cfm_utilities/print_agenda.cfc
16 ms 16 ms 1 D:/inetpub/PublicPages/agpub_client_defines.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/508_utilities.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/Application.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/agenda/agenda_utilities.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/agenda/aq_copyright.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/cfm_utilities/_methodQryAI.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/cfm_utilities/user_attr.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/cfm_utilities/utilities.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/publish/adv_search_selection.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/publish/customHeader.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/publish/ext_agpub_head.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/publish/include_set_fonts.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/publish/print_agm_expincl.cfm
0 ms 0 ms 1 D:/inetpub/PublicPages/public/publish/print_agm_ud.cfm
0 ms  STARTUP, PARSING, COMPILING, LOADING, & SHUTDOWN
266 ms  TOTAL EXECUTION TIME
red = over 250 ms average execution time


SQL Queries

chkForExtraFlds (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\agpub_client_defines.cfm @ 09:03:32.032
			select * from codes c where c.code_type = 'AddlSetup' and c.valid_code = 'SysSetup'
		
getTZOffset (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\agpub_client_defines.cfm @ 09:03:32.032
				select c.misc_alpha9 tz, c2.misc_alpha tz_offset
				from codes c
				left outer join codes as c2 on (c2.code_type = 'TIMEZONE' and c2.valid_code = c.misc_alpha9)
				where c.code_type = 'AddlSetup' and c.valid_code = 'SysSetup'
			
chkSite (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\agenda_publish.cfm @ 09:03:32.032
		SELECT dist_name FROM fasinfo
	
AddlSetup2 (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\agenda_publish.cfm @ 09:03:32.032
	SELECT misc_alpha6 subscribe_tab, misc_alpha7 officials_tab, misc_alpha8 ordinance_tab, misc_alpha9 resolution_tab, misc_alpha11 voting_tab, misc_alpha12 useTabs
	from codes where code_type = 'AddlSetup' and valid_code = 'SysSetup2'
codesFields (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\agenda\agenda_utilities.cfm @ 09:03:32.032
			select top 1 * from codes
		
meetingTypes (Datasource=frsRO, Time=0ms, Records=24) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
		SELECT mt.meeting_type, mt.descr, c.long_descr notify_public
		FROM meeting_type mt
		LEFT OUTER JOIN codes c ON (c.code_type = 'MTG_MSG' AND c.valid_code = mt.meeting_type)
		WHERE mt.show_public = 'Y'
			
		ORDER BY mt.descr
	
useNotify (Datasource=, Time=0ms, Records=4) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT notify_public FROM meetingTypes WHERE notify_public = 'Y'
contactInfo (Datasource=frsRO, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
		select text_value1 notify_public_contact, long_descr confLink
		from codes
		where codes.code_type = 'AddlSetup' and codes.valid_code = 'EmailSub'
	
chkAddlSetup (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT * from codes WHERE code_type = 'AddlSetup' AND valid_code = 'SysSetup'
chkAddlSetup2 (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT c.*,
	 	c.misc_alpha6 subscribe_tab, c.misc_alpha7 officials_tab, c.misc_alpha8 ordinance_tab, c.misc_alpha9 resolution_tab,
	 	c.misc_alpha11 voting_tab, c.misc_alpha12 useTabs, c.datasortOrder noOfMonths, c.loc_code ApplyTab,
	 	c.misc_alpha14 otherTab, c.misc_alpha15 oth_tab_descr, c1.misc_alpha3 other_doc_type,
 		c1.misc_alpha tab_color, c1.misc_alpha2 time_period, c1.misc_alpha4 sort_res_ord,
 		c1.misc_alpha5 ord_tab_descr, c1.misc_alpha6 res_tab_descr
 	from codes c
    LEFT OUTER JOIN codes c1 ON (c1.code_type = 'AddlSetup' AND c1.valid_code = 'SysSetup3')
	WHERE c.code_type = 'AddlSetup' AND c.valid_code = 'SysSetup2'
contactInfo (Datasource=frsRO, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
		select text_value1 notify_public_contact, long_descr confLink
		from codes
		where codes.code_type = 'AddlSetup' and codes.valid_code = 'EmailSub'
MeetingInfo (Datasource=frsRO, Time=15ms, Records=8) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
		select valid_code
		from codes
		where codes.code_type = 'MTG_MSG' and codes.misc_alpha15 = 'Y'
fasinfo (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT user_filedir_alias, min_dir_alias, use_minutes, use_agendaquick,
		srch_engine, isys_path, dflt_verity_coll, hart_version, user_defined
	FROM fasinfo
getFasInfo (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	select fasinfo.*,
	       c3.large_misc_alpha external_prefix, c3.misc_alpha2 active_directory, c3.misc_alpha3 ad_custsfx,
	       c3.loc_code allowExtNotes, c3.misc_alpha4 hostedInstall, c3.descr publTimeout, c3.text_value2 hosted_code
	from fasinfo
	left outer join codes as c3 on (c3.code_type = 'AddlSetup' and c3.valid_code = 'SysSetup')
AddlSetup (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	select text_value1, misc_alpha public_window, loc_code allowExtNotes
	from codes where code_type = 'AddlSetup' and valid_code = 'SysSetup'
begin_year (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT MIN(fis_yr) fis_yr FROM fas
	WHERE form_id = 'AGENDA'
end_year (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT MAX(fis_yr) fis_yr
	FROM fas
	WHERE form_id = 'AGENDA' AND final_apprvl = 'Y'
begin_collection (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT MIN(coll_name) coll_name FROM verity_collections
	ORDER BY coll_name
all_userdef (Datasource=frsRO, Time=0ms, Records=58) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT code_type FROM user_define
all_codes (Datasource=frsRO, Time=0ms, Records=11) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
	SELECT c.code_type, c.valid_code, c.descr, c.obsolete, c.misc_alpha2, c.descr, c.dataSortOrder sort_order,
		CASE WHEN descr = '' THEN valid_code ELSE descr END AS time_descr
	FROM codes c
	WHERE c.code_type = 'AG TIME'
	
		OR code_type IN ('ud_tb1','ud_pd1','ud_cb1','ud_ta1','ud_ta2','ud_fi1','ud_fi1','ud_cb1','ud_fi3','ud_fi4','ud_fi5','ud_fi6','ud_fi7','ud_fi8','ud_fi9','ud_yn1','ud_fi12','ud_fi13','ud_tb2','ud_fi2','ud_dt1','ud_fims1','ud_fil1','ud_fi3','ud_fis1','ud_tb3','ud_fi4','ud_tb4','ud_tb5','ud_tb6','ud_fi5','ud_fi6','ud_fi7','ud_fi8','ud_fi9','ud_fi10','ud_fi11','ud_fi12','ud_fi13','ud_fi14','ud_fi15','ud_fi16','ud_fi17','ud_fi18','ud_fi19','ud_fi20','ud_fi21','ud_fi22','ud_fi23','ud_dt1','ud_fi14','ud_fi15','ud_dt2','ud_rs1','ud_fi24','ud_fi25','ud_tb7','ud_fi26')
		AND (opt_form_id = '' OR opt_form_id IS NULL)
	
get_agendas (Datasource=frsRO, Time=16ms, Records=13) in D:\inetpub\PublicPages\public\publish\ext_agpub_top.cfm @ 09:03:32.032
		SELECT m.meeting_dt, m.meeting_name, m.meeting_id, a.form_num as ag_form_num,
			minutes.minutes_published, a.agenda_published,
			a.minutes_doc_name, a.minutes_doc_link,	a.default_doc_dir,
			minutes.default_doc_dir minutes_default_doc_dir,
			a.packet_doc_name, a.packet_published,
			minutes.form_num as min_form_num, minutes.minutes_packet_published,
			minutes.minutes_packet_name,
			ag_links.link_label as ag_link_label, ag_links.link_url as ag_link_url,
			min_links.link_label as min_link_label, min_links.link_url as min_link_url,
			 rel.large_misc_alpha as release_date, agt.meeting_type
		FROM meetings AS m
		INNER JOIN agenda AS a ON ( 
			a.meeting_id = m.meeting_id AND
			(a.agenda_published = 'Y' OR a.packet_published = 'Y')
		)
		LEFT OUTER JOIN minutes ON (
			minutes.meeting_id = m.meeting_id AND
			(minutes.minutes_published = 'Y' OR minutes.minutes_packet_published = 'Y')
		)
		INNER JOIN ag_template AS agt ON (agt.ag_template_id = m.template_id
		
			AND agt.meeting_type IN ('AIR','BOA','SALARY','CCBUDG','CCCSMWS','CCMTG','CCES','CCJWS','CCMTGF','CCSCM','CCSWS','CCWS','DVA','DA','FB','HPC','HOUS','IND','PQ','OSC','PR','PZ','PSPRS','SUS')
		
		)
		LEFT OUTER JOIN codes as rel ON (rel.code_type = 'AddlMtg' AND CAST(rel.valid_code AS INT) = m.meeting_id)
		
		LEFT OUTER JOIN form_links AS ag_links ON (
			ag_links.form_id  = 'AGENDA' AND
			ag_links.form_num = a.form_num AND
			ag_links.link_seq = 1
		)
		LEFT OUTER JOIN form_links AS min_links ON (
			min_links.form_id  = 'MINUTES' AND
			min_links.form_num = minutes.form_num AND
			min_links.rev_num  = minutes.rev_num AND
			min_links.link_seq = 1
		)
		WHERE m.meeting_dt >= ?

		  AND m.meeting_dt <= ?

		ORDER BY m.meeting_dt DESC, m.meeting_name
		
Query Parameter Value(s) -
Parameter #1(cf_sql_timestamp) = 2020-06-01 00:00:00.0
Parameter #2(cf_sql_timestamp) = 2020-06-30 00:00:00.0

chk_aiDisplay (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\ext_agpub_content.cfm @ 09:03:32.032
		select case when ss_agi._rowid is null then agi.display_routine else ss_agi.display_routine end as display_routine
		from ag_memo am
		inner join agenda_ln as atl on (atl.ag_memo_id = am.form_num and atl.ag_memo_rev = am.rev_num)
		inner join agenda as a on (a.form_num = atl.form_num)
		left outer join ag_item as agi on (agi._rowid = am.ag_item_rowid)
		left outer join ss_ag_item as ss_agi on (ss_agi.form_num = a.form_num and ss_agi._rowid = am.ag_item_rowid)
		where am.form_num = ?
		  and am.rev_num  = ? 
Query Parameter Value(s) -
Parameter #1(cf_sql_integer) = 4663
Parameter #2(cf_sql_integer) = 0

codesFields (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\agenda\agenda_utilities.cfm @ 09:03:32.032
			select top 1 * from codes
		
qryResults (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\cfm_utilities\_methodQryAI.cfm @ 09:03:32.032
	SELECT fas.form_id, fas.form_num fas_form_num, fas.rev_num fas_rev_num, fas.rqst_loc fas_rqst_loc, fas.action_cd fas_action_cd, fas.current_stop fas_current_stop,
		   fas.routing_apprvl fas_routing_apprvl, fas.final_apprvl fas_final_apprvl, fas.final_print fas_final_print, fas.fis_yr fas_fis_yr, fas.date_final,
		   fas.final_prt_date, fas.orig_loginid, meetings.meeting_dt as bo_date, de.fname, de.lname, de.title as utitle,															
		   meetings.doc_dir, meetings.meeting_name, meetings.meeting_dt, meetings.meeting_id, ag_times.descr time_descr, orig_depts.dept_desc, orig_divs.div_desc,
		   al.ag_size, al.ag_underline, al.ag_bold, al.ag_center, al.ag_italic, al.disp_level,
	  	   al.ag_level1 chk_level1, al.ag_level2 chk_level2, al.ag_level3 chk_level3,
		   al.ag_level1, al.ag_level2, al.ag_level3, al.ag_level4,al.seq_num,
		   al._rowid line_rowid,
		   a.text_size, a.text_font, a.print_num_ai, a.att_public, a.cont_numbering, a.att_header, a.exp_header, a.line_size, a.line_bold,
	   	   a.disp_num_ai, a.ag_punct, a.disp_ainumber, a.form_num ag_form_num, a.turn_off_level_dsp, a.disp_all_lvls,
		   a.disp_rteinfo, w.email, p.phone_no, p.phone_ext,
		   ft.meeting_id as ai_meeting_id, codes.long_descr px_size, codes.descr pdf_format, codes.misc_alpha4 special_format,
		   al._rowid AS ln_rowid, al._rowid AS agenda_ln_rowid, a.form_num AS ag_num, a.rev_num AS ag_rev, a.use_old_print_format,		
		   aa.descr ag_area_desc, asa.descr ag_subarea_desc, al.seq_vchar,
 	   	   c1.text_value1 pdf_header, c1.text_value2 pdf_footer, c1.misc_alpha prt_att_links,
	 	   c1.misc_alpha3 page_start, c1.misc_alpha2 info_header, c1.text_value3 all_bold,
	 	   	 
	 	   		c1.misc_alpha7 lvl_text_size, c1.misc_alpha6 dp_level_ai, c1.misc_alpha10 printMinutes, c1.misc_alpha11 printLegal, c1.misc_alpha13 dateSpelled, c1.misc_alpha14 left_justify_all,
	 	   	
	 	   c2.misc_alpha2 level_descriptor,
		   amdol.text_value amdol_more_info, amdol.text_block LinesCCCBoardOrder,
		   ft.* 
	FROM fas
	INNER JOIN ag_memo AS ft ON (fas.form_num = ft.form_num AND fas.rev_num = ft.rev_num)
	INNER JOIN form_hist ON (UPPER(form_hist.form_id) = fas.form_id AND UPPER(form_hist.stat_action) = 'ADD' AND form_hist.form_num = fas.form_num AND form_hist.rev_num = fas.rev_num)
	LEFT OUTER JOIN agenda AS a ON (ft.meeting_id = a.meeting_id)
	LEFT OUTER JOIN agenda_ln AS al ON (al.form_num = a.form_num AND al.ag_memo_id = ft.form_num AND al.ag_memo_rev = ft.rev_num)
	LEFT OUTER JOIN meetings ON (ft.meeting_id = meetings.meeting_id) 
	LEFT OUTER JOIN websecur AS w ON (w.login_id = ft.create_by)
	LEFT OUTER JOIN dist_empl AS de ON (de.empl_id = w.empl_id)
	LEFT OUTER JOIN phone AS p ON (p.empl_id = w.empl_id AND p.is_primary ='Y')
	LEFT OUTER JOIN codes AS ag_times ON (ag_times.code_type = 'AG TIME' AND ag_times.valid_code = ft.ag_time)
	LEFT OUTER JOIN codes ON (codes.code_type = 'AG_FONT' and codes.valid_code = a.text_size)
	LEFT OUTER JOIN ag_area aa ON (aa.meeting_type = meetings.the_meeting_type AND aa.ag_area = ft.ag_area)
	LEFT OUTER JOIN area_subarea AS asa ON (asa.ag_area = ft.ag_area and asa.ag_subarea = ft.ag_subarea and asa.meeting_type = meetings.the_meeting_type)

	LEFT OUTER JOIN dist_dept AS orig_depts ON (ft.orig_dept = orig_depts.dept_code)
	LEFT OUTER JOIN dept_div AS orig_divs ON (ft.orig_dept = orig_divs.dept_code AND ft.orig_div = orig_divs.div_code)
	LEFT OUTER JOIN form_userdef as amdol on (amdol.form_id = fas.form_id AND
		amdol.form_num = ft.form_num and amdol.rev_num = ft.rev_num AND
		amdol.code_type = 'AMDOL')
	LEFT OUTER JOIN codes AS c1 ON (c1.code_type = 'AddlMtg' and CAST(c1.valid_code AS INT) = ft.meeting_id)
	LEFT OUTER JOIN codes AS c2 ON (c2.code_type = 'MTG_MSG' and c2.valid_code = meetings.the_meeting_type)
	WHERE UPPER(fas.form_id) = 'AG_MEMO' AND
				fas.form_num = ? AND
				fas.rev_num = ? 
Query Parameter Value(s) -
Parameter #1(cf_sql_integer) = 4663
Parameter #2(cf_sql_integer) = 0

getAIList (Datasource=, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\agpub_agm_dsp.cfm @ 09:03:32.032
		SELECT * from Session.AIList
		WHERE ag_memo_id = 4663 AND
		      ag_memo_rev = 0 
final_check (Datasource=frsRO, Time=0ms, Records=2) in D:\inetpub\PublicPages\public\publish\agpub_agm_dsp.cfm @ 09:03:32.032
	SELECT _rowid
	FROM ss_ag_item
	WHERE ss_ag_item.form_num = 1047 
getFonts (Datasource=frsRO, Time=0ms, Records=7) in D:\inetpub\PublicPages\public\publish\include_set_fonts.cfm @ 09:03:32.032
 		SELECT valid_code, descr, long_descr from codes
 		WHERE code_type = 'AG_FONT'
 	
getLvlPdf (Datasource=, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_set_fonts.cfm @ 09:03:32.032
 		SELECT long_descr from getFonts
 		WHERE valid_code = 'mediumText'
 	
getPXvalue (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_set_fonts.cfm @ 09:03:32.032
		SELECT long_descr FROM codes WHERE code_type = 'AG_FONT' AND valid_code = 'mediumText'
	
agendaChk (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
		SELECT fas.final_apprvl
		FROM agenda, fas
		WHERE agenda.meeting_id = 1048 AND
			  fas.form_id = 'AGENDA' AND
			  fas.form_num = agenda.form_num
	
final_check (Datasource=frsRO, Time=0ms, Records=2) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
		SELECT _rowid, agenda.form_num
		FROM ss_ag_item, agenda
		WHERE agenda.meeting_id = 1048 AND
			  ss_ag_item.form_num = agenda.form_num
	
get_agi_temp (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
SELECT agi.*, mt.agmemo_prefix, mt.agmemo_desc, mt.meeting_type, mt.resolution_number mt_resolution_number, mt.num_label mt_num_label,
	   c.misc_alpha print_routine_program, c.misc_alpha2 pdfHeadersFooters, c.misc_alpha3 print_only_routine,
	   agt.text_size, agt.text_font, agt.ag_template_id, agt.disp_rteinfo,
	   agt.disp_ainumber, agt.print_num_ai , m.template_id 									
FROM meetings m, ag_template agt, meeting_type mt
	
	INNER JOIN ss_ag_item AS agi ON (agi.form_num = 1047 AND agi._rowid = 82)
	
LEFT OUTER JOIN codes c ON (c.code_type = 'AG_MEMO_PRT' AND c.valid_code = agi.print_routine)
WHERE m.meeting_id = 1048 AND
	  agt.ag_template_id = m.template_id AND
	  mt.meeting_type = agt.meeting_type AND
  	  agi._rowid = 82 
PrintRoutine (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
		SELECT valid_code, descr, misc_alpha, misc_alpha2 pdfHeadersFooters
		FROM codes
		WHERE code_type = 'AG_MEMO_PRT' AND valid_code = 'FLAG' AND obsolete = 'N'
	
all_userdef (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
		SELECT au.code_type au_code_type, c.misc_alpha sortRequired, au.*
		FROM user_define ud
		INNER JOIN agi_userdef as au ON (au.fld_name = ud.fld_name AND au.agi_rowid = 82)
		LEFT OUTER JOIN codes c ON (c.code_type = 'ExpRequired' AND c.valid_code = '82')
		WHERE form_id = 'AG_MEMO'
	
all_codes (Datasource=frsRO, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
			SELECT code_type, valid_code, descr, long_descr, misc_alpha2, obsolete, dataSortOrder sort_order, create_date
			FROM codes WHERE code_type IN ('ud_fi8')
			AND (opt_form_id = '' OR opt_form_id IS NULL)
		
getAllUD (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
			SELECT au.code_type, au.field_type, au.query_name, au.fld_name, au.seq_num,
					au.fld_label, au.fld_print, au.lbl_placement, au.new_row, au.colspan,
					text_block, au.agm_print_plcmnt,au.agm_csen, au.verti_hori, au.verti_hori_cols,
					CASE WHEN au.fld_rqd = 'N' then '2' else '1' end as sortBy
			FROM agi_userdef AS au
			WHERE au.agi_rowid = '82'
			order by  au.seq_num
		
get_userdef (Datasource=frsRO, Time=16ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
			SELECT u._rowid AS ud_id, u.ud_rowid, u.code_type, u.text_value,
				   ud.form_label, codes.descr, codes.large_misc_alpha
			FROM form_userdef AS u
			INNER JOIN user_define AS ud ON (ud._rowid = u.ud_rowid)
			LEFT OUTER JOIN codes ON (codes.code_type = u.code_type AND codes.valid_code = u.text_value)
			WHERE UPPER(u.form_id) = 'AG_MEMO' AND
					  u.form_num = 4663 AND
				      u.rev_num = 0 
getfi8 (Datasource=, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
				SELECT * from get_userdef
				WHERE code_type = 'ud_fi8'
			
fi8q (Datasource=, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
					SELECT valid_code, descr, sort_order, misc_alpha2 FROM all_codes
					WHERE code_type = 'ud_fi8' AND
					(obsolete = 'N' AND create_date <= ? 
					)
					ORDER BY sort_order
				
Query Parameter Value(s) -
Parameter #1(cf_sql_date) = 2020-06-09

getPXvalue (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
		SELECT long_descr FROM codes WHERE code_type = 'AG_FONT' AND valid_code = 'mediumText'
	
submittor (Datasource=frsRO, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
		SELECT ee.fname + ' ' + ee.lname name,
			websecur.login_id, ee.title utitle, websecur.email, p.phone_no, p.phone_ext,
			dept.dept_desc, dept.dept_code, dd.div_code, dd.div_desc
		FROM websecur
		LEFT OUTER JOIN dist_empl AS ee ON (ee.empl_id = websecur.empl_id)
		LEFT OUTER JOIN dist_dept AS dept ON (dept.dept_code = ee.department)
		LEFT OUTER JOIN dept_div AS dd ON (dd.dept_code = ee.department AND
											dd.div_code = ee.division)
		LEFT OUTER JOIN phone AS p ON (p.empl_id = ee.empl_id AND p.is_primary = 'Y')
		WHERE websecur.login_id = 'dsymer'
	
items (Datasource=frsRO, Time=0ms, Records=7) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
SELECT _rowid, seq_num, text_value
FROM ag_memo_item
WHERE form_num = 4663 AND
      rev_num = 0
ORDER BY seq_num
committees (Datasource=frsRO, Time=0ms, Records=17) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
	SELECT dept_code, dept_desc, review_comm FROM dist_dept
	
ReviewCommittee (Datasource=, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
	SELECT dept_code FROM committees WHERE review_comm = 'Y'
expenditures (Datasource=frsRO, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
	SELECT text1, input1, input2, input3, input4, input5, input6, fis_yrx, revenue, expenditure
	FROM ag_memo_dol WHERE ag_memo_dol.form_num = 4663 AND ag_memo_dol.rev_num = 0
	ORDER BY  ag_memo_dol._rowid	
attachments (Datasource=frsRO, Time=16ms, Records=5) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
	SELECT _rowid ag_doc_id, ag_doc_name, ag_doc_dir, ag_doc_link, sort_seq, confidentiality
		,'Y' as can_look, 'Y' as can_link
		
	FROM agenda_docs ad
	WHERE ad.form_num = 4663 AND
		  ad.rev_num = 0 
		  AND (ad.confidentiality IS NULL OR ad.confidentiality = '')		
		
	ORDER BY sort_seq, ag_doc_id
min_attachments (Datasource=frsRO, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
		SELECT * from codes where code_type ='asdfasdfasfa'
	
form_rte_stops (Datasource=frsRO, Time=0ms, Records=0) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
	SELECT _rowid stop_id, descr, form_rte.stop_id chkd_stop_id, form_rte.stop_seq
	FROM rte_stop
	LEFT OUTER JOIN form_rte ON (UPPER(form_rte.form_id) = 'AG_MEMO' AND form_rte.form_num = 4663 AND form_rte.rev_num = 0 AND form_rte.stop_id = rte_stop._rowid)
	WHERE UPPER(rte_grp) = 'AG_MEMO'
getorig (Datasource=frsRO, Time=31ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
	SELECT action_by, stat_date, de.fname, de.lname, de.title as utitle, w.dflt_rte_stop			
	FROM form_hist
	LEFT OUTER JOIN websecur AS w ON (w.login_id = form_hist.action_by)
	LEFT OUTER JOIN dist_empl AS de ON (de.empl_id = w.empl_id)
	WHERE UPPER(form_id) = 'AG_MEMO' AND
	      form_num = 4663 AND
		  rev_num = 0 AND
		  stat_action = 'ADD'
getstatus (Datasource=frsRO, Time=32ms, Records=3) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
		SELECT (hist.seq_num - 1) stop_seq, hist.stop_id, hist.action_by apprvl_id, hist.stat_date apprvl_date, 	
				hist.stat_action, hist.stat_action apprvl_stat, rte_stop.descr, rte_stop.prt_on_routing,
				de.fname, de.lname, de.title, fa.incl_originator		
		FROM form_hist hist
		INNER JOIN rte_stop ON (rte_stop._rowid = hist.stop_id AND rte_stop.prt_on_routing = 'Y')
		LEFT OUTER JOIN form_actions AS fa ON (UPPER(fa.form_id) = 'AG_MEMO' AND			
			                               fa.action_cd = 'AI82')
		LEFT OUTER JOIN websecur AS w ON (w.login_id = hist.action_by)
		LEFT OUTER JOIN dist_empl AS de ON (de.empl_id = w.empl_id)
		WHERE UPPER(hist.form_id) = 'AG_MEMO' AND
			  hist.form_num = 4663 AND
			  hist.rev_num = 0 AND
			  hist.stat_type = 'H'
		ORDER BY seq_num
	
agmemo_status (Datasource=, Time=0ms, Records=3) in D:\inetpub\PublicPages\public\publish\include_ag_memo.cfm @ 09:03:32.032
	SELECT * from getStatus
get_temp_vars (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\agenda\agenda_utilities.cfm @ 09:03:32.032
		SELECT 'Alpha','Alpha','Alpha','Alpha', a.ag_punct
		FROM meetings, agenda a
		WHERE meetings.meeting_id = ? AND
		      a.meeting_id = meetings.meeting_id
		
Query Parameter Value(s) -
Parameter #1(cf_sql_integer) = 1048

GetThisLine (Datasource=frsRO, Time=47ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_levels.cfm @ 09:03:33.033
				SELECT am.form_num fas_form_num, al._rowid ln_rowid, al.form_num, al.seq_num,
					   al.ag_level1 chk_level1, al.ag_level2 chk_level2, al.ag_level3 chk_level3,
					   al.ag_level1, al.ag_level2, al.ag_level3, al.ag_level4, al.disp_level, am.ainumber,
					   as1.sort_seq sort_level1, al.ag_memo_id, al.ag_memo_rev, c1.descr ag_time_descr,
					   fas.routing_apprvl fas_routing_apprvl, fas.final_apprvl fas_final_apprvl,
					   c2.misc_alpha7 lvl_text_size, c2.misc_alpha6 dp_level_ai, c3.long_descr px_size, c3.descr pdf_format,
							mt.agmemo_prefix, mt.agmemo_desc, a.disp_ainumber,
					   ai.*,
					   CASE WHEN al.ag_level2 != '' AND al.ag_level2 != '0' THEN as2.sort_seq ELSE -1 END AS sort_level2,
					   CASE WHEN al.ag_level3 != '' AND al.ag_level3 != '0' THEN as3.sort_seq ELSE -1 END AS sort_level3,
					   CASE WHEN al.ag_level4 != '' AND al.ag_level4 != '0' THEN as4.sort_seq ELSE -1 END AS sort_level4,
					   CASE WHEN al.ag_memo_id IS NOT NULL THEN al.ag_memo_id ELSE -1 END AS sort_memo,
					   CASE WHEN al.ag_memo_id IS NOT NULL THEN am.ag_time ELSE al.ag_time END as ag_time
				FROM agenda_ln al
				INNER JOIN agenda a ON (a.form_num = al.form_num AND a.rev_num = al.rev_num)
				LEFT OUTER JOIN ag_template AS agt ON (agt.ag_template_id = a.ag_template_id)
				LEFT OUTER JOIN meeting_type AS mt ON (mt.meeting_type = agt.meeting_type)
				LEFT OUTER JOIN ag_memo AS am ON (am.form_num = al.ag_memo_id AND am.rev_num = al.ag_memo_rev)
				LEFT OUTER JOIN fas ON (fas.form_id = 'AG_MEMO' AND fas.form_num = am.form_num AND fas.rev_num = am.rev_num)
				
				INNER JOIN ss_ag_item AS ai ON (ai.form_num = 1047 AND ai._rowid = 82)
				
				LEFT OUTER JOIN codes AS c1 ON (c1.code_type = 'AG TIME' and c1.valid_code = am.ag_time)
				LEFT OUTER JOIN alpha_sort AS as1 ON (as1.alpha_value = al.ag_level1 AND CAST(as1.alpha_value AS binary(8)) = CAST(al.ag_level1 AS binary(8)))
				LEFT OUTER JOIN alpha_sort AS as2 ON (as2.alpha_value = al.ag_level2 AND CAST(as2.alpha_value AS binary(8)) = CAST(al.ag_level2 AS binary(8)))
				LEFT OUTER JOIN alpha_sort AS as3 ON (as3.alpha_value = al.ag_level3 AND CAST(as3.alpha_value AS binary(8)) = CAST(al.ag_level3 AS binary(8)))
				LEFT OUTER JOIN alpha_sort AS as4 ON (as4.alpha_value = al.ag_level4 AND CAST(as4.alpha_value AS binary(8)) = CAST(al.ag_level4 AS binary(8)))
				LEFT OUTER JOIN codes AS c2 ON (c2.code_type = 'AddlMtg' and CAST(c2.valid_code AS INT) = a.meeting_id)
				LEFT OUTER JOIN codes AS c3 ON (c3.code_type = 'AG_FONT' and c3.valid_code = a.text_size)
				WHERE al._rowid = 24901 
chkLevel1 (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_levels.cfm @ 09:03:33.033
					SELECT a.disp_level
					FROM agenda_ln a
					WHERE a.form_num = 1047
					AND a.ag_level1 = '8'
					AND (a.ag_level2 = '' OR a.ag_level2 IS NULL)
					AND (a.ag_level3 = '' OR a.ag_level3 IS NULL)
					AND (a.ag_level4 = '' OR a.ag_level4 IS NULL)
					AND a.header_ln = 'N' AND a.footer_ln = 'N'
				
chkLevel2 (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_levels.cfm @ 09:03:33.033
					SELECT a.disp_level
					FROM agenda_ln a
					WHERE a.form_num = 1047
					AND a.ag_level1 = '8'
					AND a.ag_level2 = ''
					AND (a.ag_level3 = '' OR a.ag_level3 IS NULL)
					AND (a.ag_level4 = '' OR a.ag_level4 IS NULL)
					AND a.header_ln = 'N' AND a.footer_ln = 'N'
				
chkLevel3 (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\include_levels.cfm @ 09:03:33.033
					SELECT a.disp_level
					FROM agenda_ln a
					WHERE a.form_num = 1047
					AND a.ag_level1 = '8'
					AND a.ag_level2 = ''
					AND a.ag_level3 = ''
					AND (a.ag_level4 = '' OR a.ag_level4 IS NULL)
					AND a.header_ln = 'N' AND a.footer_ln = 'N'
				
Departments (Datasource=frsRO, Time=0ms, Records=17) in D:\inetpub\PublicPages\public\publish\adv_search_selection.cfm @ 09:03:33.033
	SELECT dept_code, dept_desc, obsolete FROM dist_dept ORDER BY dept_desc
sysinfo (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\adv_search_selection.cfm @ 09:03:33.033
	SELECT use_agendaquick, use_minutes, public_verity from fasinfo
count_minutes (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\adv_search_selection.cfm @ 09:03:33.033
		SELECT TOP 1 c.meeting_id
		FROM meetings AS m, minutes AS c
		WHERE c.meeting_id = m.meeting_id
		  AND c.minutes_published = 'Y'
		ORDER BY m.meeting_dt 
count_agendas (Datasource=frsRO, Time=0ms, Records=1) in D:\inetpub\PublicPages\public\publish\adv_search_selection.cfm @ 09:03:33.033
		SELECT TOP 1 c.meeting_id
		FROM meetings AS m, agenda AS c
		WHERE c.meeting_id = m.meeting_id
		  AND c.agenda_published = 'Y'
		ORDER BY m.meeting_dt 


Scope Variables

CGI Variables:
AUTH_PASSWORD=
AUTH_TYPE=
AUTH_USER=
CERT_COOKIE=
CERT_FLAGS=
CERT_ISSUER=
CERT_KEYSIZE=
CERT_SECRETKEYSIZE=
CERT_SERIALNUMBER=
CERT_SERVER_ISSUER=
CERT_SERVER_SUBJECT=
CERT_SUBJECT=
CF_TEMPLATE_PATH=D:\inetpub\PublicPages\agenda_publish.cfm
CONTENT_LENGTH=0
CONTENT_TYPE=
CONTEXT_PATH=
GATEWAY_INTERFACE=CGI/1.1
HTTPS=off
HTTPS_KEYSIZE=
HTTPS_SECRETKEYSIZE=
HTTPS_SERVER_ISSUER=
HTTPS_SERVER_SUBJECT=
HTTP_ACCEPT=*/*
HTTP_ACCEPT_ENCODING=gzip, br, zstd, deflate
HTTP_ACCEPT_LANGUAGE=
HTTP_CONNECTION=Keep-Alive
HTTP_COOKIE=CFTOKEN=45067e48be783f31%2DAFAAD97D%2DD46F%2D48EB%2DE2015181F0BD8983; CFID=9899449
HTTP_HOST=10.20.10.48:8555
HTTP_REFERER=
HTTP_URL=//agenda_publish.cfm?id=&mt=ALL&get_month=6&get_year=2020&dsp=agm&seq=4663&rev=0&ag=1047&ln=24901&nseq=4690&nrev=0&pseq=4707&prev=0
HTTP_USER_AGENT=Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
LOCAL_ADDR=10.20.10.48
PATH_INFO=
PATH_TRANSLATED=D:\inetpub\PublicPages\agenda_publish.cfm
QUERY_STRING=id=&mt=ALL&get_month=6&get_year=2020&dsp=agm&seq=4663&rev=0&ag=1047&ln=24901&nseq=4690&nrev=0&pseq=4707&prev=0
REMOTE_ADDR=10.20.230.5
REMOTE_HOST=10.20.230.5
REMOTE_USER=
REQUEST_METHOD=GET
SCRIPT_NAME=/agenda_publish.cfm
SERVER_NAME=10.20.10.48
SERVER_PORT=8555
SERVER_PORT_SECURE=0
SERVER_PROTOCOL=HTTP/1.1
SERVER_SOFTWARE=Microsoft-IIS/10.0
WEB_SERVER_API=
Client Variables:
cfid=9899449
cftoken=45067e48be783f31-AFAAD97D-D46F-48EB-E2015181F0BD8983
hitcount=33
lastvisit={ts '2024-05-19 09:03:32'}
timecreated={ts '2024-05-19 09:03:29'}
urltoken=CFID=9899449&CFTOKEN=45067e48be783f31-AFAAD97D-D46F-48EB-E2015181F0BD8983
Cookie Variables:
CFID=9899449
CFTOKEN=45067e48be783f31-AFAAD97D-D46F-48EB-E2015181F0BD8983
Form Fields:
ATT_TYPE=AG
DISPLAY_AG=1047
DISPLAY_ID=4663
DISPLAY_REV=0
Session Variables:
ailist=Query (16)
cfid=9899449
cftoken=45067e48be783f31-AFAAD97D-D46F-48EB-E2015181F0BD8983
dbtype=SQLSERVER
dsn=frsRO
extpathprefix=/public/
isexternal=true
logfilepath=d:\logs\
loggedin=false
sessionid=FASPUBLIC_9899449_45067e48be783f31-AFAAD97D-D46F-48EB-E2015181F0BD8983
subdir=/public/
tzoffset=0
urltoken=CFID=9899449&CFTOKEN=45067e48be783f31-AFAAD97D-D46F-48EB-E2015181F0BD8983
URL Parameters:
ag=1047
dsp=agm
get_month=6
get_year=2020
id=
ln=24901
mt=ALL
nrev=0
nseq=4690
prev=0
pseq=4707
rev=0
seq=4663
Debug Rendering Time: 15 ms