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.
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
Description: This dataset contains points of interest that may across Lyon County. These points may contain well known locations for general map display.
Description: The Lyon County Parcels represent geographic entities, defined by the Lyon County for the use of taxing, and identifying land ownership in Lyon County. This dataset also includes other relevant information that is stored in the county tax database. Parcels have been created using various data including title deed transactions, assessor database information, highway and survey data and other datasets. The data is not generally at survey quality and should be used for reference only. Lyon County makes no warranties, guarantees, or representations regarding the information provided All information provided is available on an as is basis and carries no actual or implied warranty of merchantability or fitness for a particular use. Lyon County 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.
Color: [115, 38, 0, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Color: [255, 0, 0, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 50000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [255, 0, 0, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Color: [255, 144, 97, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: various layers clipped to counties - The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system.The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.
Service Item Id: 5bccf9ce32ce44e0b7d9830d01c03772
Copyright Text: Federal Emergency Management Agency
Description: This layer is a subset of the MNDNR 100K lakes layer, which is now known as the dnr https://gisdata.mn.gov/dataset/water-dnr-hydrographyI think the lakes in this layer are cira 2003. I have noticed that some of the lakes have since been removed from the hydrography layer. I contacted Zeb Thomas from the DNR to see if he could provide a cira 2003 lake layer so that I can verify if the 100k layer is indeed the true source of the lakes layer. After verification, I may decide to update this layer.The layer has been generalized spatially, and unneeded attributes have been removed. These changes should improve drawing performance on interactive mapping layers.
Description: This layer is presumed to be from a historic dataset provided by the Minnesota Department of Natural Resources. The layer has since been modified to follow new water courses.This layer is generalized to improve performance
Service Item Id: 5bccf9ce32ce44e0b7d9830d01c03772
Copyright Text: Possibly Minnesota Department of Natural Resources
Lyon County, MN
Color: [0, 0, 0, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Color: [115, 76, 0, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none