[Geoserver-users] Problems showing linestring in Google Earth

GeoServer GeoServer User
1

I have a linestring in PostgresQL database.

I make a featuretype and I can view it in any other client except for Google
Earth. I can't figure out why this is happening.

The script used to create the linestring was

CREATE TABLE sensornet_drop1_try2_linestring_2
(
  platform_id integer,
  sample_time double precision
)
WITHOUT OIDS;
SELECT AddGeometryColumn( 'echang', 'sensornet_drop1_try2_linestring_2',
'the_geom', 4269, 'LINESTRING', 2 );

INSERT INTO echang.sensornet_drop1_try2_linestring_2
  SELECT platform_id, ST_makeline(the_geom) AS the_geom
  FROM
    (SELECT platform_id, the_geom FROM echang.sensornet_drop1_try2 ORDER BY
platform_id, time_mark) a
  GROUP BY platform_id;

The data is basically one linestring with platform_id being all the same.

Thanks for any help.

--
View this message in context: http://www.nabble.com/Problems-showing-linestring-in-Google-Earth-tp21984715p21984715.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

There is a bug in GeoServer 1.7.1 that keeps regionated KML output from
including features for postgis layers that do not have a primary key
set. Inconveniently, this version also made regionated KML the default
when clicking the KML link from the map preview page. There are a
number of fixes and workarounds:

1) Add a primary key to your table and clear out
${GEOSERVER_DATA_DIR}/geosearch/
2) Upgrade to 1.7.2, where GeoServer recognizes that regionating fails
for the layer and gives back 'refresh' mode KML (see below)
3) Append '&mode=refresh' to your request parameters, which causes
GeoServer to use the older form of KML output, which uses an
auto-refreshing view and switches between raster and vector mode based
on the number of features in view.

Hope this helps,
--
David Winslow
OpenGeo - http://opengeo.org/

On Thu, 2009-02-12 at 14:27 -0800, ec2929 wrote:

I have a linestring in PostgresQL database.

I make a featuretype and I can view it in any other client except for Google
Earth. I can't figure out why this is happening.

The script used to create the linestring was

CREATE TABLE sensornet_drop1_try2_linestring_2
(
  platform_id integer,
  sample_time double precision
)
WITHOUT OIDS;
SELECT AddGeometryColumn( 'echang', 'sensornet_drop1_try2_linestring_2',
'the_geom', 4269, 'LINESTRING', 2 );

INSERT INTO echang.sensornet_drop1_try2_linestring_2
  SELECT platform_id, ST_makeline(the_geom) AS the_geom
  FROM
    (SELECT platform_id, the_geom FROM echang.sensornet_drop1_try2 ORDER BY
platform_id, time_mark) a
  GROUP BY platform_id;

The data is basically one linestring with platform_id being all the same.

Thanks for any help.

3

Hi,

I tried this and it didn't work. I tried appending &mode=refresh to the
end of my parameters and I also upgraded to 1.7.2.

Is there something else I can try?

- Elizabeth

-----Original Message-----
From: David Winslow [mailto:dwinslow@anonymised.com]
Sent: Thursday, February 12, 2009 8:06 PM
To: Chang, Elizabeth
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Problems showing linestring in Google
Earth

There is a bug in GeoServer 1.7.1 that keeps regionated KML output from
including features for postgis layers that do not have a primary key
set. Inconveniently, this version also made regionated KML the default
when clicking the KML link from the map preview page. There are a
number of fixes and workarounds:

1) Add a primary key to your table and clear out
${GEOSERVER_DATA_DIR}/geosearch/
2) Upgrade to 1.7.2, where GeoServer recognizes that regionating fails
for the layer and gives back 'refresh' mode KML (see below)
3) Append '&mode=refresh' to your request parameters, which causes
GeoServer to use the older form of KML output, which uses an
auto-refreshing view and switches between raster and vector mode based
on the number of features in view.

Hope this helps,
--
David Winslow
OpenGeo - http://opengeo.org/

On Thu, 2009-02-12 at 14:27 -0800, ec2929 wrote:

I have a linestring in PostgresQL database.

I make a featuretype and I can view it in any other client except for

Google

Earth. I can't figure out why this is happening.

The script used to create the linestring was

CREATE TABLE sensornet_drop1_try2_linestring_2
(
  platform_id integer,
  sample_time double precision
)
WITHOUT OIDS;
SELECT AddGeometryColumn( 'echang',

'sensornet_drop1_try2_linestring_2',

'the_geom', 4269, 'LINESTRING', 2 );

INSERT INTO echang.sensornet_drop1_try2_linestring_2
  SELECT platform_id, ST_makeline(the_geom) AS the_geom
  FROM
    (SELECT platform_id, the_geom FROM echang.sensornet_drop1_try2

ORDER BY

platform_id, time_mark) a
  GROUP BY platform_id;

The data is basically one linestring with platform_id being all the

same.

Thanks for any help.