§ 35-B101. Specifications for Documents to be Submitted.

Latest version.

(a)

Generally. The purpose of this chapter is to streamline the development approval process by prescribing the information necessary for complete review of an application for development approval. No application for development approval shall be considered complete, and the applicable director or any other agency or official of the city shall not process any application for development approval, unless all of the information prescribed therefor in this appendix is included. The applicable director or any other agency or official of the city shall not delay the processing of any application for development approval if it contains the information prescribed by this appendix.

(b)

Forms. The applicable director shall promulgate necessary forms for the administration, interpretation and enforcement of this chapter. The applicable director shall maintain such forms at the offices of the department of planning and development services. The forms shall require the information set forth in this appendix for any application for development approval.

(c)

Information Required. No application for development approval shall be accepted unless the following information and data required is included. The required information and data is set forth in Table B101-1, below, and any specific regulations set forth in section 35-B102 et seq.

TABLE B101-1

	A	B	C	D	E	F	G
	(A) Material/Information	Master Development Plan	PUD Plan	Major Plat Application	Minor Plat Application	Development Plat Application	Specific Use Authorization
A.	GENERAL
	(1) Proposed name of subdivision or development if not within a previously platted subdivision. The proposed name shall not duplicate the name of any plat previously recorded in the County.	*	*	*	*
	(2) City assigned Master Development Plan ID number.	*	*	*	*
	(3) City assigned Plat ID number.			*	*
	(4) ERZD designation note as applicable.			*	*
B.	OWNERSHIP
	(1) Name and address of owner of record, developer and designer.	*	*	*	*
	(2) The names of all adjacent property owners as shown on current tax records.	*	*
	(3) Certificate of agency or power of attorney if other than owner.	*	*	*	*
	(4) Names and lot numbers of adjacent plats.			*	*
	(5) A table shall be provided on each sheet of the plat indicating the lots on which required ADA passing space are required. The passing space shall meet then current ADA regulations concerning size slopes and distance separation.			*	*
C.	APPROVALS
	(1) Signature blocks prepared for the dated signatures of the chairperson and secretary (director of development service or assignee) of the authorized approval entity.	*	*	*	*	*
D.	LEGAL
	(1) Owner's certificate of consent including a legal description of the boundaries of the proposed development and the dedication of public ways or spaces. This certificate shall be signed, dated, and notarized prior to recording the instrument.			*	*
	(2) Proposed covenants on the property, if any, including a map and legal description of area affected.		*
	(3) Copies of maintenance agreements for privately owned drainage facilities.			*	*
E.	PROPERTY SURVEY AND TOPOGRAPHIC
	(1) Two points identified by Texas Planes Coordinates.	*	*	*	*
	(2) Basis of bearings used and a north point.	*	*	*	*
	(3) Boundary of the development and total acreage encompassed, thereby described and mapped at an appropriate scale.	*	*
	(4) Legal description and exhibit of the property, an exhibit of current recorded status of the property to include but not limited to a replat, amending plat, antiquated plat, building setback line replat, lot line removal replat, and/or in the case of arbitrary lots evidence that said property falls within the original 36 square mile area of the City of San Antonio, at appropriate scale showing the boundary. Description may be related to the USGS, state grid north, if two (2) adjacent corners are shown.			*	*
	(5) Topographic contour intervals of no greater than ten (10) feet.	*
	(6) Existing topography with maximum contour interval of ten (10) feet when ground slope exceeds ten (10) percent; two (2) feet for slopes between five (5) percent and up to ten (10) percent, and where existing ground is on a slope of less than five (5) percent then either one (1) foot contours or spot elevations shall be provided where necessary.		*	*	*
	(7) All monuments erected, and corners established in the field. The material of which the monuments, corners, or other points are made shall be noted at the representation thereof or by legend, except that lot corners need not be shown. Guarantee by the owner or developer of placement of corner monuments for each lot may be by noting on the plat that such lot monumentation shall occur at completion of all onsite infrastructure construction.			*	*	*
