[Geoserver-users] Importing of shape- and related files

Hi there,
I am trying to import data into GeoServer using the Shapefile
datasource. However, it seems only .shp files are supported.

My data is contained in a file combo of
xxx.AVL
xxx.DBF
xxx.QIX
xxx.SHP
xxx.SHX
xxx.E00

and a couple of .DXF files.

Is there any howto on how to import this information?

Cheers

/peter

--
GTalk: neubauer.peter
Skype peter.neubauer
ICQ 18762544
GTalk neubauer.peter
Phone +46704 106975
Mail peter.neubauer@anonymised.com
LinkedIn http://www.linkedin.com/in/neubauer

http://www.neo4j.org - New Energy for Data - the Netbase.
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
http://www.qi4j.org - New Energy for Java - Domain Driven Development.

Peter Neubauer ha scritto:

Hi there,
I am trying to import data into GeoServer using the Shapefile
datasource. However, it seems only .shp files are supported.

My data is contained in a file combo of
xxx.AVL
xxx.DBF
xxx.QIX
xxx.SHP
xxx.SHX
xxx.E00

and a couple of .DXF files.

Is there any howto on how to import this information?

GeoServer can only load the .shp, .shx, .dbf, and you're
missing the .prj needed for projection definition (so you'll
have to specify one when loading the data).

The .qix file should be a spatial index, if it's in the right
format GeoServer will make use of it (what did generate it?
GeoServer is compatible with the .qif files generated by
shptree, an utility shipped with mapserver, and can generate
them when missing provided the shapefile is not too big).

The e00 file should be an arcinfo export and I guess
it contains the same information as the shp, but in
topological format (we are not able to read it anyways).

The avl file I'm not sure, but we can't open it either.

Anyways, if you want to display the shapefile contents
and query attributes, the .shp, .shx and .dbf are all
you need.

Cheers
Andrea

Andrea,
thanks for your fast reply! I don't have the prj filees, but I know
the projection which I filled in during the .shp import.

In order to get this in, is there any howto on constructing the prj
files, and after that, do I just specify a folder for the shapefiel
datasource? I have only tried to import all .SHP files one by one,
thus not being able to point out any other dbf/shx files in the same
/data folder.

I guess I am missing a tutorial on how to do this in the GeoServer
configuration interface :confused:

Thanks for your help!

/peter

On Jan 29, 2008 2:50 PM, Andrea Aime <aaime@anonymised.com> wrote:

Peter Neubauer ha scritto:
> Hi there,
> I am trying to import data into GeoServer using the Shapefile
> datasource. However, it seems only .shp files are supported.
>
> My data is contained in a file combo of
> xxx.AVL
> xxx.DBF
> xxx.QIX
> xxx.SHP
> xxx.SHX
> xxx.E00
>
> and a couple of .DXF files.
>
> Is there any howto on how to import this information?

GeoServer can only load the .shp, .shx, .dbf, and you're
missing the .prj needed for projection definition (so you'll
have to specify one when loading the data).

The .qix file should be a spatial index, if it's in the right
format GeoServer will make use of it (what did generate it?
GeoServer is compatible with the .qif files generated by
shptree, an utility shipped with mapserver, and can generate
them when missing provided the shapefile is not too big).

The e00 file should be an arcinfo export and I guess
it contains the same information as the shp, but in
topological format (we are not able to read it anyways).

The avl file I'm not sure, but we can't open it either.

Anyways, if you want to display the shapefile contents
and query attributes, the .shp, .shx and .dbf are all
you need.

Cheers
Andrea

--
GTalk: neubauer.peter
Skype peter.neubauer
ICQ 18762544
GTalk neubauer.peter
Phone +46704 106975
Mail peter.neubauer@anonymised.com
LinkedIn http://www.linkedin.com/in/neubauer

http://www.neo4j.org - New Energy for Data - the Netbase.
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
http://www.qi4j.org - New Energy for Java - Domain Driven Development.