{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "The street city facilities layer displays the locations and names of buildings in the city of Harrisonburg, VA. 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.\n\nThe 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.", "description": "

INDEX<\/SPAN><\/SPAN><\/P>

Section 1: <\/SPAN><\/SPAN>Responsible Parties<\/SPAN><\/SPAN><\/P>

Section 2: <\/SPAN><\/SPAN>Explanation of Attribute Data<\/SPAN><\/SPAN><\/P>

Section 3: <\/SPAN><\/SPAN>Handling of Data and Recommendations<\/SPAN><\/SPAN><\/P>

Section 4: <\/SPAN><\/SPAN>Additional Considerations<\/SPAN><\/SPAN><\/P>

SECTION 1<\/SPAN><\/SPAN> <\/SPAN><\/SPAN><\/P>

Responsible Parties<\/SPAN><\/SPAN><\/P>

Parties responsible for updating this layer:<\/SPAN><\/SPAN><\/P>

- 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>

SECTION 2<\/SPAN><\/SPAN><\/P>

Explanation of Attribute Data<\/SPAN><\/SPAN><\/P>

UniqueID <\/SPAN>- Unique identifying value assigned to a feature, generally same as OBJECTID. Assets created after May 2023 follow new UniqueID value: Month & Year + OBJECTID \u2013 Example: If the asset was created in June of 2023, the Unique ID will be 0623 - OBJECTID<\/SPAN><\/P>

Facility Name <\/SPAN><\/SPAN>\u2013 name of facility.<\/SPAN><\/SPAN><\/P>

Dimensions (sq. ft.) <\/SPAN><\/SPAN>\u2013 square footage of building.<\/SPAN><\/SPAN><\/P>

InstallDate<\/SPAN><\/SPAN> \u2013 date of facilities installation.<\/SPAN><\/SPAN><\/P>

OwnedBy<\/SPAN><\/SPAN> - designation of the entity that has ownership of the facility.<\/SPAN><\/SPAN><\/P>

  • City<\/SPAN><\/SPAN><\/P><\/LI>

  • Other<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

    Notes:<\/SPAN><\/SPAN><\/P>

    - Domain: \u201cFacility_Owned_By\u201d<\/SPAN><\/SPAN><\/P>

    MaintainedBy<\/SPAN><\/SPAN> - designation of the entity that is responsible for maintaining the facility.<\/SPAN><\/SPAN><\/P>

    • City<\/SPAN><\/SPAN><\/P><\/LI>

    • Other<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

      Notes:<\/SPAN><\/SPAN><\/P>

      - Domain: \u201cFacility_Maintained_By\u201d<\/SPAN><\/SPAN><\/P>

      Enabled<\/SPAN><\/SPAN> \u2013 1 or 0<\/SPAN><\/SPAN><\/P>

      Attachment<\/SPAN><\/SPAN> \u2013 static photo of the facility.<\/SPAN><\/SPAN><\/P>

      Plan Link<\/SPAN><\/SPAN> \u2013 file path to location where site plans for the corresponding facility is found, not applicable for all.<\/SPAN><\/SPAN><\/P>

      created_user<\/SPAN><\/SPAN> \u2013 default editor tracking field, who created the feature.<\/SPAN><\/SPAN><\/P>

      created_date<\/SPAN><\/SPAN> \u2013 default editor tracking field, when the feature was created.<\/SPAN><\/SPAN><\/P>

      last_edited_user<\/SPAN><\/SPAN> \u2013 default editor tracking field, who last edited the feature.<\/SPAN><\/SPAN><\/P>

      last_edited_date<\/SPAN><\/SPAN> - default editor tracking field, when the feature was last edited.<\/SPAN><\/SPAN><\/P>

      GlobalID<\/SPAN><\/SPAN> - default editor tracking field, unique serial number for the feature.<\/SPAN><\/SPAN><\/P>

      Shape<\/SPAN><\/SPAN> \u2013 geometric shape of these features are polygons.<\/SPAN><\/SPAN><\/P>

      Shape.STArea()<\/SPAN><\/SPAN> \u2013 default field, area of polygon.<\/SPAN><\/SPAN><\/P>

      Shape.STLength()<\/SPAN><\/SPAN> \u2013 default field, length of the polygon.<\/SPAN><\/SPAN><\/P>

      SECTION 3<\/SPAN><\/SPAN><\/P>

      Handling of Data and Recommendations<\/SPAN><\/SPAN><\/P>

      Title of<\/SPAN><\/SPAN><\/P>

      Handling<\/SPAN><\/SPAN><\/P>

      Topic #1<\/SPAN><\/SPAN><\/P><\/TD>

      [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

      [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

      Title of<\/SPAN><\/SPAN><\/P>

      Handling<\/SPAN><\/SPAN><\/P>

      Topic #2<\/SPAN><\/SPAN><\/P><\/TD>

      [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

      [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

      Title of<\/SPAN><\/SPAN><\/P>

      Handling<\/SPAN><\/SPAN><\/P>

      Topic #3<\/SPAN><\/SPAN><\/P><\/TD>

      [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

      [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

      Title of<\/SPAN><\/SPAN><\/P>

      Handling<\/SPAN><\/SPAN><\/P>

      Topic #4<\/SPAN><\/SPAN><\/P><\/TD>

      [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

      [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

      Title of<\/SPAN><\/SPAN><\/P>

      Handling <\/SPAN><\/SPAN><\/P>

      Topic #5<\/SPAN><\/SPAN><\/P><\/TD>

      [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

      [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR><\/TBODY><\/TABLE>

      SECTION 4<\/SPAN><\/SPAN><\/P>

      Additional Considerations<\/SPAN><\/SPAN><\/P>

      A. History & Logic of the Data<\/SPAN><\/SPAN><\/P>

      [For future reference, please list facets of the history of the decision-making process related to the data\u2019s use \u2013 the <\/SPAN><\/SPAN>how<\/SPAN><\/SPAN> and <\/SPAN><\/SPAN>why<\/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>

      ------<\/SPAN><\/SPAN><\/P>

      - N/A<\/SPAN><\/SPAN><\/P>

      B. Department Notes<\/SPAN><\/SPAN><\/P>

      - N/A<\/SPAN><\/SPAN><\/P>

      C. Unresolved Questions<\/SPAN><\/SPAN><\/P>

      - N/A<\/SPAN><\/SPAN><\/P>

      D. Other<\/SPAN><\/SPAN><\/P>

      - N/A <\/SPAN><\/SPAN><\/P>

      <\/P><\/DIV><\/DIV><\/DIV>", "summary": "The street city facilities layer displays the locations and names of buildings in the city of Harrisonburg, VA. 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.\n\nThe 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.", "title": "Street City Facilities", "tags": [ "City of Harrisonburg", "Harrisonburg", "Public Works Department", "Street", "STREET", "Facilities", "local government", "Virginia", "street", "streets", "public", "public works", "works", "CityWorks", "City Works", "city works", "City Facilities", "city facilities", "buildings", "infrastructure", "city buildings" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 150000000, "maxScale": 5000, "spatialReference": "", "accessInformation": "The City Facilities data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, in 2016. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.", "licenseInfo": "" }