My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 2011/11/14
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
2010-2019
>
2011
>
Agenda Packets - 2011/11/14
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:51:08 PM
Creation date
6/27/2018 1:48:39 PM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
11/14/2011
Supplemental fields
City Council Document Type
City Council Packets
Date
11/14/2011
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
159
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Section 3. New Members will pay the current one-time membership fee and the data exchange fee due for the year <br />in which the new Member is joining, as set by the Board pursuant to Article IV, Section 3, as calculated by the <br />current formula. Fees will not be pro-rated for new Members who join after January 1 of each year. <br /> <br />ARTICLE VI. GIS DATA TO BE SUPPLIED BY RAMSEY COUNTY <br />Section 1. It is the intent of this Agreement that the Users Group will negotiate an agreement with Ramsey County <br />for the exchange of County GIS Data with Members at a preferential fee structure. A component of the fees will <br />apply to the collection of aerial photography and maintenance of digital physical features derived from aerial <br />photography. <br />Section 2. The GIS Data should consist of the following components generated and maintained by the County: <br />(i) The Ramsey County Digital Base Map; <br />(ii) The Ramsey County Attribute Data Base; <br />(iii) The Physical Features File. <br />Section 3. The Board will negotiate on behalf of the Members for the cost and method of access to this data. Prior to <br />each payment to Ramsey County, the Board shall determine whether it is satisfied with the content, accuracy, and <br />timeliness of the data provided to date and make a determination if further payment shall be made. <br /> <br />ARTICLE VII. GIS DATA TO BE EXCHANGED AS PART OF THIS AGREEMENT <br />Section 1. Members agree to exchange any GIS data with Ramsey County and with any requesting Member for the <br />requesting party’s own use where that GIS data has been in some way derived and/or developed from the County <br />GIS Data accessed through this Agreement or future agreements between the Users Group and Ramsey County. <br />Members agree to exchange with Ramsey County and with any other Member any attribute data that it has created <br />and maintained where that data can be associated to a parcel using a parcel identifier. Members also agree to <br />exchange any building permit data requested by Ramsey County for the identification of future physical feature data <br />base updates. <br />Section 2. The Board will negotiate with Ramsey County on behalf of the Members in all matters deemed necessary <br />relating to supply of GIS data generated by a Member. <br />Section 3. Any costs associated with a Member supplying data to Ramsey County or to any other Member shall be for <br />access and delivery of that data only and not for any costs associated with the development of that data. <br /> <br />ARTICLE VIII. DATA ACCESS AND USAGE <br />Section 1. All Members shall have equal rights to access Ramsey County GIS Data. <br />Section 2. Data generated by Ramsey County and provided to Members may not be sold in its original form to third <br />party agencies. However, a Member may allow use of the original data by a third party for specific contracted <br />purposes. <br />Section 3. Data which results from enhancement of Ramsey County GIS Data by a Member, received pursuant to this <br />Agreement, may be sold or exchanged to a third party.
The URL can be used to link to this page
Your browser does not support the video tag.