Survey Import data does not have to be in an .mdb, .xml, or any other specific format in order to be imported into the InfoAsset Planner database. Survey Import data may come from separate Excel tables, attribute tables, or any other ArcGIS readable format. This page explains how to import this data.
To import other survey data as survey imports, follow the same initial steps as standard or non-standard database import options.
- Create a new survey import dataset and give it an ID and description.
- Now instead of importing from an either standard or non-standard database, double-click on the Tables specified in next step option. Basically what you are doing is skipping the database selection step and opening up InfoAsset Planner to look at a larger range of possible import source data. Instead of only looking to import tables within certain databases, you can import from any tables identified via ArcGIS's explorer.
Notice also there is a third option, 'Existing Survey Import'. Select this option to consolidate existing InfoAsset Planner Survey Import datasets. For example, you may import CCTV data into a separate InfoAsset Planner survey import dataset for each month, Jan. 2018 Surveys, Feb. 2018, Surveys, Mar. 2018 Surveys, etc. You could then create a separate dataset called '2018 Surveys' and import all the other datasets into this one dataset. This one dataset could then be the only dataset run through the CCTV Analysis Wizard instead of running the Wizard on each dataset separately.
- After selecting Tables specified in next step and clicking Next, the three panel import interface will open. In almost all aspects this window is exactly like the import from standard database window; however, there is one important difference. In the middle panels, instead of having a drop-down list of all the different tables within the standard database, there is Browse
- Like the Import Facility Data window, this interface permits users to match up import source data in the middle panel to the InfoAsset Planner expected tables in the left panel and expected fields on the right. When importing with this method, it is an especially good idea to save the field mappings via a .csv file.