F.	PLANNING
	(1) Date of preparation.	*	*	*	*
	(2) Graphic and written scale and north arrow.	*	*	*	*
	(3) A location map at a scale of not less than 1" = 2,000' indicating the location and distance in relation to adjacent streets and all surrounding major thoroughfares. The location map is to be located in the top left hand corner of the sheet.	*	*	*	*
	(4) Total area of property.	*	*	*	*
	(5) All existing easements or right-of-way and street names, including those contiguous to the development area, their nature, width, and the volume and page number of their recording.			*	*	*	*
	(6) All existing easements or right-of-way with street names impacting the development area, their nature and width.	*	*			*	*
	(7) The location and widths of all proposed public and private streets within the development's boundaries.			*	*	*	*
	(8) The approximate location and widths of all proposed public and private streets within the development's boundaries.		*			*	*
	(9) The approximate location and widths of all proposed public and private streets major thoroughfares, collectors and local b streets within the development's boundaries. For Master Plans (MDPs) 100 acres or less, the double line representation of all streets shall be required. (See exhibit "A")	*				*	*
	(10) The location of all proposed uses or zoning districts as applicable and the maximum allowable intensity (residential density or nonresidential FAR).		*
	(11) The location and general nature of proposed uses and proposed intensity (residential density or nonresidential FAR).	*
	(12) Notation of any restrictions required by the City Council in accordance with this Ordinance.		*
	(13) Notation of any restrictions required as part of the platting process in accordance with this Ordinance.			*	*
	(14) The location of all entrances onto existing and/or proposed adjacent roadways, whether existing or proposed.	*	*
	(15) The location and dimensions of all proposed or existing lots.		*	*	*
	(16) The location, dimensions, and area of all parcels of land proposed to be set aside for park or playground use or other public use, or for the use of property owners in the proposed subdivision, where applicable.	*	*	*	*
	(17) A development phasing schedule including the sequence for each phase; approximate size in area of each phase; and, proposed phasing of construction of public improvements, recreation and common open space areas.	*	*
	(18) The schematic location of all existing and proposed streets, as well as proposed access points. For master development plans (MDPs) greater than 100 acres and more than one (1) sheet is necessary to accommodate the entire site, single line representation of all streets not listed in subsection (9) shall be allowed or the engineer can choose to submit a supplemental for his development showing all streets in double line representation. Additional supplemental plans shall be submitted as additional segments of the original master plan are developed. (See Exhibit "B")	*	*			*	*
	(19) The schematic location of the pedestrian circulation system including walkways and bicycle paths, where applicable.	*	*
	(20) (Conservation subdivisions only) A slope analysis of the proposed development site, showing slopes for the following percent of existing grades: 0—10%, 10—20%, 21—30%, 31—40%, and slopes exceeding 40%, including a tabulation of the number of acres in each slope percentage.	*	*
	(21) A delineation of EARZ, wetlands and floodplains. Conservation subdivisions and PUD Plans shall also delineate woodlands.	*	*
	(22) The location, acreage, category and type of improvements, if any, for active and passive open space, including Greenbelt and active recreation space areas, private recreational areas.	*	*
	(23) Tabulation of the number of acres in the proposed development, showing the total number of lots, and area of open space for the site including the following:
	a. Square footage of all buildings and structures.		*				*
	b. For nonresidential uses, multi-family dwellings, and any portion of a site located within the EARZ, the approximate location and area of impervious cover.		*				*
	c. Square footage of all paved or otherwise hard surfaced streets, parking facilities, including curb and gutters, walks, loading areas, and asphalt or concrete aprons for solid waste containers, signs or outdoor mechanical equipment.						*
	(24) A final statement in tabular form which sets forth the following data, when such data is applicable to a given development plan: (note: this information shall not be required to be shown on the plat)
	a. Total number of dwelling units, by development phase;	*	*
	b. Residential density and units per acre;	*	*
	c. Total floor area and floor area ratio for each type of use;		*
	d. Total area in passive open space;		*
	e. Total area in active developed recreational open space; and		*
	f. Total number of off-street parking and loading spaces.		*
	(25) Traffic Impact Analysis (section 35- 502)	*	*	*	*
	(26) Utilities Plan		*	*
	(27) Historical/Archaeological Survey Report	*	*	*	*
	(28) An exhibit indicating the area of each lot in square feet for all single-family lots (gross and net excluding easements, flag poles) using on-site sewage (septic tank) disposal			*	*
