Geography Reference
In-Depth Information
When all your
Active
column entries switch to
Finished
, you should have a database
loaded with the county polygons; you are now ready to start experimenting.
If any of the steps turn red and display
Stopped
, you have a problem. The details and stack
trace of the problem will be shown in the
Logging
and
Execution History
tabs.
Unfortunately, as much as I'd like to be able to list every possible issue you'll see here, I
simply can't. When GeoKettle fails, it only releases a stack trace and refuses to do anything
further. This probably isn't an issue for the average developer, but for a non-technical user it
can look very scary indeed.
My experience with transformation problems is that they're usually some kind of data format
issue; for instance, an incorrect setting in the transform step of the destination server spitting
out its default data because it doesn't like something about the SQL GeoKettle has just sent
to it.
Whenever I receive a stop condition, I copy and paste the output from the
Logging
pane
into a text editor so I can start examining SQL statements and diagnosing the stack trace in
an easier-to-read window.
Once all of the transformation steps finish successfully, you can close GeoKettle and return
to Quantum GIS. Using the connection you created when loading data with SPIT, you can
view the data you now have in your database.
Previewing the Data
If we open Quantum GIS and start a new project, the first thing we need to do is set the
project properties. We do this by navigating to
Settings
>
Project Properties
in the toolbar.
Figure 41: Opening Project Properties in Quantum GIS
