1) How is GeoConnector Licensed?

2) What are the system requirements for GeoConnector?

3) Do I need ESRI's ArcGIS software to run GeoConnector?

5) What spatial data formats does GeoConnector read?

6) What spatial data formats does GeoConnector write?

7) What tabular data formats does GeoConnector read?

8) What tabular data formats does GeoConnector write?

9) GeoConnector 2.X worked fine with ArcSDE 8.3, but when I upgraded to ArcSDE 9, GeoConnector stopped working. Why?

10) What type of data operations can GeoConnector perform?

11) Why do some data input / output types take longer to process than others?

12) Can GeoConnector export subsets of my data?

13) How flexible are the scheduling options?

14) How can I schedule multiple sessions and be sure that the first session executed successfully before the next session starts?

15) If I'm not logged in, or different user is logged in, my scheduled sessions don't run. Why not?

16) I'm having trouble getting scheduled sessions to run in Windows XP. What's wrong?

How is GeoConnector Licensed?

Each individual machine running GeoConnector will require its own license file. After installation, the first time you GeoConnector, you will be prompted with a dialog informing you that there is no license file, and you will be provided with your machine name and Windows OEM number. You then email these two pieces of information to geoc@infogeographics.com. IGI staff will use this information to generate a GeoConnector license file unique to that machine, and send it to you via email. Once the license file is received, GeoConnector will be fully functional.

What are the system requirements for GeoConnector?

GeoConnector runs on WinNT, Win2K & Win2K Server, & WinXP. GeoConnector has not been tested on Windows 2003 Server, however, we are not aware of any specific issues that would prevent GeoConnector from running on a Win2K3 Server machine.

Do I need ESRI's ArcGIS software to run GeoConnector?

No, GeoConnector is a stand alone application and does not require ArcGIS for the vast majority of its functionality. The only time your machine will need ArcGIS is if you wish to have GeoConnector read or write the Personal Geodatabase format.

How do I obtain technical support for GeoConnector?

Technical support for GeoConnector can be obtained via email or telephone. To receive technical support via email, send requests to geoc@infogeographics.com. To receive technical support via telephone, dial (231) 995-8266. Before making a support request, please review the GeoConnector Help File, and the GeoConnector Tutorial provided with your installation.

What spatial data formats does GeoConnector read?

GeoConnector reads most major ESRI vector formats, including Shapefile, Coverage, & ArcSDE layers. Personal Geodatabase format is supported only on machines already running a licensed installation of ArcGIS.

What spatial data formats does GeoConnector write?

GeoConnector writes spatial data to Shapefile format. Additionally, on machines running a licensed version of ArcGIS, GeoConnector can write Personal Geodatabase feature classes.

What tabular data formats does GeoConnector read?

GeoConnector can connect directly to MS Access databases, Excel files, dBase files, Delimited Text files, and XML Files. GeoConnector can also connect to most popular ODBC data sources. In conjunction with the Equalizer Assessing Module, GeoConnector is also capable of connecting directly to BS&A's Equalizer Assessing System databases.

What tabular data formats does GeoConnector write?

GeoConnector can write output into SQL Server & Oracle ODBC connections, MS Access databases, Excel files, dBase files, Delimited Text files, and XML files.

GeoConnector 2.X worked fine with ArcSDE 8.3, but when I upgraded to ArcSDE 9, GeoConnector stopped working. Why?

GeoConnector utilizes ESRI's MapObejcts components for accessing ArcSDE. By default, the GeoConnector installation installs MapObjects v2.2, which is capable of accessing ArcSDE 8.3 and previous versions.

In order to access an ArcSDE 9.0 database, you will need to install MapObjects 2.3, which is provided for you in the "Support" directory of your GeoConnector installation media. Once installed, GeoConnector 2.X will be able to access ArcSDE 9.0 databases.

What type of data operations can GeoConnector perform?

GeoConnector can perform a number of data operations, depending on the data source types (spatial or tabular). The following matrix details the specifics of various data source types, data operations, and data output types.

Why do some data input / output types take longer to process than others?

GeoConnector uses an SQL database engine to perform most data operations. Certain input types (example XML, Equalizer Databases) are not SQL compatible and need to be imported to an SQL compatible format before processing can begin. Likewise, certain output formats cannot be mass-exported using SQL statements or ISAM drivers, and therefore will take longer to write.

Can GeoConnector export subsets of my data?

Yes. GeoConnector gives you the ability to apply attribute filters to your data sources. Only those records that satisfy the filter criteria will be included in the output dataset.

How flexible are the scheduling options?

The scheduling functionality is very flexible. GeoConnector integrates with the Windows Task Scheduler system components, and allows the vast majority of its scheduling options.

How can I schedule multiple sessions and be sure that the first session executed successfully before the next session starts?

GeoConnector provides a "session batch" functionality. With this method you specify multiple session files (*.goc) in the order you would like them to execute. This information is stored in session batch file (*.gbt). Then, instead of scheduling each file individually, you simply schedule the session batch. The session batch fires the individual sessions iteratively, ensuring that each session is successfully processed before the next session is executed. Should a session not execute successfully, all subsequent sessions are cancelled. This is very important in instances where the output of the first session is used as a data source for the second session.

If I'm not logged in, or different user is logged in, my scheduled sessions don't run. Why not?

If you want scheduled GeoConnector sessions to execute when you are not logged in, you should specify a user account that has administrative privileges when providing the "Run As" information on the GeoConnector scheduling dialog. Using an administrative account will ensure that the scheduled session executes regardless of who is logged in, or even if no one is logged in at all.

I'm having trouble getting scheduled sessions to run in Windows XP. What's wrong?

Make sure you are specifying a user account that has a password defined when providing the "Run As" information on the GeoConnector scheduling dialog. Windows XP does not require user accounts to be password protected, however, the Windows Task Scheduler component does require that a password protected account be used when scheduling a task.