G.	DESIGN
	(1) Sufficient data to determine readily and reproduce accurately on the ground the location, bearing and length of every street and alley line, lot line, building line, easements required hereunder or of record in Bexar County or ascertainable by physical inspection of the property, and boundary lines of reserved or dedicated areas. All linear dimensions shall be in feet and hundredths thereof. The maximum allowable error of linear closure shall not be in excess of 1:10,000. In closed traverses, the sum of the measured angles shall vary with the theoretical sum by a difference not greater than an average of seven and one-half (7½) seconds per angle, or the sum of the total shall not differ from the theoretical sum by more than ninety (90) seconds, whichever is smaller. Said information shall be provided on reproducible Mylar and on digital media.			*	*
	(2) Location of property lines, existing easements, burial grounds, railroad rights-of-way, watercourses; location, width, and names of all existing or platted streets or other public ways within or immediately adjacent to the tract; names of adjacent property owners or subdivision name when adjacent property is a platted subdivision from the latest certified assessment rolls	*		*	*
	(3) Final location, arrangement and dimensions of all proposed and existing lots.			*	*
	(4) Lots and open space numbered as approved by the city. Open space shall be designated by a 900 series lot # and the size in acreage shall be provided. Commentary: Information Bulletin (IB) 510 describes the process for the assignment of legal descriptions to properties.		*	*	*
	(5) .Layout shall show setbacks for areas located in the ETJ. (setbacks are not required for plats inside the city limits).		*	*	*		*
	(6) Off-street parking and loading areas and structures, including the number of spaces; dimensions of spaces and aisles; and landscaping for parking areas.		*				*
	(7) Location, sizes, elevations, and slopes of existing sewers, water mains, culverts, and other underground structures within the tract and immediately adjacent thereto; existing permanent building and utility poles on or immediately adjacent to the site and utility rights-of-way, as part of a request for LOC			*	*
	(8) Preliminary proposals for connection with existing water supply and sanitary sewage systems, or alternative means of providing water supply and sanitary waste treatment and disposal; preliminary provisions for collecting and discharging surface water drainage, as part of a request for LOC			*	*
	(9) All roadway locations and dimensions, their names, numbers, and rights-of-way with profiles and cross sections of all proposed streets showing proposed cuts and fills, as part of a request for LOC.			*	*
	(10) Location and size of existing water and sewer mains together with intended water sources and sewage disposal sites, as part of a request for LOC			*	*
	(11) Location of existing springs or public water supply, as part of a request for LOC			*	*
	(12) Location of proposed water and sewer lines, as part of a request for LOC.			*	*
	(13) Location of proposed fire hydrants, as part of a request for LOC.		*	*	*
	(14) A tree affidavit/permit application (section 35-B123)			*	*
	(15) The location, dimensions and type of all walls, fences (other than fences on private residential lots) and landscaping.						*
	(16) Tree stand delineation (Section 35-B125 General)	*
	(17) Location and size in acres of school sites, amenity center areas, or non-single-family lots as applicable.	*	*	*	*
	(18) The exterior boundaries as indicated from deeds or other instruments of the development area giving lengths and bearings of the boundary lines. If the proposed development is bounded by a watercourse, a closing meander traverse of that boundary shall be made and shown on the site plan. Where curving boundaries are used, sufficient data to establish the boundary on the ground shall be given; including the curve's radius, central angle, and arc length.	*	*	*	*	*
	(19) A stormwater management plan (section 35-B119)	*	*	*	*	*	*1
	(20) Signage, pavement markings, street, alley and cross walkway plans (section 35-B120)			*
	(21) Habitat compliance form consistent with section 35-B133 for properties greater than two (2) acres in size	*	*	*	*	*

*1. Specific use permits shall only require a stormwater management plan when the site is located over the Edwards Recharge Zone (ERZD).

(d)

Certifications. Where any provision of this section requires a certification and/or signature by the applicant, a professional, or a public agency or official, the signature lines shall be provided in the lower right-hand corner of the plans, plats, or other required documents.

(e)

Digital Plat Requirements.

(1)

Generally.

Plat information shall be provided to the City of San Antonio in two (2) forms — as hard copy subdivision plat sheets and as plat digital data. The purpose of the plat digital data requirement is to coordinate with the city's GIS program to assist city officials in analyzing, understanding, interpreting and presenting the data.

