20201130
09072700
1.0
FALSE
HAMCO_Buildings2019
166162.560220
273817.096879
1703127.989395
1811327.580082
1
002
Projected
GCS_North_American_1983
Linear Unit: Foot_US (0.304801)
NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.5'><WKT>PROJCS["NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",328083.3333333333],PARAMETER["False_Northing",820208.3333333333],PARAMETER["Central_Meridian",-85.66666666666667],PARAMETER["Scale_Factor",0.9999666666666667],PARAMETER["Latitude_Of_Origin",37.5],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2965]]</WKT><XOrigin>-18119800</XOrigin><YOrigin>-45615400</YOrigin><XYScale>3048.0060960121928</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2244</WKID><LatestWKID>2965</LatestWKID></ProjectedCoordinateSystem>
20201130
10304300
20201130
10304300
50000
5000
ISO 19139 Metadata Implementation Specification
Joan Keene
Hamilton County, IN
GIS Director
317-776-8254
One Hamilton County Square, Suite 206
Noblesville
IN
46060-2234
U.S.
joan.keene@hamiltoncounty.in.gov
20201130
ArcGIS Metadata
1.0
Joan Keene
Hamilton County, IN
GIS Director
317-776-8254
One Hamilton County Square, Suite 206
Noblesville
IN
46060-2234
U.S.
joan.keene@hamiltoncounty.in.gov
TBD
TBD
TBD
Hamilton County, Indiana Planimetric Mapping (2019)
Feature Class
HAMCO_Buildings2019
2019-01-01
1.0
Hamilton County, Indiana
raster digital data
Planimetrics – 2019
Hamilton County, IN
This metadata describes the collection for Hamilton County, IN. This is an update mapping project from previous data that was last updated in 2016. All features were mapped at 1" = 100' scale and feature definition was at the discretion of the Kucera stereo-compilation and GIS editing staff. Specific features of the shapefiles are documented in the 'Entity and Attribute Information' section.
Compiled mapping is a geometrically accurate representation of recorded surface features and ground conditions at the time of the corresponding aerial photography. As such, the mapping is useful for a variety of applications within a geographic information system (GIS), such as facility engineering/maintenance, city/county planning, property line review, etc. It can be used alone or as a vector basemap for corresponding raster orthophotos.
Joan Keene
Hamilton County, IN
GIS Director
317-776-8254
One Hamilton County Square, Suite 206
Noblesville
IN
46060-2234
U.S.
joan.keene@hamiltoncounty.in.gov
Westfield
Noblesville
Indiana
Carmel
White River
Geist Reservoir
Fishers
Morse Reservoir
Hamilton County
Building
EOP
River
Stream
Lake/Pond
Planimetric
Building
EOP
River
Westfield
Stream
Lake/Pond
Noblesville
Indiana
Carmel
White River
Planimetric
Geist Reservoir
Fishers
Morse Reservoir
Hamilton County
The geographic data is provided "as is". This organization makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. Also, this organization makes no warranty, either expressed or implied, regarding the condition of the product or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although these files have been processed successfully on computers at this organization, no warranty is made by this organization regarding the use of these data on any other system, nor does the fact of distribution constitute or imply such a warranty.
The orthoimages were collected under the supervision of a licensed Professional Surveyor and Mapper. Use of these data requires a general understanding of GIS and spatial data.
-86.2506731906
-85.855914925
39.9212024942
40.2243977567
Ground condition
2019-04-21
2019-04-09
The bounding coordinates in this metadata file represent the bounding coordinates for all planimetric features collected.
Version 6.2 (Build 9200) ; Esri ArcGIS 10.5.1.7333
1
-86.246500
-85.860154
40.221177
39.922879
The vector data is edited to remove duplicate points, close polygons, etc.
All agreed upon photo-interpretable features are collected using stereo compilation. In obscured areas, small and non-interpretable features may not be mapped. Thus, a detailed on-the-ground or historical analysis of an obscured area may result in inconsistencies.
Attribute accuracy (proper feature classification) is tested by manual comparison of the source with orthophotos of the corresponding area on an interactive computer graphic system.
Horizontal positional accuracy for stereo-compiled ground features is dependent upon the quality of the aerotriangulation (AT) bundle adjustment which georeferences the aerial imagery from which features are mapped. The horizontal component of the AT tested X = 0.073, Y = 0.094, feet RMS at the 95% confidence level. This value meets ASPRS Class 2 requirements for mapping at this scale.
Vertical positional accuracy for stereo-compiled ground features is dependent upon the quality of the aerotriangulation (AT) bundle adjustment which georeferences the aerial imagery from which features are mapped. The vertical component of the AT tested 0.088 foot RMS at the 95% confidence level. This value meets ASPRS Class 2 requirements for mapping at this scale.
New digital aerial imagery is collected concurrently with the lidar data and triangulated to provide stereo coverage of the project area in the desired coordinate system and datums. See orthoimage metadata for collection and processing details.
2019-01-01
IMG
IMG
Files converted to deliverable format (shapefile).
2019-01-01
PLAN
SHP, DWG
Planimetric feature collection is performed in one or more of BAE SocetSet, ZI SSK, Cardinal VROne softcopy digital stereoscopic compilation workstations.
2019-01-01
IMG
PLAN
Editing of compiled features and generated contours takes place in VrOne environment. Editing consists of layering validation, duplicate point removal, trimming lines, closing of polygons, etc. Vectors are compared to ortho product to validate geometric accuracy. All compilation is cut to project boundary. For building polygons that intersect the project boundary, the buildings are left whole.
2019-01-01
PLAN
PLAN
The map editing process performs the same two functions for the planimetric and topographic data, which is; 1. to check the data for accuracy, and 2. make the mapping more aesthetically pleasing and easy to work with. The various map features are assigned unique digital layers according to Kucera's general layering scheme (or a more "custom" layering scheme if specified by the client). "Layering" meaning the separation of like features to a unique digital level that can be viewed, located, counted or otherwise manipulated to the exclusion of other features / levels. Planimetrically, a good example of the layering system would be that all of the major buildings such as houses and commercial buildings be placed on their own layer named something like "BUILDINGS" so they can more easily be viewed or worked separately from more inconsequential structures such as small storage buildings or sheds that would be own their own layer named "MINOR BUILDINGS" or whatever the client would like those particular layers named. Other planimetric examples of the use of layering would be the use of separate digital layers to differentiate paved roads from unpaved roads, treelines from brushlines, ditches from streams, etc. Regarding the topographic end of things, the editing process is responsible for generating the contours to the contour interval specified by the client (most commonly 1', 2', or 5'...) using the digital terrain model provided by Compilation (which consists of breaklines and mass points) or by Lidar points. The contours are then checked for accuracy / consistency with the terrain model (comparing them to the elevations of the breaklines and points to make sure there aren't any anomalies, and their appearance is usually smoothed for aesthetic purposes and ease of use. Editing also adds spot elevations in appropriate locations like high / low areas in the terrain, road intersections, places where the contours are widely spaced, etc... and also labels the index contours with a numerical label to make reading contour elevations faster and easier. The finished mapping is then usually gridded, the appropriate title block information is added (info regarding the scale, contour interval, mapping location, client name, date of photography or Lidar collection, etc...), translated from Kucera's in-house editing software – primarily VrOne – into the digital format and layering scheme requested by the client (usually AutoCAD and/or ESRI) and delivered to the client on a DVD or by means of electronic delivery (email or posting to the FTP site for the client to download).
Edited Planimetric Mapping
PLAN
1.0
None
None
Kucera International Inc.
vector digital data
Ground condition
2019-01-01
Aerotriangulated digital aerial imagery is used to compile planimetric features in a softcopy stereo environment.
600
Digital Aerial Imagery
PLAN
1.0
Kucera International Inc. Willoughby, OH
None
None
Remote-sensing image and vector data
Ground condition
2019-04-09
2019-04-21
HAMCO_Buildings2019
Feature Class
0
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
SHAPE
Shape
Geometry
4
0
0
Feature geometry.
Esri
Coordinates defining the features.
LAYER
LAYER
String
50
0
0
UPDATE_STATUS
UPDATE_STATUS
String
50
0
0
Shape.STArea()
Shape.STArea()
Double
0
0
0
Shape.STLength()
Shape.STLength()
Double
0
0
0
dataset
EPSG
6.3(9.0.0)
0
Simple
FALSE
0
TRUE
FALSE