In addition to the general requirements defined above, we provide the following functionality at no additional cost. Implementing this functionality reduces the time and effort required to maintain the site over time and to make changes to what information get shown on the sites. Additional Requirements Functionality Comment This allows certain users to flag in the database which layers of data are valid for identification, searching, etc. Database-driven control of GIS Layers This avoids post-deployment development costs by building in this flexibility. This gives the ability to control, by users, which fields of information come back to the interface. This also allows control of which fields are exposed for a “Short Report” Database-driven control over fields of and “Detailed Report.” Field aliases can be defined to information make the site more user friendly. This can be done dynamically without having to turn the site off. Many browsers now come installed with popup No Pop-ups blockers. This creates a great deal of overhead on many sites and renders many GIS sites useless. Frames are strongly recommended against, and being No frames discouraged, by the Worldwide Web Consortium (W3C). A technique that allows direct digitization on the screen without multiple trips to the server. This greatly reduces Single trip to server for polygon, line etc digitization server load and enhances the and user’s experience overall usability. The ability to zoom the user to a fixed scale (e.g., Zoom to scale 1:24000) This increases performance and scalability as each user’s maps and other info are stored on the client as No Session Variables opposed to the server. For 200 users, each storing 512Kb of information in Sessions (200 * 512 = 102400 Kb) this equates to = 102.4 MB of server memory. 5.2 Data Layers It is anticipated that the GIS Internet Map Site will have approximately 20 base data layers. Examples of these layers are:
In addition to the general requirements defined above, we provide the following functionality at no additional cost. Implementing this functionality reduces the time and effort required to maintain the site over time and to make changes to what information get shown on the sites. Additional Requirements Functionality Comment Database-driven control of GIS Layers This allows certain users to flag in the database which layers of data are valid for identification, searching, etc. This avoids post-deployment development costs by building in this flexibility. Database-driven control over fields of information This gives the ability to control, by users, which fields of information come back to the interface. This also allows control of which fields are exposed for a “Short Report” and “Detailed Report.” Field aliases can be defined to make the site more user friendly. This can be done dynamically without having to turn the site off. No Pop-ups Many browsers now come installed with popup blockers. This creates a great deal of overhead on many sites and renders many GIS sites useless. No frames Frames are strongly recommended against, and being discouraged, by the Worldwide Web Consortium (W3C). Single trip to server for polygon, line etc digitization A technique that allows direct digitization on the screen without multiple trips to the server. This greatly reduces server load and enhances the user’s experience and overall usability. Zoom to scale The ability to zoom the user to a fixed scale (e.g., 1:24000) No Session Variables This increases performance and scalability as each user’s maps and other info are stored on the client as opposed to the server. For 200 users, each storing 512Kb of information in Sessions (200 * 512 = 102400 Kb) this equates to = 102.4 MB of server memory. 5.2 Data Layers It is anticipated that the GIS Internet Map Site will have approximately 20 base data layers. Examples of these layers are:
4b_InventorySRSandDDSDocumnets.docx