GeoServer

FeatureType cannot be created for postGIS table with single point

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: 1.6.2
  • Fix Version/s: 1.6.2
  • Component/s: Configuration
  • Labels:
    None
  • Environment:
    Debian 4.0 rc2
  • Testcase included:
    yes
  • Number of attachments :
    0

Description

When I create a spatial table in postgis with the following:

CREATE TABLE points
(
gid serial NOT NULL,
point_type integer,
the_geom geometry,
CONSTRAINT enforce_dims_the_geom CHECK (ndims(the_geom) = 2),
CONSTRAINT enforce_geotype_the_geom CHECK (geometrytype(the_geom) = 'POINT'::text OR the_geom IS NULL),
CONSTRAINT enforce_srid_the_geom CHECK (srid(the_geom) = 4326)
)
WITHOUT OIDS;
ALTER TABLE points OWNER TO postgres;

insert into points(point_type, the_geom) values (0,SetSRID(MakePoint(50,50),4326))

I cannot create a featureType for this table because Geoserver reports:

The FeatureType 'point' has a NULL extent.
HINT: the dataset is empty or has no default geometry attribute.

Activity

Hide
Milo van der Linden added a comment -

This bug appears if the "type" column in postGIS geometry_columns table does not match the geometry_type for the point table.

I resolved this issue by altering the contents of type in the geometry_columns table.

Show
Milo van der Linden added a comment - This bug appears if the "type" column in postGIS geometry_columns table does not match the geometry_type for the point table. I resolved this issue by altering the contents of type in the geometry_columns table.
Hide
Andrea Aime added a comment -

All these issues have been in "resolved" state for at least one month (many of them, much more than that). Since no one has reopened them, I'm mass-switching them to closed state. Reopen if you feel the issue has not been addressed properly.

Show
Andrea Aime added a comment - All these issues have been in "resolved" state for at least one month (many of them, much more than that). Since no one has reopened them, I'm mass-switching them to closed state. Reopen if you feel the issue has not been addressed properly.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: