101 |
The tool bar provides quick access to the commonly needed tools. |
The tool bar provides quick access to the commonly needed tools. |
102 |
By hovering over each button the user can see a short messages |
By hovering over each button the user can see a short messages |
103 |
describing what the tool does. The tools provided are Zoom In, Zoom |
describing what the tool does. The tools provided are Zoom In, Zoom |
104 |
Out, Pan, Full Extent, Full Layer Extent, Full Shape Extent, Indentify, |
Out, Pan, Full Extent, Full Layer Extent, Full Shape Extent, Identify, |
105 |
and Label. Each of the tools will be explained in further detail later |
and Label. Each of the tools will be explained in further detail later |
106 |
in the manual. |
in the manual. |
107 |
</para> |
</para> |
149 |
<guimenu>File</guimenu> |
<guimenu>File</guimenu> |
150 |
<guimenuitem>Save Session</guimenuitem> |
<guimenuitem>Save Session</guimenuitem> |
151 |
</menuchoice>. A dialog box will open allowing the user to browse |
</menuchoice>. A dialog box will open allowing the user to browse |
152 |
the filesystem and select a place to save the session. Thuban |
the file system and select a place to save the session. Thuban |
153 |
sessions should be saved under a name ending in |
sessions should be saved under a name ending in |
154 |
<varname>.thuban</varname>. If the file already exists the user |
<varname>.thuban</varname>. If the file already exists the user |
155 |
will be prompted to save under a different name or overwrite the |
will be prompted to save under a different name or overwrite the |
214 |
standard file format for storing geographic objects. These |
standard file format for storing geographic objects. These |
215 |
files have the extension ``.shp''. Associated with |
files have the extension ``.shp''. Associated with |
216 |
the shape file is a database file which stores attributes for |
the shape file is a database file which stores attributes for |
217 |
each shape in the shape file. This file, in dBASE format, |
each shape in the shape file. This file, in dBase format, |
218 |
has the extension ``.dbf''. Both files must have the same base name. |
has the extension ``.dbf''. Both files must have the same base name. |
219 |
For example, if there is a shape file named roads.shp there must |
For example, if there is a shape file named roads.shp there must |
220 |
also be a file roads.dbf. |
also be a file roads.dbf. |
357 |
</para> |
</para> |
358 |
</section> |
</section> |
359 |
|
|
360 |
<section><title>Object Labelling</title> |
<section><title>Object Labeling</title> |
361 |
<para> |
<para> |
362 |
Objects can be labelled using the Label tool |
Objects can be labeled using the Label tool |
363 |
<inlinemediaobject> |
<inlinemediaobject> |
364 |
<imageobject> |
<imageobject> |
365 |
<imagedata fileref="../images/3_3_label.png" format="PNG" scale="&imgscale;"/> |
<imagedata fileref="../images/3_3_label.png" format="PNG" scale="&imgscale;"/> |
537 |
image layers. Shape layers consist of vector based shapes with |
image layers. Shape layers consist of vector based shapes with |
538 |
geo-referenced coordinates. There are three types of supported |
geo-referenced coordinates. There are three types of supported |
539 |
shapes: polygons, lines, and points. Image layers can be any image |
shapes: polygons, lines, and points. Image layers can be any image |
540 |
file format supported by the Geospatial Data Abstraction Library |
file format supported by the Geo-spatial Data Abstraction Library |
541 |
(GDAL). The images must have geographic |
(GDAL). The images must have geographic |
542 |
coordinate data either embedded within the file or in a seperate |
coordinate data either embedded within the file or in a separate |
543 |
file that is in the same directory as the image file. GeoTIFF files |
file that is in the same directory as the image file. GeoTIFF files |
544 |
work very well with Thuban and were designed specifically to be image |
work very well with Thuban and were designed specifically to be image |
545 |
layers in GIS programs. |
layers in GIS programs. |
687 |
</para> |
</para> |
688 |
<section><title>Visible</title> |
<section><title>Visible</title> |
689 |
<para> |
<para> |
690 |
The Visible column has checkboxes that determine whether a |
The Visible column has check-boxes that determine whether a |
691 |
classification group will be displayed in the legend. This is |
classification group will be displayed in the legend. This is |
692 |
useful if the user knows that the groups completely cover |
useful if the user knows that the groups completely cover |
693 |
the data set and don't want the DEFAULT group to be displayed |
the data set and don't want the DEFAULT group to be displayed |
719 |
If the type is Integer, then any valid integer may be entered. In |
If the type is Integer, then any valid integer may be entered. In |
720 |
addition, with special syntax, a range of values can be entered. |
addition, with special syntax, a range of values can be entered. |
721 |
A range from <varname>start</varname> to <varname>end</varname> |
A range from <varname>start</varname> to <varname>end</varname> |
722 |
inclusive is specifed like this: <literal>[start;end]</literal>. |
inclusive is specified like this: <literal>[start;end]</literal>. |
723 |
The exclusive range is specified like this: |
The exclusive range is specified like this: |
724 |
<literal>]start;end[</literal>. Ranges can include infinity like |
<literal>]start;end[</literal>. Ranges can include infinity like |
725 |
this: <literal>[-oo;oo]</literal>. Field types can also be of type |
this: <literal>[-oo;oo]</literal>. Field types can also be of type |
754 |
classification at once while still giving the user control over |
classification at once while still giving the user control over |
755 |
how it appears. Clicking <guibutton>Generate Class</guibutton> |
how it appears. Clicking <guibutton>Generate Class</guibutton> |
756 |
opens the <varname>Generate Classification</varname> dialog. |
opens the <varname>Generate Classification</varname> dialog. |
757 |
Under the <varname>Generate</varname> pulldown there are at most |
Under the <varname>Generate</varname> pull down there are at most |
758 |
three different ways to generate classifications: |
three different ways to generate classifications: |
759 |
Unique Values, Unique Distribution, and Quantiles. Some options |
Unique Values, Unique Distribution, and Quantiles. Some options |
760 |
may not be available if the data type for the field does not |
may not be available if the data type for the field does not |
852 |
list of available projections as a new entry, and thus makes it |
list of available projections as a new entry, and thus makes it |
853 |
available to future Thuban sessions. Clicking <guibutton>New</guibutton> |
available to future Thuban sessions. Clicking <guibutton>New</guibutton> |
854 |
will create an entirely new, empty projection. The |
will create an entirely new, empty projection. The |
855 |
<guibutton>Remove</guibutton> button will permanantly remove a |
<guibutton>Remove</guibutton> button will permanently remove a |
856 |
projection from the list of available projections. |
projection from the list of available projections. |
857 |
</para> |
</para> |
858 |
</section> |
</section> |
908 |
identifier. Thus you can perform analysis like selecting all |
identifier. Thus you can perform analysis like selecting all |
909 |
records where "population > 10000" or |
records where "population > 10000" or |
910 |
"cars_per_inhabitant < bikes_per_inhabitant" (note that the field names |
"cars_per_inhabitant < bikes_per_inhabitant" (note that the field names |
911 |
are only explanatory, the dBASE files allow only |
are only explanatory, the dBase files allow only |
912 |
11 character field names). |
11 character field names). |
913 |
|
|
914 |
Selections can be combined either by applying a selection only on |
Selections can be combined either by applying a selection only on |
921 |
with highlighted selection results. Columns and rows can be resized. |
with highlighted selection results. Columns and rows can be resized. |
922 |
</para> |
</para> |
923 |
<para> |
<para> |
924 |
The contents of a table can be exported into a file, either dBASE |
The contents of a table can be exported into a file, either dBase |
925 |
format (DBF) or comma seperated values (CSV). The |
format (DBF) or comma separated values (CSV). The |
926 |
<guibutton>Export</guibutton> button |
<guibutton>Export</guibutton> button |
927 |
raises a file dialog to specify a path and file name, the export type |
raises a file dialog to specify a path and file name, the export type |
928 |
is determined by the file extension (either .dbf or .csv). |
is determined by the file extension (either .dbf or .csv). |
957 |
<guimenuitem>Open</guimenuitem> |
<guimenuitem>Open</guimenuitem> |
958 |
</menuchoice> |
</menuchoice> |
959 |
item raises a file dialog to let you select a |
item raises a file dialog to let you select a |
960 |
dBASE file from the file system to be loaded into Thuban read-only. |
dBase file from the file system to be loaded into Thuban read-only. |
961 |
On <guibutton>OK</guibutton> the selected file is loaded and a |
On <guibutton>OK</guibutton> the selected file is loaded and a |
962 |
table view is opened. |
table view is opened. |
963 |
</para> |
</para> |
1084 |
normal tables can be simply closed (and thereby dereferencing |
normal tables can be simply closed (and thereby dereferencing |
1085 |
the source tables), this is not possible for attribute tables. |
the source tables), this is not possible for attribute tables. |
1086 |
|
|
1087 |
Hence joins on attribute tables must be solved explicitely. This is |
Hence joins on attribute tables must be solved explicitly. This is |
1088 |
what the |
what the |
1089 |
<menuchoice> |
<menuchoice> |
1090 |
<guimenu>Layer</guimenu> |
<guimenu>Layer</guimenu> |
1166 |
</varlistentry> |
</varlistentry> |
1167 |
|
|
1168 |
<varlistentry> |
<varlistentry> |
1169 |
<term>dBASE file</term> |
<term>dBase file</term> |
1170 |
<listitem> |
<listitem> |
1171 |
<para> |
<para> |
1172 |
dBASE files are used to store the attributes for each layer. This |
dBase files are used to store the attributes for each layer. This |
1173 |
is closely associated with the Shapefile format. For detailed |
is closely associated with the Shapefile format. For detailed |
1174 |
specifications on the correct format of a dBASE file used with |
specifications on the correct format of a dBase file used with |
1175 |
Thuban please see the Technical Specification for the Shapefile |
Thuban please see the Technical Specification for the Shapefile |
1176 |
format above. |
format above. |
1177 |
</para> |
</para> |
1209 |
</appendix> |
</appendix> |
1210 |
|
|
1211 |
</book> |
</book> |
1212 |
|
|