Name: Parcels

Display Field: ParcelKey

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The Township uses two survey systems. The first was 1859 District Lot system which still describes many properties near the Fraser River. The District Lot system was superseded in 1873 with the New Westminster Township Section system which covers the bulk of the municipality and is used to the present day. The cadastral data set originated as hand drawn township-section maps in imperial scales. The lot lines were compiled from historical community maps, registered legal plans surveyed with astronomic bearings and legal descriptions where no surveys exist. In the late 1970’s the Township's maps were converted to metric scales and all dimension annotation was converted manually to metric. In 1982 parcels BC GAS manually digitized the hand drawn township-section maps and assembled them into a single continuous cadastral fabric encompassing the entire township. The lot line data was rubber sheeted to fit the higher accuracy mapping of neighbouring municipalities, no interior control points were used. In 1983 Langley Township obtains BC GAS Intergraph format lot line data and translated it into Terrasoft format for the Township's GIS.In 1986 the lot lines were converted to parcel polygons linked to BCAA folio numbers and Tempest. In 1987 map annotation was converted to digital. In 1999 the GIS data was converted from Terrasoft to AutoCAD Map format. In 2000 the digital base was again rubber sheeted with a township wide grid pattern of survey monuments used for control. In 2003 lot links were converted from BCAA folio numbers to Township property numbers. In 2004 GIS data is converted from AutoCAD Map format to Munsys Oracle format. In 2005 Langley Township adopts DIGITAL LEGAL SURVEY PLAN STANDARDS and new cadastral is entered directly from high accuracy UTM projected surveys. In 2009 GIS data was converted from Munsys Oracle format to ESRI ArcSDE format.

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 10000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 523332.35309999995
YMin: 5427761.2206999995
XMax: 539528.3095000004
YMax: 5450724.83
Spatial Reference: 26910  (26910)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [104, 104, 104, 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: false
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: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• ParcelKey ( type: esriFieldTypeString, alias: ParcelKey, length: 50 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• Created_Date ( type: esriFieldTypeDate, alias: Created_Date, length: 8 )
• Created_User ( type: esriFieldTypeString, alias: Created_User, length: 15 )
• Modified_Date ( type: esriFieldTypeDate, alias: Modified_Date, length: 8 )
• Modified_User ( type: esriFieldTypeString, alias: Modified_User, length: 15 )
• Comments_Sys ( type: esriFieldTypeString, alias: Comments_Sys, length: 150 )
• Comments_User ( type: esriFieldTypeString, alias: Comments_User, length: 150 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• SHAPE.STArea() ( type: esriFieldTypeDouble, alias: SHAPE.STArea() )
• SHAPE.STLength() ( type: esriFieldTypeDouble, alias: SHAPE.STLength() )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata