Description: Attribute/Field NameTypeField DescriptionField ValueDescriptionFID*Object IDObjectIDShape *GeometryType of shape used THOROUGFATextType of Project (Enhanced or Proposed)Enhanced Facility ThoroughfareEnhanced SegmentProposed Facility ThroughfareProposed SegmentSTREETTYPETextFunctional ClassificationSTStreet (Includes Commercial Street (CS), Road (RD), Residential Street (RS))AVAvenueBVBoulevardHWHighwayPKWYParkwayCROSSSECTITextProposed Cross-section of the roadwayXX ###-##Functional Classification Width of Right-of-Way - Width of Pavement PRIORITYTextPrioritization of the Facility Short: 0-10 years0-10 yearsMedium: 10-20 years10-20 yearsLong: 20+ years20+ yearsN/ANot ApplicablePRIORITY_GTextPrioritization of the Facilities for the CIP Map 1Short Term (0-10 years)2Mid Term (10-20 years)3Long Term (20+ years)9Not Included in Prioritization (City Use)0Not Included in Prioritization (City Use)BikePlanTextBicycle Facility BBBuffered Bike LaneCTCycle TrackCT/BBCycle Track or Buffered Bike LaneCT/SPCycle Track or Shared Use PathSHSharrowsSPShared Use Path WSWide ShoulderNONENo Bike Facility N/ANot ApplicableSeg_NameTextName of Facility Segment used in Cost EstimatesA-#Avenue Facility Segment #B-#Boulevard Facility Segment #H-#Parkway Facility Segment #S-#Street Facility Segment #S-#-IZStreet Facility Segment # located in an Intensity ZonePA-#Proposed Avenue Facility Segment #PA-#-IZProposed Avenue Facility Segment # located in an Intensity ZonePB-#Proposed Boulevard Facility Segment #PH-#Proposed Parkway Facility Segment #PS-#Proposed Street Facility Segment #PS-#-IZProposed Street Facility Segment # located in an Intensity ZoneIH 35IH 35 Facility Segment *DOWNTOWNSegment located in Downtown *ROWTextRight of Way Classification for the facilityCOMMERCIALGREENFIELDRESIDENTIAL NONEShape_LengthDoubleLength of roadway segment (Feet)NumLanesShortNumber of Lanes of the Roadway SegmentRoadwayDivStringLength of roadway segment (Feet)Divided Roadway is divided UndividedRoadway is undivided For segments labeled Option_XXX-## in Attribute XS_HDR, the cross-section labeled is an optional cross-section and not designated. For polylines labeled DOWNTOWN in Attribute Seg_Name, the Cross-section classification is based on Option E-1 from the Downtown Analysis.*There are no Cost Estimate provided for IH 35 or DOWNTOWN at this time.GIS SDE Attributes:OBJECTID: System-generated unique identifier for each record within the feature class.CREATEDBY: Name of the person logged into the system that GIS automatically stamps as the original creator.CREATEDDATE: Date/time stamp from the moment the GIS record was created.MODIFIEDBY: Name of the person logged into the system that GIS automatically stamps as the feature is modified.MODIFIEDDATE: Date/time stamp from the last moment the GIS record was changed. SHAPE: System-generated geometry type of the feature.Shape.len: System-generated length of the feature.GlobalID: System-generated unique identifier for each record that is required in replicated geodatabases.
Copyright Text: HDR Engineering, City of San Marcos
Description: Attribute/Field NameTypeField DescriptionField ValueDescriptionFID*Object IDObjectIDShape *GeometryType of shape used THOROUGFATextType of Project (Enhanced or Proposed)Enhanced Facility ThoroughfareEnhanced SegmentProposed Facility ThroughfareProposed SegmentSTREETTYPETextFunctional ClassificationSTStreet (Includes Commercial Street (CS), Road (RD), Residential Street (RS))AVAvenueBVBoulevardHWHighwayPKWYParkwayCROSSSECTITextProposed Cross-section of the roadwayXX ###-##Functional Classification Width of Right-of-Way - Width of Pavement PRIORITYTextPrioritization of the Facility Short: 0-10 years0-10 yearsMedium: 10-20 years10-20 yearsLong: 20+ years20+ yearsN/ANot ApplicablePRIORITY_GTextPrioritization of the Facilities for the CIP Map 1Short Term (0-10 years)2Mid Term (10-20 years)3Long Term (20+ years)9Not Included in Prioritization (City Use)0Not Included in Prioritization (City Use)BikePlanTextBicycle Facility BBBuffered Bike LaneCTCycle TrackCT/BBCycle Track or Buffered Bike LaneCT/SPCycle Track or Shared Use PathSHSharrowsSPShared Use Path WSWide ShoulderNONENo Bike Facility N/ANot ApplicableSeg_NameTextName of Facility Segment used in Cost EstimatesA-#Avenue Facility Segment #B-#Boulevard Facility Segment #H-#Parkway Facility Segment #S-#Street Facility Segment #S-#-IZStreet Facility Segment # located in an Intensity ZonePA-#Proposed Avenue Facility Segment #PA-#-IZProposed Avenue Facility Segment # located in an Intensity ZonePB-#Proposed Boulevard Facility Segment #PH-#Proposed Parkway Facility Segment #PS-#Proposed Street Facility Segment #PS-#-IZProposed Street Facility Segment # located in an Intensity ZoneIH 35IH 35 Facility Segment *DOWNTOWNSegment located in Downtown *ROWTextRight of Way Classification for the facilityCOMMERCIALGREENFIELDRESIDENTIAL NONEShape_LengthDoubleLength of roadway segment (Feet)NumLanesShortNumber of Lanes of the Roadway SegmentRoadwayDivStringLength of roadway segment (Feet)Divided Roadway is divided UndividedRoadway is undivided For segments labeled Option_XXX-## in Attribute XS_HDR, the cross-section labeled is an optional cross-section and not designated. For polylines labeled DOWNTOWN in Attribute Seg_Name, the Cross-section classification is based on Option E-1 from the Downtown Analysis.*There are no Cost Estimate provided for IH 35 or DOWNTOWN at this time.GIS SDE Attributes:OBJECTID: System-generated unique identifier for each record within the feature class.CREATEDBY: Name of the person logged into the system that GIS automatically stamps as the original creator.CREATEDDATE: Date/time stamp from the moment the GIS record was created.MODIFIEDBY: Name of the person logged into the system that GIS automatically stamps as the feature is modified.MODIFIEDDATE: Date/time stamp from the last moment the GIS record was changed. SHAPE: System-generated geometry type of the feature.Shape.len: System-generated length of the feature.GlobalID: System-generated unique identifier for each record that is required in replicated geodatabases.
Copyright Text: HDR Engineering, City of San Marcos
Description: TypeField DescriptionField ValueDescriptionObject IDObjectIDGeometryType of shape used TextType of the Greenway/Trail Enhanced Facility GreenwayGreenway/Trail is enhancedProposed Facility Greenway Greenway/Trail is proposedTextClassification of Greenway/TrailUNDEVELOPEDA majority of the land along the Greenway/Trail has no built structuresNEEDS IMPROVEMENTAn existing path which should be upgraded as part of the Greenway/TrailPEDESTRIAN CROSSINGA segment of the Greenway/Trail is crossing a roadway, water feature, or requires a grade separated crossingNATURALGreenway/Trail exists of an unpaved natureBUILTA path of desired material and size currently existsUNKNOWNFurther information is neededTextOwnership of the land the Greenway/TrailPUBLIC/EXISTING EASEMENTMajority of the Greenway/Trail is on public land or an existing easementROWMajority of the Greenway/Trail is along an existing or proposed ROWTEXAS STATE UMajority of the Greenway/Trail is on Texas State University landUNKNOWNFurther information is neededPRIVATEMajority of the Greenway/Trail is on private propertyDoubleLength in miles, as calculated in GISLong IntegerLength in feet, as calculated in GISTextProposed Grade Separated Crossing along Greenway/TrailYesGrade-separated pedestrian crossing along Greenway/TrailNoNo grade-separated pedestrian crossings along Greenway/TrailN/ANot Applicable; new grade-separation not recommended along Existing TrailsLong IntegerUnique Project Number for Proposed Greenway/Trail projects starting at 1. (All Project_No that are 0 are existing facilities)TextMinimum Width of Greenway/Trail Project (feet)TextSurface Material usedCONCRETEConcrete in areas of higher use and flood-prone areasLIMESTONELimestone in areas of less use where a natural path is desiredN/AExisting Path, Materials only specified for Proposed pathsTextName of Street/Land the Greenway/Trail runs alongTextStarting Limit of the Greenway/TrailTextEnding Limit of the Greenway/TrailTextAt-Grade Pedestrian Crossings along Greenway/TrailYesAt-grade pedestrian crossing along Greenway/TrailNoneNo at-grade pedestrian crossings along Greenway/TrailTextPrioritizationSHORT0-10 YearsMEDIUM10-20 YearsLONG20+ YearsPDDProposed Short-Term Greenway on Planned Development or SubdivisionTextLength of segment (Feet)
Copyright Text: HDR Engineering, City of San Marcos
Description: The EPZ feature Zone Determination method as written in the Technical Manual as supprot for Section 6.5.2.1-Overall Operational Lightning Levels:(A.) Designation of a property's zone is done subsequent to approval of all Legislative and Subdivision actions of this code. The designation utilizes the City of San Marcos's GIS files and the data in place at the time of the designation.(1) All property designated as open space on the City of San Marcos Future Land Use Map is designated as Environmental Performance Zone E-4.(2) A 350 foot wide overlay is established around the boundaries of the designated open space.(3) A 350 foot wide highway corridor is established along IH-35, SH 123. SH 20 no1th of Snake Creek and portions of SH 80 west of the Blanco River and Arterials within the CBA and east of Hunter Road.(4) Arterials and highways west of the CBA and Hunter road are excluded from this corridor to preserve the environmental and historic character of the hill country as a back drop to the city.(5) A Performance zone measure of E-1 is designated for all non-residential lots (not designated E-4) with frontage within the 350' highway corridor for IH 35 and not designated as open space.(6) A Performance zone measure of E-2 is designated for all non-residential lots (not designated E-1 or E-4) with frontage within a 700' wide highway corridor along IH 35 and all non-residential lots (not designated E-1 or E-4) with frontage within a 350' wide highway corridor along SH 123. SH 20 north of Snake Creek and portions of SH 80 west of the Blanco River and Arterials within the CBA and east of Hunter Road.(7) All remaining properties which are predominantly residential or are commercial uses in a predominantly residential area are designated as a Performance zone measure of E-3.Data Fields:[EPZ]- Environmental Performance Zone[MaxAvgHzfc]- Maximum Average Light Level in Horizontal foot-candles measured at grade[Description]- Type of area in which zone is applicable
Copyright Text: City of San Marcos Planning & Development Services
Description: Intent. The Intent of the urban stormwater management district is to: Provide for appropriate stormwater management in areas designated as high intensity zones on the preferred scenario map. Provide for efficient regional stormwater management controls within the urban watershed area. Support the efforts of the Edwards Aquifer Habitat Conservation Plan and the Watershed Protection Plan to protect the San Marcos River by: a. Protecting the biological integrity of the river habitat; b. Managing stormwater runoff rate, volume, and velocity; c. Reducing stormwater pollution concentrations and loads; d. Preventing the increase of soil deposition within the river, and e. Preventing the increase of river bank erosion.
Copyright Text: City of San Marcos Planning and Engineering Depts.
Brian K. Reis, PE, CFM
Central Texas Infrastructure Manager
Reis, Brian K. [mailto:BKReis@lan-inc.com]
Description: San Marcos River Corridor (SMRC), Water Quality Overlay for CodeSMTX Chapter 6 Section 2. This feature is resultant of the following criteria: 1) areas along the San Marcos River north and west of Interstate Highway 35 are equivalent to the current SMRC as defined in Section 5.3.1.1 of San Marcos, Texas Land Development Code; 2) areas along the San Marcos River east and south of Interstate Highway 35 are based on the greater of either the FEMA Advisory Base Flood Elevation (ABFE) 2015 (Cite panel) or a 1000’ buffer generated from the NHDflowline (USGS National Hydrography Dataset (NHD) Best Resolution for Texas 20160414 State or Territory FileGDB 10.1) of the San Marcos River and 1000’ feet up the Blanco River from the confluence. Updates as needed, based on FEMA floodplain maps; water quality monitoring data; effectiveness of CodeSMTX article 6.2.2.1.
Copyright Text: City of San Marcos Engineering, Planning and Developement Services
Description: 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. 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.Sent April 21, 2017Flood Hazard areas. Definition queries based on the following informationFloodway - 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'
Description: MyPermitNow populates this feature when an address is verified. The attribute data is auto-populated by MyPermitNow; the geometry is copied from the Development Services Address Point feature (point feature). Field Description below:Project Name- Name of Project, the name is typically determined by developerPlanning Case Number- the case number is made up of three fields for Zoning Case types and four fields for Subdivision Case types. For Example:Zoning Case Types: (Case TypeAbbreviation) – (2 digit Year) – (Submittal Number)i.e. AN-18-01, this is the first annexation case of 2018Subdivision Case Types: (PC) - (2 digit Year) – (Submittal Number) – (Plat Type)i.e. PC-18-25_03 this is the 25th platting case of 2018 and is a final platPlat Type Designations (Concept Plat _01; Preliminary Plat_02; Final Plat_03; Replat_04; Amending Plat_05Case Type– Current Subdivision Case Types: Associated Documents- Link to project in MyPermitNow (aka myGovermentOnline) Applicant Name- Name of ApplicationApplicant Business- Name of Applicants BusinessProject Description- Short description of projectCase Manager- Name of planner assigned to the caseCase Manager Contact- Phone number or email of assigned plannerAcres- Acres listed on applicationAddress- Address listed on applicationStatus- Project Status, such as Completed or Awaiting Revisions, as set by Case ManagerProposed # Lots- Proposed number of legal lots (Subdivision Cases only)Proposed # SF Lots- Proposed number of Single Family legal lots (Subdivision Cases only)Proposed Land Use- Typically set by Case ManagerMeeting1- Public Hearing date 1Meeting2- Public Hearing date 2Meeting3- Public Hearing date 3Meeting4- Public Hearing date 4Meeting5- Public Hearing date 5Meeting6- Public Hearing date 6Note1- Space for Editor commentNote2- Space for Editor comment
Copyright Text: Planning and Development Services, P. Phillips
Description: Ordinance Number 2017-37, Home Share Rentals, adopted by the City of San Marcos City Council on August 1, 2017 establishes rules and registration requirements for Home Share Rentals less than 30 days. Approved with the Ordinance:Add Home Share Rentals as a separate use in the land use matrixDefine Home Share Rentals as the primary use on a property where no individual lives on a permanent basisAllow Home Share Rentals as a conditional use only in residential areasExpand the restriction of only one registration being permitted per personEnforcement will be primarily based on complaints. The Director of Neighborhood Services has authority to deny renewal of a registration; suspend a current registration; or revoke a registration if the standards of the Home Share Ordinance or any other Federal, State, or Local Law are violated.Fields are auto-populated via the online permitting and application portal MyPermitNow. https://www.mygovernmentonline.org/
Description: The feature points indicate places designated historic by either City of San Marcos ordinance (4.2.5.1) or the Texas Historical Commission (THC). Attributes for each point include, name and address. Ordinance numbers for landmarks designated in CoSM Land Development Code (LDC) are provided. Category indicates either Historical Marker or National Registry Listing as defined by THC; Marker_Typ and HistRelev are unverified fields. Designating authority has been verified through THC website and CoSM LDC. Address error for the First Christian Church of San Marcos was corrected from 216 W San Antonio St to 222 W San Antonio St at request of Historic Preservatio Officer (August 2018).
Copyright Text: City of San Marcos Land Development Code Section 4.2.5.1 - HD, Historic District, CoSM Ordinances 1986-81, 2004-16, 2007-20; Texas Historical Commission, Texas Historical Commission Atlas http://atlas.thc.state.tx.us/; Jeanette Chamorro compilation and review of the data.
Description: Boundaries of Neighborhoods that belong to Council of Neighborhood Association (CONA). CONA is a non profit organized for the general purpose of bringing neighborhoods together and to protect and advance the interests of neighborhoods.Boundaries were expanded to include as many residential properties as possible.The CIty of San Marcos updates the information herein when CONA provides new information.
Copyright Text: Betsy Robertson - CONA President sheldes86@yahoo.com Redrawn July 2013.
Latest Update 09/04/2018- Information received from Kirk Abbott- Engineering via City Clerk Office via Amy Kirwin
02/23/2016- Information received from Kevin Burke- Economic and Development Projects Coordinator
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.
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: MyPermitNow populates this feature when an address is verified. The attribute data is auto-populated by MyPermitNow; the geometry is created from the Development Services Address Point feature (point feature) or the Development Services Proposed Development feature (polygon feature).Field Description below:Project Name- Name of Project, the name is typically determined by developerPlanning Case Number- the case number is made up of three fields for Zoning Case types and four fields for Subdivision Case types. For Example:Zoning Case Types: (Case TypeAbbreviation) – (2 digit Year) – (Submittal Number)i.e. AN-18-01, this is the first annexation case of 2018Subdivision Case Types: (PC) - (2 digit Year) – (Submittal Number) – (Plat Type)i.e. PC-18-25_03 this is the 25th platting case of 2018 and is a final platPlat Type Designations (Concept Plat _01; Preliminary Plat_02; Final Plat_03; Replat_04; Amending Plat_05Case Type– Current Subdivision Case Types: Associated Documents- Link to project in MyPermitNow (aka myGovermentOnline) Applicant Name- Name of ApplicationApplicant Business- Name of Applicants BusinessProject Description- Short description of projectCase Manager- Name of planner assigned to the caseCase Manager Contact- Phone number or email of assigned plannerAcres- Acres listed on applicationAddress- Address listed on applicationStatus- Project Status, such as Completed or Awaiting Revisions, as set by Case ManagerProposed # Lots- Proposed number of legal lots (Subdivision Cases only)Proposed # SF Lots- Proposed number of Single Family legal lots (Subdivision Cases only)Proposed Land Use- Typically set by Case ManagerMeeting1- Public Hearing date 1Meeting2- Public Hearing date 2Meeting3- Public Hearing date 3Meeting4- Public Hearing date 4Meeting5- Public Hearing date 5Meeting6- Public Hearing date 6Note1- Space for Editor commentNote2- Space for Editor comment
Copyright Text: Planning and Development Services, P. Phillips
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: 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.