Name: Address Points

Display Field: ST_NAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: This dataset includes address structure points within Lyon County, MN. the dataset structure points are in the GAC / MnGEO format. A significant portion of the dataset was developed between 2006 to 2018, In 2019 GAC (Geospatial Advisory Committee) elements were added. In 2020 MnGeo elements were added. Also at that time Lyon County restructured data to improve data quality. If you find any concern with the dataset then please contact Lyon County, MN Geographic Information Systems Department.This data supports sub address information such as apartment units. However at this time none have been added to the dataset. The format that is used to include sub addresses are different between the MnGEO and GAC schema. The MnGeo has 5 fields. The GAC format has only 2 fields that contain data In addition the dataset contains 2 fields that allow users to further describe the sub address type. No determination has been made regarding to which is proffered. Adjustments may be made depending on the needs of MnGEO, GAC, neighboring counties, Sheriff's Department, how much data is stored, and the complexity needed to translate between formats.The access points are generally located over a building structure as the data was originally intended to be used for plat maps that were created between 2010-2015.Sub-Address Data:The standard for sub address information is different between the MnGEO / NENA format and the GAC format. NENA provides 5 preset attributes including Building, Floor, Unit, Room, Seat as well as one generic Additional Location Information Field. GAC on the other hand provides two key value pairs for the sub address type and sub address identifier as well as a generic Additional Location Information Field. The NENA format is beneficial because it is the standard nationwide and it also have 5 containers. The GAC format may be beneficial because it allows us to describe information better such as Entrance A, East Wing, etc. The limit of only having 2 fields (3 with the generic location information field) is that we cannot describe as many things. That being said, it will be doubtful that we will need that many fields.I intend to keep the GAC format. However, there are a couple considerations:How do I convert my GAC data to the NENA format?How do I convert neighboring NENA data into the GAC format.Should I not convert data as sub addresses outside of my provisioning boundary may be out of scope for our needs.I could maintain both fields in my dataset. However, what happens if there is a discrepancy between the GAC and NENA fields?Other datasets may or may not including the primary addresses. For example is 101 Main Street, 101 Main Street Unit 1, and 101 Main Street Unit 2 maintained or are only the units maintained such as 101 Main Street Unit 1, 101 Main Street Unit 2. This possibly may make it difficult to assimilate data from other organizations.

Service Item Id: 5bccf9ce32ce44e0b7d9830d01c03772

Copyright Text: Lyon County, MN

Default Visibility: false

MaxRecordCount: 2000

MaxSelectionCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 7854.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -1.06969736978E7
YMin: 5495811.9683
XMax: -1.06414708521E7
YMax: 5563467.153999999
Spatial Reference: 102100  (3857)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSMSCircle
Color: [25, 0, 255, 255]
Size: 10.0
Angle: 0.0
XOffset: 0
YOffset: 0
Outline:
[0, 0, 0, 255] Width: 0
Label: N/A
Description: N/A
Transparency: 15
Labeling Info:
Label Placement: esriServerPointLabelPlacementAboveRight
Label Expression: N/A
Use Coded Values: true
Symbol:
Color: [0, 77, 168, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 10
Font Family: AvenirNext LT Pro Medium
Font Style: normal
Font Weight: bold
Font Decoration: none

Min. Scale: 3064.0
Max. Scale: 0.0

Feature Draw Order:

N/A

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
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
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: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• ADDRESS ( type: esriFieldTypeString, alias: Full Address, length: 200 )
• LG_ADDRESS ( type: esriFieldTypeString, alias: Legacy Address, length: 40 )
• ANUMBER ( type: esriFieldTypeInteger, alias: Address Number )
• ST_NAME ( type: esriFieldTypeString, alias: Street Name, length: 60 )
• ST_CONCAT ( type: esriFieldTypeString, alias: Street Name Full, length: 150 )
• LST_NAME ( type: esriFieldTypeString, alias: Legacy Street Name, length: 75 )
• LST_CONCAT ( type: esriFieldTypeString, alias: Legacy Street Name Full, length: 86 )
• POSTCOMM ( type: esriFieldTypeString, alias: Postal Community Name, length: 40 )
• MSAG_C ( type: esriFieldTypeString, alias: MSAG Community Name, length: 30 )
• PROP_CITY ( type: esriFieldTypeString, alias: Propercase Postal Community Name, length: 40 )
• ZIP ( type: esriFieldTypeString, alias: ZIP Code, length: 5 )
• CTU_NAME ( type: esriFieldTypeString, alias: CTU Name, length: 100 )
• LANDMARK ( type: esriFieldTypeString, alias: Complete Landmark Name, length: 150 )
• COUNTY_PIN ( type: esriFieldTypeString, alias: County Parcel Unique Identifier, length: 22 )

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

  Iteminfo   Thumbnail   Metadata