Description: ORIGINALSOURCE: Accuracy context for the record. This is what we know to be the original source from the data input. This may not be known from old input data. UPDATESOURCE: Accuracy context for the record. This field represents the latest spatial update to the record. This field will be overwritten. For instance, the original source could have been from an Asbuilt but it was then GPS’d in the field so the new Update Source is Differential GPS. LOCATIONDESCRIPTION: Statement illustrating the whereabouts of a feature.NAME: Name the retrofit site as it is referred to with modeling and/or location based.OWNERSHIP: Organization with jurisdiction over the real-world feature represented in the feature class. Acronyms are listed below for clarity. COSM: City of San MarcosHCISD: Hays County Independent School DistrictSMCISD: San Marcos Consolidated Independent School DistrictTXDOT: Texas Department of TransportationUPRR: Union Pacific RailroadMAINTAINED: Organization responsible for the care of the real-world feature represented in the feature class. Acronyms are listed below for clarity. COSM: City of San MarcosHCISD: Hays County Independent School DistrictSMCISD: San Marcos Consolidated Independent School DistrictTXDOT: Texas Department of TransportationUPRR: Union Pacific RailroadLANDDEVELOPMENTTYPE: The type of land that this retrofit site is on which references the aquifers. RECEIVING: PROJECTID: LINKID: MEDIALINK: URL for a website related to the record.PRODUCTIONNOTES: Technical notes from GIS personnel.DESCRIPTION: Statement illustrating the feature.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.GlobalID: System-generated unique identifier for each record that is required in replicated geodatabases.
Copyright Text:
Default Visibility: true
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 0
Max Scale: 0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
XMin: NaN
YMin: NaN
XMax: NaN
YMax: NaN
Spatial Reference: 102740
(2278)
Description: OBJECTID: System-generated unique identifier for each record within the feature class.MAXIMOID: ID given to all features in order of creation and autopopulated with scripts. MAXIMOIDPFX: Prefix given to the MaximoID that identifies the feature type.PFX: This is the prefix that is given to a feature for Maximo to identify its type. ORIGINALSOURCE: Accuracy context for the record. This is what we know to be the original source from the data input. This may not be known from old input data. UPDATESOURCE: Accuracy context for the record. This field represents the latest spatial update to the record. This field will be overwritten. For instance, the original source could have been from an Asbuilt but it was then GPS’d in the field so the new Update Source is Differential GPS. ACCEPTANCEDATE: The date at which the bond is accepted through Engineering and Capital Improvements Department. WARRANTYDATE: The date at which the bond expires; typically 1 or 2 years after the acceptance date and this information is provided by the Engineering and Capital Improvements Department. LOCATIONDESCRIPTION: Statement illustrating the whereabouts of a feature.FUNCTION: Additional designation of the feature. Includes the following:BIORETENTION: This is the process in which contaminants and sedimentation are removed from the stormwater runoff. It is collected into this treatment area which has grass buffer strips, sand bed, ponding area, organic layers, planting soil and plants. BIOSWALE: This is landscape elements designed to concentrate or remove silt and pollution out of surface runoff water. They consist of swaled drainage course with gently sloped slides (less than 6%) and filled with vegetation, compost and/or riprap. DETENTION: A basin without control gates used for temporary storage of storm water during peak periods of downpour.GREENROOF: These are unique in that they have the ability to capture and retain a volume of rain from each rainstorm. This captured water is then evapotranspired back to the atmosphere through the green roof vegetation. MODULAR WETLAND: This is the only stormwater system to utilize horizontal flow biofiltration. This replaces the downward flow systems. This horizontal flow system allows for smaller footprints with higher flows. OTHER: Anything other than what is already listed but is not abundant enough for a category. PERMIABLE PAVERS: Allow for stormwater runoff to filter through surface voids into an underlying stone reservoir for temporary storage and/or infiltration. RAIN GARDEN: It is a planted shallow depression that collects rainwater runoff from roofs, parking lots, and other surfaces. RETENTION: A basin without control gates used for permanent storage of stormwater runoff. UNKNOWN: It is not yet determined what type of water storage the feature is. WETLAND: Used to reduce peak runoff rates and require sufficient drainage areas and dry weather base flows to function properly. FORMTYPE: OWNERSHIP: Organization with jurisdiction over the real-world feature represented in the feature class. Acronyms are listed below for clarity. COSM: City of San MarcosHCISD: Hays County Independent School DistrictSMCISD: San Marcos Consolidated Independent School DistrictTXDOT: Texas Department of TransportationUPRR: Union Pacific RailroadMAINTAINED: Organization responsible for the care of the real-world feature represented in the feature class. Acronyms are listed below for clarity. COSM: City of San MarcosHCISD: Hays County Independent School DistrictSMCISD: San Marcos Consolidated Independent School DistrictTXDOT: Texas Department of TransportationUPRR: Union Pacific RailroadRECHARGEZONE: This is whether or not the structure is inside the area in which water enters an aquifer. In a recharge zone surface water or precipitation percolate through relatively porous, unconsolidated, or fractured materials, such as sand moraine deposits or cracked basalt that lie over a water bearing or aquifer, formation. It is a yes, no or unknown field with domains. MEDIALINK: URL for a website related to the record.PRODUCTIONNOTES: Technical notes from GIS personnel.DESCRIPTION: Statement illustrating the feature.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.area: System-generated area 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.
Description: Traffic Signals - Includes Traffic Signal Lights, and point features for Intersections."Non-Operational" indicates that masts and/or signal lights are present but are not operational."Traffic Signal Light" indicates a present, operating Signal Light"Signal Intersection" is a single point to indicate an intersection that contains signalsUpdated with individual signals by MPECK (Transportation GIS) on April 6th, 2015.
Description: Attributes include:Width in feetProject name (associated construction project, etc)Condition (Good, Fair or Poor)Verified (YorN)Inspection DateMaterialCommentStatus (Built, Proposed, etc)
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>[StName] the roadway name on which the work will occur alongside.</SPAN></P><P><SPAN>[St_From] one of the typically perpendicular crosstrees bounding the StName. Note that no importance is given to digitized direction, as this is just a way to describe the bounds of the sidewalk improvement. </SPAN></P><P><SPAN>[St_To] one of the typically perpendicular crosstrees bounding the StName, but opposite the St_From value. Note that no importance is given to digitized direction, as this is just a way to describe the bounds of the sidewalk improvement. </SPAN></P><P><SPAN>[ProjectDesc] a description of the project, such as "E Hopkins St Sidewalk Installation and gap in-fill"</SPAN></P><P><SPAN>[Responsibility] domain value field that describes which project is planning to the do the sidewalk maintenance or installation. </SPAN></P><P><SPAN>[WorkType] describes the type of maintenance planned, either "New Sidewalk" or "Maintenance". "New Sidewalk" describes sidewalk that is being constructed for the first time, to either fill in gaps, or install for an entire roadway or neighborhood. "Maintenance" describes work that we repair existing sidewalk, which often times means the old sidewalk is ripped out and new installed. Maintenance is more costly than new sidewalk installs. </SPAN></P><P><SPAN>[Year] the four digit year the work is being planned. You may see lots of records with year designation 2055. These were projects that are deemed to be future CIP projects, but since a year has not been determined, some arbitrary distance year was used. </SPAN></P><P><SPAN>[Status] status of the project. Completed, future, onhold, in progress...</SPAN></P><P><SPAN>[CompletedDate] the date the project was completed, if known. If not known use the closest month and year, and use 15 for the day. </SPAN></P><P><SPAN>[Comment] everybody knows what this is. </SPAN></P></DIV></DIV></DIV>
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. 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. 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". UPDATE: This feature class only has CL geometries for "Open" rights-of-way. This field should be deleted or re-purposed. [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 from Asbuilt. 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. [ACCEPTED] (Date) Date field used to record the month, day, and year that a roadway was officially accepted by the City of San Marcos. Engineering signs off on acceptance letters and stores these documents. This field was added in May of 2018. Due to a lack of data, the date built field was copied into this field for older roadways. Going forward, all new roadways will have this date. . This field will typically be populated well after a road has been drawn into GIS. Entered by Engineering/CIP.[WARRANTY_EXP] (Date) Date field used to record the expiration date of a newly accepted roadway. Typically this is one year from acceptance date, but can be greater. This field was added in May of 2018, so only roadways that have been excepted since and older roadways with valid warranty dates within this time frame have been populated.
Description: Polygon of road surface where the bridge is at a higher level than the adjacent roadReceived in August, 2014 along with the other Aerial/Planimetric data from CAPCOG.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The layer contains 21 different parking layers that are all accounted for, some of them are unused though. The following fields also describe it's purpose and information. </SPAN></P><UL><LI><P><SPAN>The Restriction Field has information that acknowledges if parking is available all day, if there are time restrictions for the area and the type of parking zone. For example, a field might say (Residential Parking - Mon-Fri 8 AM to 5 PM). This tells the user that this area is for neighborhood parking during the hours of 8 AM until later in the day at 5 PM during business days. </SPAN></P></LI></UL><UL><LI><P><SPAN>The Side Field determines where the zone is placed and what directional area the zone is taking place. For example, whether that be on a North side or South side if it was only one lane for parking or both sides if it is both lanes being used for the parking zones. </SPAN></P></LI></UL><UL><LI><P><SPAN>The Location Name Field determines where the area of parking is at. It gives the street name to help determine the area. For example, (CM Allen Pkwy) tell us where the parking zone is located. </SPAN></P></LI></UL><UL><LI><P><SPAN>The Location Field tells whether the parking is located on the street or a parking lot. </SPAN></P></LI></UL><UL><LI><P><SPAN>The Usage Field tells whether the area contains Free, Paid, Permit, No Parking, Official use and Right of Way Parking rights. </SPAN></P></LI></UL><P><SPAN /></P></DIV></DIV></DIV>
Description: Polygon for all PavementReceived in August, 2014 along with the other Aerial/Planimetric data from CAPCOGSee the GIS Manager for more details