Digital data of subdivision plats will consist of graphical elements representing the hard copy subdivision plat. The applicant shall provide digital data twice during the subdivision review process — initially, when the subdivision plat is submitted to the department of development services for plat review, and secondly, before the subdivision plat is approved by the planning commission. Additional digital submittals are required if changes occur between the second digital submittal and the recordation of the plat. The final digital submittal would reflect the graphical elements of the recorded plat.

The initial digital data submittal shall include the subdivision boundary, as a minimum. The digital media shall bear a label similar to that of the final digital media, as described in subsection (e)(7), below, with the exception of the plat number.

The final digital data media may be submitted with the final subdivision plat documents to the department of development services. The final digital data media must be submitted before the subdivision plat is considered complete and ready for the planning commission consideration.

The digital data submittals are subject to review and approval as a condition to the subdivision plat review and approval process. The X-Y coordinates indicated with the initial submittal will be subject to approval, as per section 35-B121 of this chapter. If an error is found to exist in the digital data which the city cannot correct, or if the digital data is otherwise unacceptable, the city will contact the submitting organization to have the digital data corrected.

Both the digital files and hardcopy files must contain all the elements consistent with accurately defining the geometry and global position of the proposed subdivision. In addition, the following two (2) key data elements are also required on plat submittals.

All new street names must have been approved by the U. S. Postal Service and shown on the hardcopy and digital plat submittals. The city will no longer accept unnamed street designations such as street "A".

The city must be able to determine from the plat a correct tax account number made up of NCB (5 digits), Block (3 digits), and Lot number for each proposed lot. Information on the plat will allow the creation of a correct and therefore unique tax account number for every proposed lot. The city will no longer accept invalid block numbers such as Block "D".

Failure to provide approved street names and correct and unique NCB, block, and lot numbers may result in significant delays as no plat will be approved until this key data is determined.

(2)

Control Points and Monumentation Guidelines.

Primary horizontal control points will be used when surveying each tract being subdivided. These primary horizontal control points must be established by using centimeter-grade accuracy GPS devices and procedures and methods that meet the Texas Board of Land Surveyor's minimum standards 22 TAC, part 29 ("the Standards"). The precision of the monumentation will be in accordance with section 663.15 of the Standards. New primary horizontal control points must be established and monumented for each subdivision.

Primary horizontal control points shall be tied to at least one (1) National Geodetic Survey (NGS) mark and the point will be identified datum point on both the hardcopy and digital plat submittals.

The minimum number of required primary horizontal control points (reference corners) is based upon the overall plat size in acres as follows:

Plat Size	Number of Points
20 acres or less	2 points
20 + to 50 acres	3 points
greater than 50 acres	4 points

The X-Y coordinates for each of the primary horizontal control points and consistent and appropriate bearings between each of the primary horizontal control points should be provided. These primary horizontal control points will be provided in NAD83 U.S. Survey feet, State Plane Coordinates for Texas South Central Zone (Zone Number 4204).

All primary horizontal control points shall be permanently identified with monumentation set to Texas Board of Land Surveyor's minimum standards, Section 663.17.

(3)

Data Layer/Level Requirements. Data will be separated into the following feature categories, each residing on its own unique level or layer. Any layer name or level number is acceptable as long as each feature set is on its own individual layer or level.

Layer and Level Element Types

Feature	Element Types
Subdivision Boundary Data	Lines and Curves
Control Points and Ties to Boundary Text	Points and Cells
Text*	Text
Primary Lot Line Data	Lines and Curves
Right-of-Way Centerline Data	Lines and Curves
Right-of-Way Data	Lines and Curves
Easement Data	Lines and Curves

(*Subdivision plat certification data is not required to be included in the plat digital data until final plat submittal.)

(4)

Additional Digital Criteria. The following additional criteria will apply to data submitted digitally:

Cells shall be fully expanded.

Curves shall only be used to represent irregular boundaries.

The subdivision outside boundary shall be transmitted as a closed figure. For example, the subdivision boundary would be represented as one (1) polyline rather than a series of lines, arcs, and curves. This will assure closure of the subdivision perimeter.

Curvilinear boundaries — not lines or arcs — will be represented by sufficient points to unambiguously define the boundary. Examples of curvilinear boundaries might include the centerline of a stream, high water mark, contour lines, and transition curves on railroads.

