Hello!
Setting up a geoserver Feature Type using postgis data set and getting this
error:
"The FeatureType 'callesnac' has a NULL extent.
HINT: the dataset is empty or has no default geometry attribute."
Some reading suggest that the geometry column in postgres has not been
declared, but when looking at the table's column with pgAdmin III I see that
the column "the_geom" specifies the Data Type as "geometry", so, what do you
think is the problem?
Thanks!
--
View this message in context: http://www.nabble.com/the-dataset-is-empty-or-has-no-default-geometry-attribute-tp20781431p20781431.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
The problem is mostly likely that the geometry column has not been registered in the geometry_columns table. You can manually insert a row into geometry_columns and it should work.
Or... the dataset is actually empty and there are no rows in the table.
-Justin
SenTnel wrote:
Hello!
Setting up a geoserver Feature Type using postgis data set and getting this
error:
"The FeatureType 'callesnac' has a NULL extent. HINT: the dataset is empty or has no default geometry attribute."
Some reading suggest that the geometry column in postgres has not been
declared, but when looking at the table's column with pgAdmin III I see that
the column "the_geom" specifies the Data Type as "geometry", so, what do you
think is the problem?
Thanks!
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Thanks for helping! There´s just one thing:
"You can manually insert a row into geometry_columns"
How do I accomplish that?
The dataset is not empty.
Thanks again.
Justin Deoliveira-6 wrote:
The problem is mostly likely that the geometry column has not been
registered in the geometry_columns table. You can manually insert a row
into geometry_columns and it should work.
Or... the dataset is actually empty and there are no rows in the table.
-Justin
SenTnel wrote:
Hello!
Setting up a geoserver Feature Type using postgis data set and getting
this
error:
"The FeatureType 'callesnac' has a NULL extent.
HINT: the dataset is empty or has no default geometry attribute."
Some reading suggest that the geometry column in postgres has not been
declared, but when looking at the table's column with pgAdmin III I see
that
the column "the_geom" specifies the Data Type as "geometry", so, what do
you
think is the problem?
Thanks!
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
View this message in context: http://www.nabble.com/the-dataset-is-empty-or-has-no-default-geometry-attribute-tp20781431p20800571.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
The following insert should so it:
INSERT INTO geometry_columns VALUES ('','public','callesnac,'the_geom',2,<srid>,<geometryType>);
Where <srid> is the identifier of the spatial reference system for your data (example 4326). And <geometryType> is the class of geometry of your data (example 'MULTIPILYGON').
Hope that helps.
-Justin
SenTnel wrote:
Thanks for helping! There´s just one thing: "You can manually insert a row into geometry_columns"
How do I accomplish that?
The dataset is not empty.
Thanks again.
Justin Deoliveira-6 wrote:
The problem is mostly likely that the geometry column has not been registered in the geometry_columns table. You can manually insert a row into geometry_columns and it should work.
Or... the dataset is actually empty and there are no rows in the table.
-Justin
SenTnel wrote:
Hello!
Setting up a geoserver Feature Type using postgis data set and getting
this
error:
"The FeatureType 'callesnac' has a NULL extent. HINT: the dataset is empty or has no default geometry attribute."
Some reading suggest that the geometry column in postgres has not been
declared, but when looking at the table's column with pgAdmin III I see
that
the column "the_geom" specifies the Data Type as "geometry", so, what do
you
think is the problem?
Thanks!
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.