| snippet:
|
The street Curbs layer is an arc-based dataset that displays the locations and types of all curb lines in the city of Harrisonburg, VA. This layer will be used in conjunction with Cityworks. The data can be digitized using aerial imagery, or can be collected using a GPS-compatible device. Each line in the database should be an accurate representation of what is on the street.
The information already contained within the dataset has been manually collected by the City of Harrisonburg, which has employed the means mentioned above to create and populate the data layer. |
| summary:
|
The street Curbs layer is an arc-based dataset that displays the locations and types of all curb lines in the city of Harrisonburg, VA. This layer will be used in conjunction with Cityworks. The data can be digitized using aerial imagery, or can be collected using a GPS-compatible device. Each line in the database should be an accurate representation of what is on the street.
The information already contained within the dataset has been manually collected by the City of Harrisonburg, which has employed the means mentioned above to create and populate the data layer. |
| accessInformation:
|
The Curbs data layer was created by Alfredo Gutierrez Velasquez in the Public Works Department of the City of Harrisonburg, on 6/1/2016. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg. |
| thumbnail:
|
|
| maxScale:
|
5000 |
| typeKeywords:
|
[] |
| description:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>INDEX</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 1: </SPAN></SPAN><SPAN><SPAN>Responsible Parties</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 2: </SPAN></SPAN><SPAN><SPAN>Explanation of Attribute Data</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 3: </SPAN></SPAN><SPAN><SPAN>Handling of Data and Recommendations</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 4: </SPAN></SPAN><SPAN><SPAN>Additional Considerations</SPAN></SPAN></P><P /><P /><P><SPAN STYLE="font-weight:bold;"><SPAN>SECTION 1</SPAN></SPAN><SPAN><SPAN> </SPAN></SPAN></P><P STYLE="font-weight:bold;"><SPAN><SPAN>Responsible Parties</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-style:italic;"><SPAN>Parties responsible for updating this layer:</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>- The Public Works Department is responsible for updating and maintaining this layer. Additions or editing of features within this layer should be administered or approved by the Asset Manager.</SPAN></P><P /><P STYLE="font-weight:bold;"><SPAN><SPAN>SECTION 2</SPAN></SPAN></P><P STYLE="font-weight:bold;"><SPAN><SPAN>Explanation of Attribute Data</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Length</SPAN></SPAN><SPAN><SPAN> – (feet) the total length or the curb feature</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>InstallDate</SPAN></SPAN><SPAN><SPAN> - this is the year that the curb was physically installed.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>OwnedBy</SPAN></SPAN><SPAN><SPAN> - designation of the entity that has ownership of the curb.</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>City</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Other</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 24;"><SPAN><SPAN>Notes:</SPAN></SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN><SPAN>- Domain: “Curb_Owned_By”</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>MaintainedBy</SPAN></SPAN><SPAN><SPAN> - designation of the entity that is responsible for maintaining the curb.</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>City</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Other</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 24;"><SPAN><SPAN>Notes:</SPAN></SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN><SPAN>- Domain: “Curb_Maintained_By”</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>LastInspectionDate</SPAN></SPAN><SPAN><SPAN> - date of the last inspection on the curb.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Condition</SPAN></SPAN><SPAN><SPAN> – conditional status that describes the curb - this should be found in the Inspection Report.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>ConditionDate</SPAN></SPAN><SPAN><SPAN> – date that the condition of the curb was inspected.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Enabled</SPAN></SPAN><SPAN><SPAN> – 1 or 0</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Attachment</SPAN></SPAN><SPAN><SPAN> – static photo of the curb.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Plan Link</SPAN></SPAN><SPAN><SPAN> – file path to location where site plans for the corresponding curb is found.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>InspectionsLink</SPAN></SPAN><SPAN><SPAN> - link to the City Works report form.</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Location – </SPAN></SPAN><SPAN><SPAN>closest address to curb’s location, full address - without ZIP code</SPAN></SPAN><SPAN><SPAN>.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>PlanDate </SPAN></SPAN><SPAN><SPAN>– date of the site plan where the corresponding curb is found.</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>UniqueID - </SPAN></SPAN><SPAN><SPAN>Unique identifying value assigned to a feature, generally same as OBJECTID. Assets created after May 2023 follow new UniqueID value: Month & Year + OBJECTID – Example: If the asset was created in June of 2023, the Unique ID will be 0623 - OBJECTID</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>created_user</SPAN></SPAN><SPAN><SPAN> – default editor tracking field, who created the feature.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>created_date</SPAN></SPAN><SPAN><SPAN> – default editor tracking field, when the feature was created.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>last_edited_user</SPAN></SPAN><SPAN><SPAN> – default editor tracking field, who last edited the feature.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>last_edited_date</SPAN></SPAN><SPAN><SPAN> - default editor tracking field, when the feature was last edited.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>CurbType</SPAN></SPAN><SPAN><SPAN> – type of curb that the line represents.</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Curb</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Curb and Gutter</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 24;"><SPAN><SPAN>Notes:</SPAN></SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN><SPAN>- Domain: “Curb_Type_1”</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>GlobalID</SPAN></SPAN><SPAN><SPAN> - default editor tracking field, unique serial number for the feature.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Shape</SPAN></SPAN><SPAN><SPAN> – geometric shape of these features are polylines.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Shape.STLength()</SPAN></SPAN><SPAN><SPAN> – default field, length of the polyline.</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;"><SPAN><SPAN>SECTION 3</SPAN></SPAN></P><P><SPAN><SPAN>Handling of Data and Recommendations</SPAN></SPAN></P><P /><TABLE><TBODY><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Title of</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Handling</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Topic #1</SPAN></SPAN></P></TD><TD><P><SPAN><SPAN>[Brief advice/description of how to address a specific component of/issue related to the data.]</SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Title of</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Handling</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Topic #2</SPAN></SPAN></P></TD><TD><P><SPAN><SPAN>[Brief advice/description of how to address a specific component of/issue related to the data.]</SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Title of</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Handling</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Topic #3</SPAN></SPAN></P></TD><TD><P><SPAN><SPAN>[Brief advice/description of how to address a specific component of/issue related to the data.]</SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Title of</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Handling</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Topic #4</SPAN></SPAN></P></TD><TD><P><SPAN><SPAN>[Brief advice/description of how to address a specific component of/issue related to the data.]</SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Title of</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Handling </SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Topic #5</SPAN></SPAN></P></TD><TD><P><SPAN><SPAN>[Brief advice/description of how to address a specific component of/issue related to the data.]</SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </SPAN></SPAN></P></TD></TR></TBODY></TABLE><P /><P /><P STYLE="font-weight:bold;"><SPAN><SPAN>SECTION 4</SPAN></SPAN></P><P><SPAN><SPAN>Additional Considerations</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>A. History & Logic of the Data</SPAN></SPAN></P><P STYLE="font-style:italic;margin:0 0 0 48;"><SPAN><SPAN>[For future reference, please list facets of the history of the decision-making process related to the data’s use – the </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>how</SPAN></SPAN><SPAN><SPAN> and </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>why</SPAN></SPAN><SPAN><SPAN> things were specifically done the way that they were.] (If the data should be handled/collected a specific way, that should be listed and explained here.)</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>------</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- Initial Planning: Image below shows how curb segments will be defined.</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN> </SPAN></P><P /><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>8/27/2018 – Curb segments are now to be grouped into block-lengths, or from street intersection to street intersection. This does not include driveway or commercial entrances, if a segment is divided by these features then both segments on either side of the feature are to be merged together. Segments should end on the corner of an adjoining street intersection. Additionally, segments on the other side of the road should be included in the feature, if there is a segment on the opposite side of the street, within the length of the block, then the features should be merged together.</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>B. Department Notes</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- Cityworks will need to track:</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Last Inspection Date</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Condition</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Last Maintenance Date</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Schedule Maintenance</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>C. Unresolved Questions</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- Geometric Network & Drains to MS4?</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>D. Other</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- N/A</SPAN></SPAN></P></DIV></DIV></DIV> |
| licenseInfo:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data is intended to be used by COH - PWD street maintenance crew.</SPAN></P></DIV></DIV></DIV> |
| catalogPath:
|
|
| title:
|
Street Curbs Data |
| type:
|
|
| url:
|
|
| tags:
|
["City of Harrisonburg","Harrisonburg","Public Works Department","Street","STREET","Curbs","local government","Virginia","street","streets","curb","curbs","public","public works","works","CityWorks","City Works","city works"] |
| culture:
|
en-US |
| name:
|
|
| guid:
|
|
| minScale:
|
150000000 |
| spatialReference:
|
|