GIS Data Model (Geodatabase) Development Services
SGS can design and build a GIS data model (geodatabase) to suit any project GIS needs. Geodatabase design should be tailored specifically to the informational needs of the client. SGS will sit down with you to figure exactly what is to be mapped, how we can best incorporate these elements as features in a geodatabase, what aspects of each feature require information to be collected (feature attributes), and what data will populate the attribute data fields for each feature. Smart geodatabase design principles should be implemented so as to allow for limited data entry errors, such as the use of drop down menu's for data entry where possible (feature attribute domains). Geodatabase design is scalable and can range from simple to complex based on your needs. SGS can also modify any existing ESRI template geodatabase if preferred by the client.
SGS can design a geodatabase to suit the conversion of data that does not currently exist in a spatial context into a GIS, such as the incorporation of Excel, Access, or other database tables stored with address information or XY coordinate information into a GIS. If your interest is to continue to use these non spatial database tables as they exist for data entry, simple XY point features (or polygon features) can be created based on the address or XY coordinate information that contain a unique identifier that relates the GIS point feature to records in the non spatial database. Alternatively, SGS can design a geodatabase that will function to replace your existing data entry protocol. Any of the above allow you to visualize and examine information from a non spatial database table in a geographic context. Examples could include tables containing time series data related to XY coordinates for gas wells or rain gauges or any other information as tied to a physical location.
If GPS field mapping or infrastructure inventorying is a part of your GIS project plan, geodatabase construction can be paired with a customized GPS field data collection protocol (see Utility infrastructure GPS/GIS inventory mapping and consulting services). A common problem for inexperienced GIS/GPS users who implement an infrastructure inventorying project without sufficient planning is that they end up with a variety of data export files from the GPS that have differing data formats. If you do not have a geodatabase and you collect GPS data and store export data as individual files rather than in a central database it can quickly become a confusing scenario. This can be avoided with a well designed mapping protocol and properly constructed geodatabase that can manage what type of data are collected and stored. The geodatabase itself should of course be scaleable in that you will decide that you want to add feature types or change the information you are collecting, and if the geodatabase has been constructed correctly these edits will be easy to manage.
