View In:   ArcGIS Online Map Viewer

Name: Parcel Boundaries

Display Field: ACCTID

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The Tax Lot Polygons dataset was captured for the Worcester County, Maryland GIS Response Mapping project which occurred from Fall, 2005 to Summer, 2007. The source materials for this data include Maryland Tax Maps, 2004 Aerial Photography, Maryland Tax Records, and Subdivision Plats available from MD State Archives' Plats.net system and town management/utilities maps. Where possible, subdivision plats were utilized to develop property lines using Coordinate Geometry (COGO) techniques. The COGO attributes such as line length and bearing are stored within the line feature Tax_LN feature class. The property lines were then rotated to propertly fit the subdivision as seen on the 1' 2004 aerial photography. The property polygons were then constructed from the property lines using ArcMap's Topology Toolbar and the polygons were attributed. For areas in which subdivision plats were not available, the property boundaries were heads up digitized from the tax map with consideration to the underlying aerial photography and the visible man made features such as buildings, driveways, fence lines etc. During the heads up digitization process, the property's legal area as stored within the tax records was also considered. The town management/utility maps were utilized as they often gave an accurate representaiton of the road right-a-way in towns and depicted, portions of property/lot lines. These too were used similarly to the tax maps in terms of heads up vectorization and consideration of visible features in the aerial photography. Worcester County TSD has received updated parcel data from MDP for Ocean City, on 6/22/10. The OC parcels were deleted and replaced with the 6/22/10 OC parcels. Worcester County does not maintain the OC parcels therefore, a periodic update of OC parcels will occur. . Note There is no plotyline file updates for Ocean City so the tax_ln file for Worcester Co. excludes OC parcels.Worcester County GIS has been and continues to update the Parcel boundaries utilizing plats as obtained from plats.net based on subdivisions, and basic Quality Control by searching the plats.net web site archives, etc.. Note there are many parcels that were originally created with little accurate information, The QC of this parcel layer is an ongoing effort by Worcester GIS analyst as plats and boundary surveys become available.

Service Item Id: fb23a66f14cf454999e147f61f5d6cfb

Copyright Text: Spatial Systems Associates, Inc.

Default Visibility: true

MaxRecordCount: 2000

MaxSelectionCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 12000.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: -75.67424008217345
YMin: 37.95936252921318
XMax: -75.04655562612105
YMax: 38.50311036327231
Spatial Reference: 4326  (4326)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [130, 130, 130, 0]
Outline:
Style: esriSLSSolid
Color: [0, 112, 255, 255]
Width: 1
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: true
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: false
Supports Sql Format: false
Supports Query Analytic: false
Supports Query With Current User: true

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 )
• ACCTID ( type: esriFieldTypeString, alias: ACCTID, editable: true, nullable: true, length: 16, defaultValue: null, modelName: ACCTID )
• LOT ( type: esriFieldTypeString, alias: LOT, editable: true, nullable: true, length: 5, defaultValue: null, modelName: LOT )
• PARCEL ( type: esriFieldTypeString, alias: PARCEL, editable: true, nullable: true, length: 5, defaultValue: null, modelName: PARCEL )
• SOURCE ( type: esriFieldTypeString, alias: SOURCE, editable: true, nullable: true, length: 50, defaultValue: null, modelName: SOURCE )
• MAP ( type: esriFieldTypeString, alias: MAP, editable: true, nullable: true, length: 5, defaultValue: null, modelName: MAP )
• SECTION_ ( type: esriFieldTypeString, alias: SECTION_, editable: true, nullable: true, length: 5, defaultValue: null, modelName: SECTION_ )
• BLOCK ( type: esriFieldTypeString, alias: BLOCK, editable: true, nullable: true, length: 5, defaultValue: null, modelName: BLOCK )
• IMG_PATH ( type: esriFieldTypeString, alias: IMG_PATH, editable: true, nullable: true, length: 255, defaultValue: null, modelName: IMG_PATH )
• TECH ( type: esriFieldTypeSmallInteger, alias: Technician, editable: true, nullable: true, defaultValue: null, modelName: TECH , Coded Values: [0: AdamTomko] , [1: AdamTravis] , [2: BrianBlake] , ...17 more... )
• COMMENTS ( type: esriFieldTypeString, alias: COMMENTS, editable: true, nullable: true, length: 255, defaultValue: null, modelName: COMMENTS )
• DATE_CREATED ( type: esriFieldTypeDate, alias: DATE_CREATED, editable: true, nullable: true, length: 8, defaultValue: null, modelName: DATE_CREATED )
• Taxlink ( type: esriFieldTypeString, alias: Taxlink, editable: true, nullable: true, length: 255, defaultValue: null, modelName: Taxlink )
• Acres ( type: esriFieldTypeDouble, alias: Acres, editable: true, nullable: true, defaultValue: null, modelName: Acres )
• IMAGELNK ( type: esriFieldTypeString, alias: IMAGELNK, editable: true, nullable: true, length: 250, defaultValue: null, modelName: IMAGELNK )
• created_user ( type: esriFieldTypeString, alias: created_user, editable: false, nullable: true, length: 255, defaultValue: null, modelName: created_user )
• created_date ( type: esriFieldTypeDate, alias: created_date, editable: false, nullable: true, length: 8, defaultValue: null, modelName: created_date )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, editable: false, nullable: true, length: 255, defaultValue: null, modelName: last_edited_user )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, editable: false, nullable: true, length: 8, defaultValue: null, modelName: last_edited_date )
• Shape__Area ( type: esriFieldTypeDouble, alias: SHAPE.area, editable: false, nullable: true, defaultValue: null, modelName: SHAPE.area, required: true )
• Shape__Length ( type: esriFieldTypeDouble, alias: SHAPE.len, editable: false, nullable: true, defaultValue: null, modelName: SHAPE.len, required: true )

Templates:

• Name: Parcel Boundaries
  Description:
  Prototype:
  IMAGELNK: null
  ACCTID: null
  LOT: null
  PARCEL: null
  SOURCE: null
  MAP: null
  SECTION_: null
  BLOCK: null
  IMG_PATH: null
  TECH: null
  COMMENTS: null
  DATE_CREATED: null
  Taxlink: null
  Acres: null
  
  Drawing Tool: esriFeatureEditToolPolygon

Capabilities: Query,Create,Update,Delete,Uploads,Editing

Sync Can Return Changes: false

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

Child Resources:

Supported Operations:   Query   Apply Edits   Add Features   Update Features   Delete Features   Calculate   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata   Update Metadata