20211004 07225700 1.0 FGDC CSDGM Metadata FALSE AddressStructurePoints 002 Projected GCS_WGS_1984 Linear Unit: Meter (1.000000) WGS_1984_Web_Mercator_Auxiliary_Sphere <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/3.5.0'><WKT>PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Mercator_Auxiliary_Sphere"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],PARAMETER["Auxiliary_Sphere_Type",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",3857]]</WKT><XOrigin>-20037700</XOrigin><YOrigin>-30241100</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102100</WKID><LatestWKID>3857</LatestWKID></ProjectedCoordinateSystem> 20250916 08252800 20250916 08252800 500000 5000 ItemDescription Esri ArcGIS 13.5.3.57366 Address Structure Points This dataset identifies the location of addresses within Lyon County, MN. The address points are generally placed over a building structure. <DIV STYLE="text-align:Left;"><DIV><DIV>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:<UL><LI>How do I convert my GAC data to the NENA format?</LI><LI>How do I convert neighboring NENA data into the GAC format.</LI><LI>Should I not convert data as sub addresses outside of my provisioning boundary may be out of scope for our needs.</LI><LI>I could maintain both fields in my dataset. However, what happens if there is a discrepancy between the GAC and NENA fields?</LI><LI>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.</LI></UL> </DIV></DIV></DIV> Lyon County, MN Address Points Lyon County MN ADP Structure Points E9-1-1 NG9-1-1 911 <DIV STYLE="text-align:Left;"><DIV><DIV>This data is not freely distributed. Source data should be requested directly from the Lyon County GIS Department. Use of the data contained in this layer is restricted to the cooperative agreement policy. If you have a copy of this dataset without permission then please destroy it. In no case may any receiving organization may not redistribute the data even if it is in a modified format.Disclaimer: The County of Lyon makes no warranties, guarantees, or representations regarding the information provided on the Lyon County Geographic Information System. All information provided in the Geographic Information System is available on an as is basis, and carries no actual or implied warranty of merchantability or fitness for a particular use. Lyon County does not warrant the information against deficiencies of any kind. Use of the information on the Lyon County Public Geographic Information System indicates that the user accepts this disclaimer of all warranties and assumes the risk of any defects or deficiencies of any kind. The user of the information contained in the Geographic Information System, by accepting the disclaimer of warranties herein, further accepts and agrees that the County of Lyon and any of its officers, agents or employees are not liable for damages of any type arising from the use of the information herein, whether direct, consequential, incidental, special or punitive.Please do not use the air photos, or any line work as a substitute for a survey.</DIV></DIV></DIV> File Geodatabase Feature Class dataset EPSG 6.18.3(9.3.1.2) 0 Simple FALSE 0 TRUE FALSE AddressStructurePoints Feature Class 0 OBJECTID OBJECTID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Shape Geometry 0 0 0 Feature geometry. Esri Coordinates defining the features. ANUMBER Address Number Integer 4 0 0 ST_NAME Street Name String 60 0 0 POSTCOMM Postal Community Name String 40 0 0 ADDRESS Full Address String 200 0 0 ST_CONCAT Street Name Full String 150 0 0 ZIP ZIP Code String 5 0 0 PROP_CITY Propercase Postal Community Name String 40 0 0 LST_NAME Legacy Street Name String 75 0 0 LST_CONCAT Legacy Street Name Full String 86 0 0 CTU_NAME CTU Name String 100 0 0 LG_ADDRESS Legacy Address String 40 0 0 LANDMARK Complete Landmark Name String 150 0 0 COUNTY_PIN County Parcel Unique Identifier String 22 0 0 MSAG_C MSAG Community Name String 30 0 0 20250916