(5)

Formats for Graphical Data. Any of three (3) formats are allowed for digital plat data submitted to the development services department — DXF (generic), DWG (AutoCAD), and DGN (Microstation).

DGN (Microstation) (Bentley). This is the graphics format used by the City of San Antonio, so no conversion is required when data is provided in this format. The Microstation software used to produce these files should be the most current or prior version of the product. Files produced using software over two (2) releases old may not be accepted. DGN files created on digital media for delivery to the city will be created as ASCII files. No reference files will be attached to DGN files submitted to the city.

DWG (AutoCAD) (Autodesk). This file format is used by Autodesk with their AutoCAD product. This is the preferred way for AutoCAD users to transfer files to the city. The AutoCAD software used to produce these files should be the most current or the prior version of the product. File produced using software over two (2) releases old may not be accepted. "Paper Space" will not be used as part of the drawing file being submitted.

DXF (All Others) (Drawing Exchange File). DXF is an exchange format developed by Autodesk for use with their AutoCAD product. This format is the preferred exchange format for organizations that use graphics software provided by vendors other than Bentley or Autodesk. Only the ASCII output file option will be accepted for this exchange format. A binary DXF output format option is available, but it will not be accepted as a valid exchange format. The software used to produce these files should be compatible with the current or prior versions of Microstation or AutoCAD. Files produced using file compatibility over two (2) releases old may not be accepted.

(6)

File Naming Conventions. The applicant shall submit one (1) file for each plat that is submitted to the city. File naming conventions will be used as follows with "xxxxx" representing the assigned plat number.

Plat submitted from AutoCAD	xxxxx.DWG
Plat submitted from Microstation	xxxxx.DGN
Plat submitted from other software products	xxxxx.DXF

(7)

Media Requirements and File Creation. The city will accept files on digital media. Files created for delivery to the city will be produced using Windows output formats. Digital media will be labeled with the following information:

Plat number, subdivision name, number of files (sheets), on the digital media creation date, company name, contact name and phone number.

(8)

City's Use of Digital Data. The city staff utilizes the final digital data to create the geometry and global position of the newly established subdivision.

(f)

Digital Requirements for Street and Drainage Construction Plan Submittals.

(1)

Generally.

Street and drainage construction plan drawings shall be provided to the City of San Antonio in two (2) forms — as traditional hard copy Mylar drawings and as drawing digital data. The purpose of the drawing digital data requirement is to allow for improved document storage, retrieval, and review within various city departments, and is to be used for information purposes only. Unlike the hard copy documents which are signed and sealed legal documents, the drawing digital data will have no legal significance. However, the drawing digital data may be used to assist city employees in analyzing, understanding, interpreting and presenting the data.

Drawing digital data will consist of the graphical elements represented on the final hard copy street and drainage construction plans submitted to the city. Signatures, seals, stamps, and other non-graphical drawing elements are not required as part of the drawing digital data submittal.

Drawing digital data submittals, delivered to the city on CD(s) or diskette(s), are required as a condition to the final approval of the street and drainage drawing set. If the city determines an error is found to exist in the digital data including the inability to read the media on which the drawing data is delivered, discrepancies between the hard copy drawings and the digital data, or if the digital data is otherwise unacceptable, the city will contact the submitting organization to have the digital data corrected and/or redelivered to the city prior to public works issuance of the letter of certification.

(2)

Data Layer/Level Requirements. Data will be separated into the following feature categories on digitally submitted street plan and profile drawings with each feature type residing on its own unique level or layer. Any layer name or level number is acceptable as long as each feature set is on its own individual layer or level.

Layer and Level Element Types

Feature	Element Types
Property and Lot Boundary Data	Lines, and Curves and Text
Curb Lines	Lines and Curves
Wheel Chair Ramps	Lines, and Curves, and Blocks
Edge of Pavement	Lines and Curves
Sidewalks	Lines and Curves
Drainage Inlets	Lines, and Curves, and Blocks
Easement Data	Lines and Curves
Contour Lines and Elevations	Lines and Curves Polylines and Text

(3)

Additional Digital Criteria. The following additional criteria will apply to data submitted digitally:

Cells shall be fully expanded.

Curves shall only be used to represent irregular boundaries.

(4)

City-Provided Standard Detail Sheets in a Digital Format. The city's drainage and capital programs departments will provide standard details in a digital format to anyone requesting the files. The request should include whether the files should be provided in AutoCad (DWG), MicroStation (DGN), or Generic (DXF) format. These files may be e-mailed to the requestor, or provided on diskette. Since the city does not use AutoCad, the requests for this format will be performed using the conversion software available within MicroStation, and is provided with no claims as to the requestor's ability to read or use the delivered files.

(5)

Formats for Graphical Data. Any of three (3) formats are allowed for drawing digital data submitted for approval by the public works department — DXF (generic), DWG (AutoCAD), and DGN (Microstation).

DGN (Microstation) (Bentley). This is the graphics format used by the City of San Antonio. The Microstation software used to produce these files should be the most current or prior version of the product. Files produced using software over two (2) releases old may not be accepted. No reference files will be attached to DGN files submitted to the city.

DWG (AutoCAD) (Autodesk). This file format is used by Autodesk with their AutoCAD product. This is the preferred way for AutoCAD users to transfer files to the city. The AutoCAD software used to produce these files should be the most current or the prior version of the product. Files produced using software over two (2) releases old may not be accepted. No xreference files will be attached to DWG files submitted to the city.

DXF (All Others) (Drawing Exchange File). DXF is an exchange format developed by Autodesk for use with their AutoCAD product. This format is the preferred exchange format for organizations that use graphics software provided by vendors other than Bentley or Autodesk. Only the ASCII output file option will be accepted for this exchange format. The software used to produce these files should be compatible with the current or prior versions of Microstation or AutoCAD. Files produced using file compatibility over two (2) releases old may not be accepted.

(6)

File Naming Conventions. The applicant shall submit one (1) file for each drawing sheet that is submitted to the city. File naming conventions and extensions will be used as follows:

Drawings submitted from AutoCAD	xxxxxx-yyya.DWG
Drawings submitted from Microstation	xxxxxx-yyya.DGN
Drawings submitted from other software products	xxxxxx-yyya.DXF

"xxxxxx" is the plat number assigned by the city's department of planning and development services prior to drawing submittal,

"yyy" is the sheet number of the drawing in the submitted set, and

"a" is used to allow insertion of additional sheets in their proper place within the drawing set when appropriate.

Leading zeros should be used in both the six-digit plat number and the three-digit sheet number to assure proper sorting by file name. For example, an AutoCad file containing sheet 12 of 56 for plat number 010233 would be named 010233-012.DWG.

A new sheet inserted into the set late in the approval process after sheet numbers have been assigned - in this example, to follow sheet 12 - would be identified by file name 010233-012A.DWG

(7)

Media Requirements and File Creation. The city will accept files on DOS 3.5" high density (1.4 Mb) diskettes or on 650 Mb CD's. Files created on diskette or CD for delivery to the city will be produced using Windows output formats. WinZip may be used to compress the files being submitted. Diskettes and CD's will be labeled with the following information:

Plat number, subdivision name, number of files (sheets) on the diskette or CD, disk creation date, company name, and contact name and phone number.

(8)

City's Use of Submitted Digital Data. The city staff may make minor corrections to the drawing digital data if the information needs correcting due to minor differences between the hard copy sheets and the digital data, or if other minor errors, such as layering errors are detected. In instances where differences exist, the information provided on the hard copy Mylar drawings will always take precedence over the drawing digital data. The digital information has no legal significance.

(Ord. No. 95573 § 9, Amendment "I") (Ord. No. 97332 § 8) (Ord. No. 98697 § 1) (Ord. No. 2006-11-30-1333, § 2, 11-30-06) (Ord. No. 2009-01-15-0001, § 2, 1-15-09) (Ord. No. 08-20-0652, § 1, 8-20-09) (Ord. No. 2009-08-20-0661, § 3, 8-20-09)(Ord. No. 2015-12-17-1077 , § 2, 12-17-15)

                    
                        var val = document.getElementById('citecontent').innerHTML;
                        art.dialog.defaults.title = window.location.href;
                        art.dialog.data('cite', val);
                        art.dialog.data('homeDemoPath', '/Scripts/plus/artDialog/');
                        art.dialog.open('/Scripts/plus/artDialog/citeiframe.html');