Description: This feature is used to digitize proposed development and/ or zoning changes; often in conjunction with MyPermitNow review requirements. The feature is populated by Development Services GIS Analyst. PROJECT_NAME: Name of projectFEATURE_TYPE: Zoning, PDD, Subdivision, Parcel, Easement, OtherACRES: Calculated Geometry CASE_NUM: Planning Case designationPHASE: Proposed stage of projectADDR_NUM: Address numberPRE_DIR: Street Pre-fixST_NAME: Street NameST_TYPE: Street SuffixNOTE1: Digitizing notesNOTE2: Other NotesSOURCE: Typically CAD file or Survey Metes & BoundsLOT_NUM: Lot number if applicable BLOCK_NUM: Block number if applicable ZONECODE: Proposed zoning
Description: These address data are updated, typically by request, to City of San Marcos Planning and Development Services on a daily to weekly basis. Updates occur as new parcel plats are recorded, as building footprints change, when new service equipment such as cell towers and meters is installed, to bring existing address points into compliance with CAPCOG 911-Addressing guidelines, and as needed for various other circumstances.The 911 addresses (denoted in the Address911 field as “Y”) follow the CAPCOG (Capital Area Council of Governments) Addressing Guidelines (10-28-09) available here: http://www.capcog.org/divisions/emergency-communications/911-technology/(last accessed March 30, 2017).Non-911 addresses (denoted in the Address911 field as “N”) are maintained for location finding, public infrastructure inventory, and for various other circumstances. Location finding address points includes all intersection, 100 block numbers, and mile markers.There are two types of new addresses, In-fill and Subdivisions. In-fill addressing occurs in already developed areas that experience change. The Planning and Development Services Planning Technician updates and maintains the infill addresses, often in coordination with the City of San Marcos Fire Marshal’s office. Planning and Development Services 911 Address Coordinator creates new subdivision addressing. This feature exists in DevServices.sde. Field Information:OBJECTID- System-generated unique identifier for each record within the feature classMAXIMOID- unique identifier tie for public services asset management software; field is auto populated by IT GIS scriptMAXIMOIDPFX- unique identifier with prefix indicating (ADDR) feature tie for public services asset management software; field is auto populated by IT GIS scriptSAN- Site Address Number, assigned based on CAPCOG guidelines; alias: ADDRESSPRD- Prefix Directional (N, S, E, W); alias: PREFIX DIRECTIONSTN- Street Name; alias: STREET NAME; domain: ST_TYPESTS- Street Suffix; alias: STREET TYPEUNIT_NUM- FULLADDR- all caps concatenation of PRD + STN + STS (field calculate with this expression: ucase ([SAN] &" "& [PRD]&" "& [STN]&" "& [STS])UNIT TYPE*- values include: APT, ACSRY, BLDG, CLBHSE, CONDO, DUP, STE- these values , ; domain: ServUnitTypeZIP CODE- Zipcode- currently all 78666 COUNTY- Hays, Caldwell, Comal, or GuadalupeADDINFO*- used to add information about address, such as Business or Complex name or address type SF (single-family), intersection, etc.; alias DESCRIPTIONADDRESS911- yes or no value distinguishes 911 addresses from non-911 addresses; domain: YORNPOINT_X- Calculated geometry for “X Coordinate of Point” in PCS: NAD 1983 StatePlane Texas South Central FIPS 4204 Feet using Decimal DegreesPOINT_Y- Calculated geometry for “X Coordinate of Point” in PCS: NAD 1983 StatePlane Texas South Central FIPS 4204 Feet using Decimal DegreesCREATEDBY- system generated value based on log in ID CREATEDDATE- system generated value in UTMMODIFIEDBY- system generated value based on log in IDMODIFIEDDATE- system generated value in UTMSHAPE System-generated geometry type of the featureADDRESS_TYPE*- used to add information about addressGlobalID-System-generated unique identifier for each record that is required in replicated geodatabases*Indicate field is not consistent. The feature is under audit and overhaul in 2017 and 2018. Project will encompass and establish specific, consistent descriptors, update and add domains, compare and correct, as needed, consistency with these features: AptSteNum, Condo, Apartment, MFHousing, Parcel, Building, Centerline and Street address ranges
Copyright Text: City of San Marcos Planning and Development Services. Original points were created as polygon to point from the parcel feature by Joni Hickey in late 90's or early 2000's.
Description: MyPermitNow generates the points in this feature as addresses verify, and as the status of a project changes. For the most up-to-date information about a permit, please visit MyPermitNow.org. ‘Landuse’ field indicates designation of the permit, such as residential, commercial, institutional, multi-family, ect. The ‘Type’ field will provide information about the project such as new, remodel, public improvements, addition, certificate of occupancy, ect.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>Permit_FloodFlag is comprised of ExternalData.GIS.FloodHazardArea_1 (FHA) merged with Benson\User files\Engineering\Eng. Files\GIS Eng. Mapping Directory\Richard Reynosa\Flood Data\Database\FloodAnalysisData.gdb\fp100plus2ft. The FHA had the following definition queries on the Floodway (ZONE_SUBTY = 'FLOODWAY') layer file and the 100 Year Floodplain (FLD_ZONE = 'A' OR FLD_ZONE = 'AE' OR FLD_ZONE = 'AO' AND ZONE_SUBTY NOT LIKE 'FLOODWAY') layer file when the merge tool was run. </SPAN></SPAN></P><P><SPAN /></P><P><SPAN STYLE="font-size:12pt">Metadate from the FEMA FHA features: It’s the final preliminary information FEMA will be moving forward with toward publishing the new maps. They still have to go through a public review process. But this is the latest information the City will use to regulate new development. - RichardReynosa. Hays, Caldwell, Guadalupe and Comal Counties.</SPAN></P><P><SPAN STYLE="font-size:12pt">Sent April 21, 2017 Flood Hazard areas. Definition queries based on the following information</SPAN></P><P><SPAN STYLE="font-size:12pt">Floodway - ZONE_SUBTY = 'FLOODWAY'; 100 year Floodplain - FLD_ZONE = 'A' OR FLD_ZONE = 'AE' OR FLD_ZONE = 'AO' AND ZONE_SUBTY NOT LIKE 'FLOODWAY' 500 year FloodPlain - FLD_ZONE = 'X' AND ZONE_SUBTY = '0.2 PCT ANNUAL CHANCE FLOOD HAZARD'</SPAN></P></DIV></DIV></DIV>
Description: Updated FEMA data of the four counties surrounding the city of San Marcos. Caldwell last update from FEMA 7feb2017Comal last update from FEMA 5aug2019Guadalupe last update from FEMA 13dec2019Hays last update from FEMA 30oct2019County data merged together 18feb2020 (A. Essington)
Copyright Text: National Flood Hazard Layer (NFHL) https://www.floodmaps.fema.gov/NFHL/status.shtml
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>OBJECTID: System-generated unique identifier for each record within the feature class.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>SOURCE: Organization that provided the data. </SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>NAME: Name to which the plume is associated to which is mainly given from the TCEQ. </SPAN></SPAN></P><P /><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>MEDIALINK: URL for a website related to the record.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PRODUCTIONNOTES: Technical notes from GIS personnel.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>DESCRIPTION: Statement illustrating the feature.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>CREATEDBY: Name of the person logged into the system that GIS automatically stamps as the original creator. </SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>CREATEDDATE: Date/time stamp from the moment the GIS record was created.</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>MODIFIEDBY: Name of the person logged into the system that GIS automatically stamps as the feature is modified. </SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>MODIFIEDDATE: Date/time stamp from the last moment the GIS record was changed.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>SHAPE: System-generated geometry type of the feature.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Shape.len: System-generated length of the feature.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>GlobalID: System-generated unique identifier for each record that is required in replicated geodatabases.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>About the Housing Tax Credit Program</SPAN></P><P><SPAN>The Housing Tax Credit program is administered by Texas Department of Housing and Community Affairs (</SPAN><A href="https://www.tdhca.state.tx.us:443/" STYLE="text-decoration:underline;"><SPAN>https://www.tdhca.state.tx.us/</SPAN></A><SPAN>). The program awards tax credits to eligible participants in order to offset a portion of their federal tax liability in exchange for the production or preservation of affordable rental housing. Investors benefit from the reduced tax liability in exchange for their investment and communities benefit from quality developments that are required to operate as rent restricted housing for up to 30 years or more. </SPAN></P><P><SPAN>This feature shows the Low Income Housing Tax Credit (LIHTC) projects located in San Marcos Texas. </SPAN></P></DIV></DIV></DIV>
Color: [225, 225, 225, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: Areas in San Marcos city limits aggregated by zoning code. Attributes include zone code, zoning district, case number, residential status, sector number, and SF zoning status.
Color: [78, 78, 78, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Perpetua Titling MT Font Style: normal Font Weight: normal Font Decoration: none
Description: The Extraterritorial Jurisdiction (ETJ) is the unincorporated land within three and one half (3.5) miles of San Marcos’s boundary that is not within the city limits or ETJ of another city. It is the territory where San Marcos alone is authorized to annex land. In accordance to the Texas Local Government Code Title 2 Subtitle C Chapter 42, interlocal agreements between the City of San Marcos and the City of Kyle created (Res 1987-072) and updated (Res 2013-034) an ETJ Agreement line where ETJ overlap occurred. Additional agreement lines with the City of New Braunfels (Res 1987-76R) and Uhland (2013-076) are also reflected in this feature. In 2016, a map error was discovered in the northwest area of the ETJ. This error has perpetuated in the data since 2007, when the city declared a population of 50,000 which extended the ETJ to 3.5 miles (Resolution 2007-146-R). After discussion with the City of Kyle the adjustment was made to correct this error in February 2017. The area consisted of 103 parcels northwest of Owl Hollow Rd and northeast of Hilliard Road.
Copyright Text: City of San Marcos Planning and Development Services
Description: Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines support address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network. (From ESRI Local Government Model "RoadCenterline" Feature)**This dataset was significantly revised in August of 2014 to correct for street segments that were not properly split at intersections. There may be issues with using data based off of the original centerline file. ** The column Speed Limit was updated in November 2014 by the Transportation Intern and is believed to be accurate** The column One Way was updated in November of 2014 by core GIS and is believed to be accurate.[MAXIMOID] A unique id field used in a work order management software called Maximo by IBM. Maximo uses GIS CL data to assign locations to work orders using this field. This field is maintained by the Transportation GIS specialists and is auto incremented when new streets are digitized. For example, if the latest digitized street segment MAXIMOID = 999, the next digitized line will receive MAXIMOID = 1000, and so on. STREET NAMING IS BROKEN INTO THREE FIELDS FOR GEOCODING:[PREFIX] (Text,3) This field is attributed if a street name has a prefix such as W, N, E, or S.[NAME] (Text,44) Domain with all street names. The name of the street without prefix or suffix.[ROAD_TYPE] (alias,[SUFFIX]) (Text,4) Describes the type of road aka suffix, if applicable. CAPCOG Addressing Guidelines Sec 504 U. states, “Every road shall have corresponding standard street suffix…” standard street suffix abbreviations comply with USPS Pub 28 Appendix C Street Abbreviations. Examples include, but are not limited to, Rd, Dr, St, Trl, Ln, Gln, Lp, CT. [LEFT_LOW] (Integer,10) The minimum numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 101.[LEFT_HIGH] (Integer,10) The largest numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 201.[LOW](Integer,10) The minimum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 100.[HIGH] (Integer,10)The maximum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 200.[ALIAS] (Text,30) Alternative names for roads if known. This field is useful for geocode re-matching. [CLASS] (Text,15)The functional classification of the centerline. For example, Minor (Minor Arterial), Major (Major Arterial). THIS FIELD IS NOT CONSISTENTLY FILLED OUT, NEEDS AN AUDIT. [FULLSTREET] (Text,30) The full name of the street concatenating the [PREFIX], [NAME], and [SUFFIX] fields. For example, "W San Antonio St."[ROWWIDTH] (Double,38) Width of right-of-way along the CL segment. Data entry from Plat by Planning GIS Or from Engineering PICPs/ CIPs.[NUMLANES] (Double,38) Number of striped vehicular driving lanes, including turn lanes if present along majority of segment. Does not inlcude bicycle lanes. [LANEMILES] (Double,38) Describes the total length of lanes for that segment in miles. It is manually field calculated as follows (( [ShapeLength] / 5280) * [NUMLANES]) and maintained by Transportation GIS.[SPEEDLIMIT] (Text,5) Speed limit of CL segment if known. If not, assume 30 mph for local and minor arterial streets. If speed limit changes are enacted by city council they will be recorded in the Traffic Register dataset, and this field will be updating accordingly. Initial data entry made by CIP/Planning GIS and maintained by Transportation GIS.[YRBUILT] replaced by [DateBuilt] See below. Will be deleted. 4/21/2017[LASTYRRECON] (alias [RECONSTRUCTION]) (Text,10) Is the last four-digit year a major reconstruction occurred. Most streets have not been reconstructed since orignal construction, and will have <NULL> values. The Transportation GIS Specialist will update this field. [OWNER] (Text,25) Describes the governing body or private entity that owns/maintains the CL. It is possible that some streets are owned by other entities but maintained by CoSM. Possible attributes include, CoSM, Hays Owned/City Maintained, TxDOT Owned/City Maintained, TxDOT, one of four counties (Hays, Caldwell, Guadalupe, and Comal), TxState, and Private.[ST_FROM] (Text,50) Centerline segments are split at their intersections with other CL segments only. This field names the nearest cross-street in the From- direction. Should be edited when new CL segments that cause splits are added. [ST_TO] (Text,50) Centerline segments are split at their intersections with other CL segments only. This field names the nearest cross-street in the To- direction. Should be edited when new CL segments that cause splits are added. [PAV_WID] (Double,38) Pavement width of street in feet from back-of-curb to back-of-curb. This data is entered from as-built by CIP GIS. In January 2017 Transportation Dept. field staff surveyed all streets and measured width from face-of-curb to face-of-curb where curb was present, and edge of pavement to edge of pavement where it was not. This data was used to field calculate pavement width where we had <null> values. A value of 1 foot was added to the field calculation if curb and gutter or stand up curb were present (the face-of-curb to back-of-curb is 6 in, multiple that by 2 to find 1 foot). If no curb was present, the value enter in by the field staff was directly copied over. If values were already present, and entered from asbuilt, they were left alone. [ONEWAY] (Text,50) Field describes direction of travel along CL in relation to digitized direction. If a street allows bi-directional travel it is attributed "B", a street that is one-way in the From_To direction is attributed "F", a street that is one-way in the To_From direction is attributed "T", and a street that does not allow travel in any direction is attibuted "N". [ROADLEVEL] (Double,38) Field will be aliased to [MINUTES] and be used to calculate travel time along CL segments in minutes using shape length and [SPEEDLIMIT]. Field calculate using the following expression: [MINUTES] = ( ([SHAPE_LENGTH] / 5280) / ( [SPEEDLIMIT] / 60 ))[ROWSTATUS] (Text,15) Values include "Open" or "Closed". Describes whether a right-of-way is open or closed. If a street is constructed within ROW it is "Open". If a street has not yet been constructed, and there is ROW, it is "Cosed". [ASBUILT] (Text,200) field used to hyper link as-built documents detailing construction of the CL. Field was added in Dec. 2016. [DateBuilt] (Date) Date field used to record month and year a road was constructed. Data was collected previously without month information. Data without a known month is entered as "1/1/YYYY". When month and year are known enter as "M/1/YYYY". Month and Year from asbuilt. Added by Engineering/CIP.