View In:   ArcGIS Online Map Viewer

Name: Building Footprints

Display Field: buildingty

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Initial Data Capture: </SPAN><SPAN /></P><P STYLE="margin:0 0 11 0;"><SPAN>Building were originally digitized using ESRI construction tools such as rectangle and polygon. Textron Feature Analyst was then used to digitize buildings using a semi-automated polygon capture tool as well as a fully automated supervised learning method. The method that proved to be most effective was the semi-automated polygon capture tool as the fully automated process produced polygons that required extensive cleanup. This tool increased the speed and accuracy of digitizing by 40%.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Purpose of Data Created: </SPAN><SPAN /></P><P STYLE="margin:0 0 11 0;"><SPAN>To supplement our GIS viewers with a searchable feature class of structures within Ventura County that can aid in analysis for multiple agencies and the public at large.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Types of Data Used: </SPAN><SPAN /></P><P STYLE="margin:0 0 11 0;"><SPAN>Aerial Imagery (Pictometry 2015, 9inch ortho/oblique, Pictometry 2018, 6inch ortho/oblique) Simi Valley Lidar Data (Q2 Harris Corp Lidar) </SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Coverage of Data:</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>Buildings have been collected from the aerial imageries extent. The 2015 imagery coverage the south county from the north in Ojai to the south in thousand oaks, to the east in Simi Valley, and to the West in the county line with Santa Barbara. Lockwood Valley was also captured in the 2015 imagery. To collect buildings for the wilderness areas we needed to use the imagery from 2007 when we last flew aerial imagery for the entire county. 2018 Imagery was used to capture buildings that were built after 2015.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Schema: </SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>Fields: APN, Image Date, Image Source, Building Type, Building Description, Address, City, Zip, Data Source, Parcel Data (Year Built, Basement yes/no, Number of Floors) Zoning Data (Main Building, Out Building, Garage), First Floor Elevation, Rough Building Height, X/Y Coordinates, Dimensions. </SPAN></SPAN></P></LI></UL><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Confidence Levels/Methods:</SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>Address data: </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>90% </SPAN></SPAN><SPAN><SPAN>All Buildings should have an address if they appear to be a building that would normally need an address (Main Residence). To create an address, we do a spatial join on the parcels from the centroid of a building polygon and extract the address data and APN. To collect the missing addresses, we can do a spatial join between the master address and the parcels and then the parcels back to the building polygons. Using a summarize to the APN field we will be able to identify the parcels that have multiple buildings and delete the address information for the buildings that are not a main residence.</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>Building Type Data: </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>99% </SPAN></SPAN><SPAN>All buildings should have a building type according to the site use category code provided from the parcel table information. To further classify multiple buildings on parcels in residential areas, the shape area field was used to identify building polygons greater than 600 square feet as an occupied residence and all other buildings less than that size as outbuildings. All parcels, inparticular parcels with multiple buildings, are subject to classification error. Further defining could be possible with extensive quality control </SPAN></P></LI><LI><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>APN Data: </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>98% </SPAN></SPAN><SPAN><SPAN>All buildings have received APN data from their associated parcel after a spatial join was performed. Building overlapping parcel lines had their centroid derived which allowed for an accurate spatial join.</SPAN></SPAN></P></LI></UL><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Troubleshooting Required: </SPAN><SPAN /></P><P STYLE="margin:0 0 11 0;"><SPAN>Buildings would sometimes overlap parcel lines making spatial joining inaccurate. To fix this you create a point from the centroid of the building polygon, join the parcel information to the point, then join the point with the parcel information back to the building polygon.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN /></P></DIV></DIV></DIV>

Copyright Text: ITSD GIS

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:

XMin: 6115890.083389476
YMin: 1840542.236842975
XMax: 6370531.726336136
YMax: 2118580.171907723
Spatial Reference: 102645  (2229)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [252, 207, 207, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields:

• objectid ( type: esriFieldTypeOID, alias: OBJECTID, editable: false, nullable: false, defaultValue: null, modelName: OBJECTID )
• buildingty ( type: esriFieldTypeString, alias: Building Type, editable: true, nullable: true, length: 50, defaultValue: null, modelName: BUILDINGTY )
• building_d ( type: esriFieldTypeString, alias: Building Description, editable: true, nullable: true, length: 254, defaultValue: null, modelName: BUILDING_D )
• apn ( type: esriFieldTypeString, alias: Assessor Parcel Number, editable: true, nullable: true, length: 10, defaultValue: null, modelName: APN )
• address ( type: esriFieldTypeString, alias: Full Address, editable: true, nullable: true, length: 50, defaultValue: null, modelName: ADDRESS )
• city ( type: esriFieldTypeString, alias: City, editable: true, nullable: true, length: 50, defaultValue: null, modelName: CITY )
• zip ( type: esriFieldTypeString, alias: Zip Code, editable: true, nullable: true, length: 50, defaultValue: null, modelName: ZIP )
• data_sourc ( type: esriFieldTypeString, alias: Data Source, editable: true, nullable: true, length: 50, defaultValue: null, modelName: Data_Sourc )
• imagesourc ( type: esriFieldTypeString, alias: Image Source, editable: true, nullable: true, length: 50, defaultValue: null, modelName: IMAGESOURC )
• imagedate ( type: esriFieldTypeString, alias: IMAGEDATE, editable: true, nullable: true, length: 4, defaultValue: null, modelName: IMAGEDATE )
• z_min ( type: esriFieldTypeDouble, alias: Z Min, editable: true, nullable: true, defaultValue: null, modelName: Z_Min )
• height ( type: esriFieldTypeInteger, alias: Height, editable: true, nullable: true, defaultValue: null, modelName: Height )
• situs_nr ( type: esriFieldTypeString, alias: Situs Number, editable: true, nullable: true, length: 9, defaultValue: null, modelName: SITUS_NR )
• situs_dir ( type: esriFieldTypeString, alias: Situs Direction, editable: true, nullable: true, length: 2, defaultValue: null, modelName: SITUS_DIR )
• situs_stre ( type: esriFieldTypeString, alias: Situs Street Name, editable: true, nullable: true, length: 25, defaultValue: null, modelName: SITUS_STRE )
• situs_typ ( type: esriFieldTypeString, alias: Situs Type, editable: true, nullable: true, length: 2, defaultValue: null, modelName: SITUS_TYP )
• situs_unit ( type: esriFieldTypeString, alias: Situs Unit, editable: true, nullable: true, length: 10, defaultValue: null, modelName: SITUS_UNIT )
• yr_blt ( type: esriFieldTypeString, alias: Year Built, editable: true, nullable: true, length: 4, defaultValue: null, modelName: YR_BLT )
• flr_1a ( type: esriFieldTypeString, alias: First Floor Sq Ft, editable: true, nullable: true, length: 5, defaultValue: null, modelName: FLR_1A )
• flr_2a ( type: esriFieldTypeString, alias: Second Floor Sq Ft, editable: true, nullable: true, length: 5, defaultValue: null, modelName: FLR_2A )
• flr_3a ( type: esriFieldTypeString, alias: Third Floor Sq Ft, editable: true, nullable: true, length: 5, defaultValue: null, modelName: FLR_3A )
• bsmt_a ( type: esriFieldTypeString, alias: Basement, editable: true, nullable: true, length: 5, defaultValue: null, modelName: BSMT_A )
• xcoord ( type: esriFieldTypeDouble, alias: X-COORD, editable: true, nullable: true, defaultValue: null, modelName: XCOORD )
• ycoord ( type: esriFieldTypeDouble, alias: Y-COORD, editable: true, nullable: true, defaultValue: null, modelName: YCOORD )
• created_date ( type: esriFieldTypeDate, alias: CREATED_DATE, editable: false, nullable: true, length: 8, defaultValue: null, modelName: CREATED_DATE )
• last_edited_date ( type: esriFieldTypeDate, alias: LAST_EDITED_DATE, editable: false, nullable: true, length: 8, defaultValue: null, modelName: LAST_EDITED_DATE )
• globalid ( type: esriFieldTypeGlobalID, alias: GLOBALID, editable: false, nullable: false, length: 38, defaultValue: null, modelName: globalid )
• Shape__Area ( type: esriFieldTypeDouble, alias: st_area(shape), editable: false, nullable: false, defaultValue: null, modelName: st_area(shape) )
• Shape__Length ( type: esriFieldTypeDouble, alias: st_length(shape), editable: false, nullable: false, defaultValue: null, modelName: st_length(shape) )

Templates:

• Name: Building Footprints
  Description:
  Prototype:
  ycoord: null
  buildingty: null
  building_d: null
  apn: null
  address: null
  city: null
  zip: null
  data_sourc: null
  imagesourc: null
  imagedate: null
  z_min: null
  height: null
  situs_nr: null
  situs_dir: null
  situs_stre: null
  situs_typ: null
  situs_unit: null
  yr_blt: null
  flr_1a: null
  flr_2a: null
  flr_3a: null
  bsmt_a: null
  xcoord: null
  
  Drawing Tool: esriFeatureEditToolPolygon

Capabilities: Query,Extract

Sync Can Return Changes: true

Is Data Versioned: true

Supports Rollback On Failure: false

Supports ApplyEdits With Global Ids: false

Edit Fields Info:

• Creation Date Field: created_date
• Creator Field: created_user
• Edit Date Field: last_edited_date
• Editor Field: last_edited_user

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations:   Query   Query Attachments   Query Analytic   Calculate   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata