Data Export
SPRING exports the
following entities, in the formats:
-
Vectors : ARCINFO (ungenerate), ASCII-SPRING, ShapeFile, E00 and DXF/DWG (any version).
-
Numeric Grids : ARCINFO (ungenerate), ASCII-SPRING, and SURFER
-
Thematic Matrix : ARCINFO (ungenerate), ASCII-SPRING, TIFF/GEOTIFF and RAW
(binary)
-
Images : TIFF/GEOTIFF/BIGTIFF, RAW (binary), JPEG2000
and ASCII-SPRING (GRID REG)
-
Tables
:
SPACESTAT, ASCII-SPRING ou CSV
The exportation to any of
these formats requires an active Project
and an infolayer with data or a table.
To facilitate the
description of the procedures we divide the export into:
NOTE:
See the explanation table about the export and import of ASCII-SPRING data.
See
about the import/export formats of SPRING
See also:
Database
Definition
Data
Model Definition
How
to Import SGI data ?
How
to Import GRIB images ?
How
to Import data ?
How
to Export to the SpringWEB
?
How
to
Export
to
the
TerraLib
?
Exportation of Thematic
Maps, Networks and Cadastral
Exporting data
to ASCII, DXF/DWG , SHAPEFILE, ARCINFO-UNG, or E00:
-
activate in the "Control Panel" the Infolayer (of categories Thematic, Numeric, Cadastral or
Network) that contains the data for
exportation;
-
click on File
- Export... . The window "Export"
will be presented;
o
click on Format:
and choose among ASCII-SPRING, ARCINFO-UNG , DXF-R12, SHAPEFILE, E00 or DXF/DWG.
The option TIFF/GeoTIFF
andRAW are used for the IL's.
-
if the format is ASCII-SPRING click on
Separator: and
choose among (;), (,) or (None);
-
click on
Coord.: and
choose among Planes(meters), Geographic(GMS) =
degrees/minutes/seconds only for ASCII-SPRING, Geographic(degrees)=decimal
degrees or Geographic(seconds)=decimal seconds;
-
click on Selected
Classes to export
only the desired classes. Then click on Select... in the Control Panel to make the selection of the Data and of the desired classes
(visualized).
-
click on Entity: and
choose among:
-
Lines and Labels - for thematic,
cadastral, or network ILs in the formats
ASCII-SPRING, ARCINFO-UNG, DXF-R12 or DXF/DWG;
-
Polyg. and Labels - for thematic, and
cadastral ILs in the formats ASCII-SPRING,
ARCINFO-UNG, DXF-R12, SHAPEFILE or DXF/DWG - the polygons will be exported as
islands generating a duplication of lines at the limits between them;
-
Points - for thematic, or
cadastral ILs in the formats
ASCII-SPRING, ARCINFO-UNG, DXF-R12, SHAPEFILE or DXF/DWG;
-
Texts - for every data
model in the formats ASCII-SPRING, DXF-R12 or DXF/DWG;
-
All - for thematic,
cadastral, or network ILs in the
format ASCII-SPRING (the sections
lines/identifiers/points/text will be in the same file + attribute
table);
-
Lines and Labels Auto -
for thematic, cadastral, or network ILs in
the ASCII-SPRING format - creates files of lines (types LINES and
POINTS) and points (POINT2D), where in the identification section we
have the label and classes of the objects sequentially enumerated. It
is a very easy way of identifying the entities in your map by importing
these files;
-
Spatial Lag. Matrix - for thematic,
cadastral, or network ILs in the
ASCII-SPRING format (the sections
lines/identifiers/points/text will be in the same file + attribute
table);
-
Polyg. without Label - for thematic, or
cadastral ILs in the ASCII-SPRING format (a
file of 2D points is generated - to visualize it should be imported as
a Point entity);
-
Reg. Grid - (Regular Grid) only for
thematic or cadastral ILs in the ASCII-SPRING
or ARCINFO-UNG formats - for ASCII-SPRING the legend with the classes
is also exported;
-
click
on
Save
...
-
in the window
"SPRING of Files" inform the
destination directory, type in the name of the file and click on
Save;
IMPORTANT: By convention ILs are exported in the ASCII-SPRING format, using some
suffixes added to the name of the ILs. The table in
the end of the page shows such extensions for each exported entity, which entity should be
selected for import and some observations.
Exportation of numeric
maps
Exporting data
to ASCII-SPRING, DXF/DWG , SHAPEFILE, ARCINFO-UNG
, E00 or
Surfer formats:
-
activate in the "Control Panel" the Infolayer of the category Numeric that
contains the data for exportation;
-
clickon File
- Export... . The
"Export" window will be presented;
-
click on Format: and choose among ASCII-SPRING, ARCINFO-UNG , DXF/DWG, SHAPEFILE or
E00. The option TIFF/GeoTIFF
orRAW orSurfer are
used for IL's that have a rectangular DTM model;
-
if the format is ASCII-SPRING
click on Separator:
and choose among (;), (,) or (None);
-
click on
Coord: and choose
among Planes(meters), Geographic(GMS) - degrees-/minutes/seconds only
for ASCII-SPRING, Geographic(degrees) - decimal degrees or Geographic(seconds) - decimal seconds ;
-
click on Entity: and
choose among:
-
Samples - in the formats
ASCII-SPRING, ARCINFO-UNG, DXF-R12, SHAPEFILE, E00 or DXF/DWG ;
-
Reg. grid - in the formats
ASCII-SPRING, ARCINFO-UNG, TIFF/GeoTIFF, Raw
or Surfer;
-
Contour Lines - in the formats
ASCII-SPRING, ARCINFO-UNG, DXF-R12, SHAPEFILE, E00 or DXF/DWG;
-
Texts - in the formats
ASCII-SPRING, DXF-R12 or DXF/DWG;
-
TIN - in the format
ASCII-SPRING, DXF-R12 or DXF/DWG
-
TIN 3D - in the formats
ASCII-SPRING, DXF-R12 or DXF/DWG
-
All - in the format
ASCII-SPRING (the sections lines/identifiers/points/text are in the
same file + attribute table);
-
click
on
Save
...
-
in
the window "SPRING of Files" inform the destination
directory, type in the file name and click on the button Save.
IMPORTANT :
By convention when IL's are exported to the ASCII-SPRING format, some
suffixes are added to the IL's name. The table at the end of the page shows such extensions for every
exported entity, which entity should be selected for importing and some
observations.

Images Exportation
SPRING exports IL's of
the image model to the formats TIFF (if the project has no projection) or GeoTIFF (if the project has a projection), be it an image in gray levels, synthetic, classified or
RGB (each IL in one channel). Monochromatic images can be exported to the RAW
(binary) format.
Images can be exported to
the formats ASCII-SPRING as a regular grid. Images can be exported in JPEG2000 format (containing or not project projection).
Exporting TIFF/GeoTiff/BIGTIFF, RAW
, ASCII-SPRING (GRIDREG) or JPEG2000 images
-
activate
in the "Control Panel" the Infolayer of the category Image
that contains the data for exportation;
-
click
on
File - Export... . The window "Export"
will be presented;
-
click
on Format: and choose among TIFF/GeoTiff, RAW
, ASCII-SPRING or JPEG2000. The option RAW is only available for
gray level images, i.e., monochromatic;
-
depending on the active IL one can choose:
-
Monochromatic
- for gray level,
synthetic or classified images. Click on the Infolayer name in the
list.
-
RGB
- only if the active IL is
monochromatic. In this case, every IL with the same size and resolution
will be presented;
-
click on
R
and then on an IL in the list
-
click on
G
and then on an IL in the list
-
click on
B
and then on an IL in the list
-
click
on
Save
...
-
in
the
"SPRING of Files"
window inform the destination
directory, type the name of the file and click on the button Save...;
NOTE : Tiff or GeoTiff images can be exported in Bigtiff format even if the data does not exceed
4 Gigabytes, by clicking the BigTiff button next to the options. If the data exceeds 4 Gigabytes,
it will be exported in Bigtiff format.

Exportation of Object Tables
and Non-Spatial Tables
The object tables and
non-spatial tables are associated to IL's of the cadastral or network models.
So it suffices to have an IL of one of these models to allow for the
exportation of tables.
The tables can be
exported in the ASCII-SPRING, SPACESTAT ou CSV formats can be exported. If the
exportation of tables of other formats is desired use your own database
management system.
Exporting
tables
:
-
activate in the "Control Panel" the Infolayer of cadastral or network categories that
contain the associated table;
-
click on File
- Export... . The "Export"
window will be presented;
-
click on Format: and
choose between ASCII-SPRING, SPACESTAT or CSV
-
click on Entity: and
choose between:
-
Tables - in the formats
ASCII-SPRING, SPACESTAT ou CSV;
-
Non-Spatial Tables - in the
ASCII-SPRING or CSV format;
-
clickon Category...
to choose what
you want to export. The window "Categories List" is presented. Choose one
from
the list and
click on
Apply;
-
click
on
Save
...
-
in the window
"SPRING of Files" inform the
destination directory, type the file name and click on the button Save;
IMPORTANT :
By convention when IL's are
exported to the ASCII-SPRING format, some suffixes are added to the IL's
name. The table at the end of the page shows such extensions for every exported
entity, which entity should be selected for importing and some observations.

TABLES
- ASCII-SPRING
The table below shows the extensions created by the exportation of
data in the ASCII-SPRING format, the import and export entities selected in
the corresponding window, as well as some observations.
MODEL
|
Entity in
the
exportation
|
Code1*
/ Extensions
|
Entity for
importation
|
OBSERVATION
|
Thematic
|
Lines
and Labels.
|
LINES
/ *_L2D.spr
|
Line without adjustment (1)
Line with adjustment
(2)
Line
with
topology
(3)
|
The differences among the three import
options are: (1) creates only the lines file - can be used for entities
that do not define areas, for example, a river map, or when one knows a
priori that he will have to perform edition/corrections using SPRING; (2)
creates the lines and performs the adjustment of the nodes, however, one
must guarantee that the ends of two lines , for example, must be on the
same point , for the tolerance of the adjustment is zero; (3) creates the
lines, adjusts and polygonizes - should be used
for entities that define areas, however, one must guarantee that the nodes
are adjusted so that the system can create the polygons. The identification
file should be imported right after. In this second file there are
coordinate pairs over lines or internal to the polygon that identifies them
plus the corresponding thematic class.
|
POINTS
/ *_LAB.spr
|
Identifiers
|
Thematic
|
Polyg
.
and
Labels
|
POLYGONS
/ *_POL.spr
|
cannot
be
imported
.
|
All
the polygons are exported as islands, that means,
lines defining borders between two polygons will have this contact
duplicated. Some SPRING tools may not work correctly with this type of
topology, but if you want to import the file *_POL.spr,
rename the internal name POLYGONS to LINES, and later using SPRING you can
use the clean vector tool. The
identification
file should be imported right after.
|
POINTS
/ *_LAB.spr
|
Identifiers
|
Thematic
|
Points
|
POINT2D
/ *_P2D.spr
|
2D
Point
|
The
coordinate of the points and the classes, if they exist, will be in the
same file, for example, (coordX, coordY, Class)
|
Thematic
|
Texts
|
TEXT
/ *_TEX.spr
|
Text
|
All
the characteristics of texts exportation are kept during import.
|
Thematic
|
All
|
*.spr
|
Lines (one of the options)
Identifiers
2D
Point
Text
|
One only
file with many sections will be created during export, that is, LINES,
POINTS, POINT2D and TEXT. The importation should thus be performed by
parts. The contents of some of the parts could be empty, with no data, for
they depend on what we have in the IL of origin. See
the
observations above for each section.
|
Thematic
|
Lines
and Labels
Auto
|
LINES
/ *_L2D.spr
|
Line with adjustment (2)
Line with topology (3)
|
The
lines file should be imported as described in the section about the import
of LINES above. In the files of types POINTS and POINT2D you will
find the identification of the points/lines/polygons in a sequential way. If
there was a point in the origin file, we will have as the identifier of the
class = <IL_name><number>, if
line we will have class = <IL_name>_lin<number>, if polygon we will have class = <IL_name>_pol<number>.
If you want you can change these values before importation, this way you
will have your map with all the entities duly identified.
|
POINTS
/ *_LAB.spr
|
Identifiers
|
POINT2D
/ *_P2D.spr
|
2D
Point
|
Thematic
|
Polyg
. without
Label
|
POINT2D
/ *_SEM.spr
|
2D
Point
|
Creates
a file of the type POINT2D that indicates if there are any unidentified polygons
in your map. Makes it easier to discover association errors when there are
too many polygons in the map. Can be imported as 2D points to present on
the screen where the identification is
missing.
|
Thematic
|
Reg
. Grid
|
GRIDREG
/ *_GRT.spr
|
Regular
Grid/Matrix
|
Creates
a matrix file of the thematic map. The values in the matrix correspond to
the index of the classes. The visual of each index is also exported, being
recoverable during import.
|
|
|
|
|
|
Cadastral
|
Lines
and
Labels
|
LINES
/ *_L2D.spr
|
Line without adjustment (1)
Line with adjustment
(2)
Line
with
topology
(3)
|
The
differences among the three import options are: (1) creates only the lines
file - can be used for entities that do not define areas, for example, a
river map, or when one knows a priori that he will have to perform
edition/corrections using SPRING; (2) creates the lines and performs the
adjustment of the nodes, however, one must guarantee that the ends of two lines
, for example, must be on the same point , for the tolerance of the
adjustment is zero; (3) creates the lines, adjusts and polygonizes
- should be used for entities that define areas, however, one must
guarantee that the nodes are adjusted so that the system can create the
polygons. The identification file should be imported right after. In this
second file there are coordinate pairs over lines or internal to the
polygon that identifies them plus the label, name, and category of the
corresponding object.
|
POINTS
/ *_LAB.spr
|
Identifiers
|
Cadastral
|
Polyg
.
and
Labels
|
POLYGONS
/ *_POL.spr
|
cannot
be
imported
.
|
All
the polygons are exported as islands, that means,
lines defining borders between two polygons will have this contact
duplicated. Some SPRING tools may not work correctly with this type of
topology, but if you want to import the file *_POL.spr,
rename the internal name POLYGONS to LINES, and later using SPRING you can
use the clean vector tool. The
identification
file should be imported right after.
|
POINTS
/ *_LAB.spr
|
Identifiers
|
Cadastral
|
Points
|
POINT2D
/ *_P2D.spr
|
2D
Point
|
The
coordinates of the points, labels, names and categories of objects will be
in the same file, for example, (coordX; coordY; label; name; object)
|
Cadastral
|
Tables
|
TABLE
/ *_TAB.spr
|
Update Object Category/Attribute Table or
Create New Object Category / Attribute Table.
|
The
importation of an object table should be done through the "Import
Tables" window. The name of the categories of the objects should be
defined inside the file, there is no need to
select it on the interface. The key word "CATEGORY_OBJ" identifies the type of the table.
|
Cadastral
|
Non-spatial
Tables
|
TABLE
/ *_TAB.spr
|
Update Non-spatial Table
or
Create New Non-Spatial
Category
|
The
importation of an object table should be done through the "Import
Tables" window. The name of the categories of the objects should be
defined inside the file, there is no need to
select it on the interface. The key word "CATEGORY_NOSPATIAL"
identifies the type of the table.
|
Cadastral
|
Texts
|
TEXT
/ *_TEX.spr
|
Text
|
All
the characteristics of the exportation of texts will be kept during import.
|
Cadastral
|
All
|
*.spr
TABLE / *_TAB.spr
|
Lines (one of the options)
Identifiers
2D Point
Text
"Table
Importation"
|
One only file with many sections will be
created during export, that is, LINES, POINTS, POINT2D and TEXT. The
importation should thus be performed by parts. The contents of some of the
parts could be empty, with no data, for they depend on what we have in the
IL of origin. See the observations above for each section. The attributes
of the objects in the IL will be exported with the type TABLE.
|
Cadastral
|
Lines
and Labels
Auto
|
LINES
/ *_L2D.spr
|
Line with adjustment (2)
Line with topology (3)
|
The lines file should be imported as
described in the section about the import of LINES above. In the
files of types POINTS and POINT2D you will find the identification of the
points/lines/polygons in a sequential way. If there was a point in the
origin file, we will have as the identifier of the object = <IL_name><number>+<object_cat>, if line we will have object = <IL_name>_lin<number>+<object_cat>,, if polygon
we will have object = <IL_name>_pol<number>+<object_cat>,.
If you want you can change these values before importation, this way you
will have your map with all the entities duly identified.
|
POINTS
/ *_LAB.spr
|
Identifiers
|
POINT2D
/ *_P2D.spr
|
2D
Point
|
Cadastral
|
Spatial Lag.Matrix
(format SPACESTAT)
|
*.gal
|
Non
Importable
|
File with the Spatial Lag. Matrix between
unidentified polygons of an objects map. The file will only be read by the
program SPACESAT.
|
Cadastral
|
Polyg
. without
Labels
|
POINT2D
/ *_SEM.spr
|
2D
Point
|
Creates
a file of the type POINT2D that indicates if there are any unidentified
polygons in your map. Makes it easier to discover association errors when
there are too many polygons in the map. Can be imported as 2D points to
present on the screen where the identification is
missing.
|
|
|
|
|
|
Networks
|
Lines
and
Labels
|
NETWORK
/ *_NET.spr
|
Line without adjustment (1)
Line with adjustment
(2)
Line
with
topology
(3)
|
The
differences among the three import options are: (1) creates only the lines
file - can be used for entities that do not define areas, for example, a
river map, or when one knows a priori that he will have to perform
edition/corrections using SPRING; (2) creates the lines and performs the
adjustment of the nodes, however, one must guarantee that the ends of two
lines , for example, must be on the same point , for the tolerance of the
adjustment is zero; (3) same as option (2) for it makes no sense the
polygonalization in the network model. The identification file should be
imported right after. In this second file there are coordinate pairs over
lines that identify them plus the label, name, and category of the
corresponding object, besides the information if it is a network node or a
LINE.
|
NETWORK_OBJECTS
/ *_NETOBJ.spr
|
Identifiers
|
Networks
|
Tables
|
TABLE
/ *_TAB.spr
|
Update Object Category/Attribute Table or
Create New Object Category / Attribute Table.
|
The importation
of an object table should be done through the "Import Tables"
window. The name of the categories of the objects should be defined inside
the file, there is no need to select it on the
interface. The key word "CATEGORY_OBJ"
identifies the type of the table.
|
Networks
|
Non-spatial
Tables
|
TABLE
/ *_TAB.spr
|
Update Non-spatial Table
or
Create New Non-Spatial
Category
|
The importation of an object table should
be done through the "Import Tables" window. The name of the
categories of the objects should be defined inside the file,
there is no need to select it on the interface. The key word
"CATEGORY_NOSPATIAL" identifies the type of the table.
|
Networks
|
Texts
|
TEXT
/ *_TEX.spr
|
Text
|
All the
characteristics of the exportation of texts will be kept during import.
|
Networks
|
All
|
*.spr
TABLE / *_TAB.spr
|
Lines
Identifiers
Text
"Table
Importation"
|
One only
file with many sections will be created during export, that is, NETWORK,
NETWORK_OBJECTS and TEXT. The importation should thus be performed by
parts. The contents of some of the parts could be empty, with no data, for
they depend on what we have in the IL of origin. See the observations above
for each section. The attributes of the objects in the IL will be exported
with the type TABLE.
|
|
|
|
|
|
Numeric
|
Samples
|
SAMPLE
/ *_L3D.spr
|
Samples
(DEM)
|
In a
samples file we can have spot heights and contour lines, in separate
sections. The file of type LINES exported together with the samples stores
the break lines that are in fact 2D lines without heights. Any file of the
LINES type can be imported with break lines.
|
LINES
/ *_L2D.spr
|
Break
Line (DEM)
|
Numeric
|
Reg
. Grid
|
GRIDREG
/ *GRR.spr
|
Regular
Grid/Matrix
|
File with a matrix of real numbers.
|
Numeric
|
Contour
Lines
|
CONTOURLINES
/ *ISO.spr
|
cannot
be
imported
|
The
Contour Lines exported correspond to the ones generated by the process of
interpolation of the grid, different from the
samples. In fact it is an contour line that in
order to be imported needs to have the name CONTOURLINE changed to SAMPLE.
|
Numeric
|
Texts
|
TEXT
/ *_TEX.spr
|
Text
|
All the characteristics of the exportation
of texts will be kept during import.
|
Numeric
|
All
|
*.spr
|
Samples
Break Line (DEM)
Text
Regular Grid/Matrix
|
One
only file with many sections will be created during export, that is,
SAMPLE, LINES, CONTOURLINES, TEXT and GRIDREG. The importation should thus
be performed by parts. The contents of some of the parts could be empty,
with no data, for they depend on what we have in the IL of origin. See the
observations above for each section.
|
1*
- Corresponds to
the reserved words in the first line of the SPR file / and the suffixes used
in front of the IL name during export. For importation, it is enough to have
the extension *.spr and the reserve word within the
file plus the data
See also:
Definition
of Database
Definition
of Data Model
How
to IMPORT data from the GIS?
How
to IMPORT GRIB images?
How
to IMPORT data ?
How
to EXPORT to the SpringWEB
?
How
to EXPORT to
TerraLib
?
|