![]() The SPRING Work
Environment
On this page we present
how the system and database files, the environment variables, etc..., are
archived.
Memory,
disk and file system
After installing SPRING (see
Installation
and
Configuration of SPRING), a set of directories
is created under the directory where the system was installed. It is needed
at least 100 MB of space in hard disk. /etc
In this directory
the files and auxiliary subdirectories of the system are archived. The files
are:
/etc/pattern
In this subdirectory
we can find the mould files created by the Scarta module. It should have read
and write permission in case other users want to use this directory. /etc/CSV
In
this subdirectory we can find the files needed for the library that handles
TIFF/GEOTIFF files. /etc/chart/symbol
In
this subdirectory we will find the "*.dxf" files related to the
symbols used by "Scarta" - the chart generation module. This
directory has write permission for the user to add any symbol generated by
other applications that export in the DXF format. A symbol generated
by AutoCAD 12.x should be used only by the basic entities of the system
like: line, polyline, circle, etc..., solid fill of any color,
besides fonts like normal and roman. It is very important while
exporting the symbol to a DXF file that the limits command be
used to define the limits around the symbol generated. /etc/templates, /etc/config, /etc/graficos
In
this subdirectory we can find the template files for each Spring chart. /bitmaps
This directory
contains two other subdirectories (/pattern and /hash) with the raster files
(bitmaps) related to the area hatch patterns. /help
This
directory contains all the “*.gif” and “*.htm” files that refer to the help online system of the
modules Impima, Spring and Scarta. /springdb
In this directory
the system demonstration database is kept. The user can use this directory or
any other to keep his databases. /util
This
directory contains the program files used for conversion between data
formats. files
After
the installation of the Windows version the following files/folders will be
found:
arquivos
After
installing the Unix version one must have in his computer the following
files/folders:
CodeBase and Associated DatabasesEvery descriptive attribute of geographic data is kept in a relational database. The structure of the files generated in the DBASE manager is comparable with DBASE 4, that is, ".dbf" for files and ".mdx" for the indexes, what facilitates the integration of tables in such format with the data generated by SPRING. The structure for the other managers is kept by these ones, then, for database generated in ACCESS, the database structure will be stored in ACCESS tables in an ACCESS base named “spring.mdb”. In MySQL database, the tables will be named “*.MYD","*.MYI" e "*.frm", in a database created in MySQL. The same will happen for each manager structure. See next in File Formats how the tables generated by the system are stored. File
Formats in SPRING
Here we present the file formats of the files generated by SPRING. Starting
from the Database files, followed by the files for Project, Information
Layers, and the formats of the files for image data, line, polygon, thematic
image, and numeric grid. align="center" style='TEXT-ALIGN:center'>Files Associated to the Database When creating a database, we define its name and the directory where
it should be created. This directory should exist and have write permissions
for the user, especially when it is a directory that is shared over the
network. A database defines another directory that will be created under the
one defined by the user. All the data created by SPRING in this new database
will be stored under this director. Following we present the files associated to the database
together with their descriptions, remember that in the case of Codebase databases these tables are stored in
the directory itself Database defined by the user: This
table stores every category and classes created for any database. The
structure of this table is: * for Model we have
the following codes: NextIds5
is a table generated from the creation of a
Database. It is a "counter" internal
to SPRING that controls the generation of identifiers for any element
inserted in the database. They
are identifiers of the next item that will be created in the database. Its
structure: This
table and index file contain the projections (cartographic projection and the parameters provided by the user) defined
for the projects present in the database. Its structure is: Table
with the characteristics of the projects in the Database. Its structure is
the repeated for each project: Describes
the existing representations of an infolayer in a Project: Describes
the visual of the data presentation of Spring (IL, Thematic Class, Object): Describes
the definitions of an IL: Table
and index file of anchors, where 000XXX is id of representation in repres table. This table is only created at the moment an object
is associated to a graphic representation in any cadastral or network infolayer. Its
structure is: Table
and index file of the existent geographic objects in all the databases, where 000XXX is object category id. This
table is only created at the moment an object is created
in a Project. Its structure is: Tables
and index files automatically created by the system,
where 000XXX is object category id. These tables are used by
the user to define the alphanumeric attributes of the objects. Its structure
is: Tables with the IL classes visual. Its structure is: 1.
Infoid = identifier of the IL; 2.
tmcode = geoclass code; 3.
tmcounter = counter for the number of points, lines or polygons associated to
each geoclass; 4.
visible = visibility type code. Collections Tables. Its structure is: 1.
catid = identifier of the objects category to which the collection is
applied; 2.
collection = name of the collection; 3.
x1, x2, y1, y2 = bounding box; 4.
expression = expression to which the collection is applied ; 5.
infoid = identifier of the Information Layer. Tables with the images, documents, videos etc associated to the
database. Its structure is: 1.
photoid = identifier of the datum; 2.
photo = file location; 3.
type = file type. Tables with the metadata. Its structure is:
1.
id = identifier of the metadata; 2.
repid = identifier of the
representation; 3.
nometab = name of the Category
Table; 4.
nome = name of the metadata; 5.
autor = name of the author; 6.
fonte = origin; 7.
qualidade
= data quality; 8.
descrição = data description; 9.
date
, time = date and time of
the creation.
When creating a project a
subdirectory is created under the directory where the database resides. Many
files can be part of a project, and all of them will have a numeric code
representing the IL as a part of its name. Depending on its category an IL
can have many code representations, for example: i000011.spg and v000011.lin
are files belonging to the same IL. In SPRING the infolayers
of the thematic, numeric and image model types are internally stored and
processed by the system in files of specific structure. Each infolayer will
have its corresponding files: a thematic model will have a lines file, a
polygons file, a nodes file, and a thematic map; a layer of the image model
will have the data stored in a data file (spg), decriptor (dsc) and a lut file; layer of the numeric
model will have its data stored in a lines files (contour lines and points)
and spg files (grids); layer of cadastral model will have lines, polygons, nodes and anchors files; and layers
of network model will be lines, nodes and anchors files. All model will be text
file. Following you will find a
generic description of each of these data files. For Lines:
file name contain lines (V000000.lin, V000000.blk, V000000.rtl) .
Files *.blk contain the blocks with points that make the lines. These
blocks have maximum size of 32 points. Lines of only 2 points have no blocks,
and the points of this line stored in the header row (initial point and end
point) .
Files *.p3d
contain point information of plans for the category numerical
information. It contains the following information for each item:
Files *.kdt contain the structure of the tree Index (kdtree) of the
points.
Files *.po2 contain the following:
Files *.rtp contain the structure of the tree Index (rtree) of polygons.
For Anchors: filenames that contain the anchors (V000000.an1, V000000.an2, V000000.rta):
Files *.an1 contain the anchors headers, contain the following for each
anchor:
Files *.an2 contain the following:
Files *.rta contain the structure of the tree Index (rtree) of anchors.
For Text: filenames that contain the text (E000000.itx, E000000.txt, E000000.kde);
Files *.itx contain text identifier.
Files *.txt contain the following:
Files *.kde
contain
the structure of the tree Index (rtree) of text. For Thematic Images: filenames contain the image (IT000000.spg, IT000000.dsc,IT000000.lut).
For Grid: filenames that contain the grid (G000000.spg, G000000.dsc, G000000.lut).
For Classified Image: filenames that contain the image (I000000.spg, I000000.dsc,I000000.thm).
For Labeled Image: filenames that cotain the image (I000000.spg, I000000.dsc,I000000.reg).
For Synthetic Image: filenames
that contain the image (I000000.spg, I000000.dsc,I000000.lut).
For Image: filenames that contain the
image (I000000.spg, I000000.dsc).
Files *.lut contain the index with the values in RGB of synthetic and
classified images or the slice of values for viewing the grid as an image..
Files *.thm contain themes (code, RGB values and name) of classified
image.
Files *.reg contain the labeled image
segments.
Files *.spg are files in the format of values as a grid expressed in
binary mode.
Files *.dsc are text files with the description of the data represented
in the spg, the information contained in this file are variable, depending on
the kind of image processing and applied to it. It is essencial to include:
SPRING is the evolution
of the SITIM and SGI systems, developed for
microcomputers that represent the greatest installed based for geoprocessing
systems in The Interactive Image
Treatment System - SITIM - is a system for image processing. The Geographic
Information System - SGI - is a geographic database to process spatially
coded information and extract information from remote sensing data, field
survey, etc... This version of SPRING
also imports and exports thematic and numeric data to the ASCII, ARC-INFO,
SGI, SHAPEFILE, SURFER, IDRISI, DXF and DWG formats, as well as images to the
TIFF, GeoTIFF, RAW, GRIB, JPEG and SITIM formats. Text can also be imported
and exported in ASCII, DXF and DWG format. 1) To define where SPRING
is installed (required). 2) To define where the
file "database.dbf" will be created and kept (required). 3) To define the format
of the communication with the digitizing table (required only when you want
to use one). Possible values = MicroGridCounts, MicroGridHigh Resolution, GTCO-Low, GTCO-High GTCO-MULTICAD
Calcomp3, SUMMASKETCH-Low, SUMMASKETCH-High. See about the configuration of tables in the
installation and configuration manual. 4) To define the number
of data bits in the serial communications with the digitizing table. Possible
values = 7 or 8 (required when
using a digitizing table). 5) To define the parity
of the communication with the digitizing table. Possible values = even, odd,
or none (required when using a digitizing
table). 6) To define the number
of stop bits in the communication with the digitizing table. Possible values
= 1 or 2 (required when using a
digitizing table). 7) To define the port
where the table is connected. Possible values: "/dev/ttya",
"/dev/cua1", "COM1", "COM2", etc... for UNIX (required when using a digitizing
table). 8) To define the default
database (optional). 9) To define the default
project of the database defined above (optional). 11) To define the CD-ROM
reading device (valid only for the IMPIMA module - required when reading
images from a CD-ROM). 12) To define the SPRING visualization
version, Classic or Non-Classic. "HKEY_CURRENT_USER\Software\INPE/DPI\SPRING50\Settings". In Linux, a Configuration
File "~/.config/INPE-DPI/SPRING50.conf", which is managed by the Qt
library, is created for each user. NOTE: For
the modifications to take effect, in the case of some options, it is
necessary to close and run the SPRING module again. |