[Geoserver-users] Design Thoughts- Lots of point data. WFS? WMS?

Using OpenLayers and GeoServer. Essentially we have lots (>10,000) points
(lat, lon with other string data) that we would like to overlay on some WMS
layer (google maps, virtual earth, etc.). User must be able to click points
to display pop ups. The data is currently stored in mysql db(essentially
lat, lon, and some other data) and we're using JSON to retrieve it from a
java servlet, but that can be modified.

Looking for the most efficient way to render the data in terms of
responsiveness.

I'm pretty new to OpenLayers and GeoServer so I thought I'd just throw this
out there to get some ideas.

Thanks a lot!
--
View this message in context: http://www.nabble.com/Design-Thoughts--Lots-of-point-data.--WFS--WMS--tp21363194p21363194.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Hi,

On Fri, Jan 9, 2009 at 12:43 AM, vjalfxweb <juddy.g@anonymised.com> wrote:

Using OpenLayers and GeoServer. Essentially we have lots (>10,000) points
(lat, lon with other string data) that we would like to overlay on some WMS
layer (google maps, virtual earth, etc.). User must be able to click points
to display pop ups. The data is currently stored in mysql db(essentially
lat, lon, and some other data) and we're using JSON to retrieve it from a
java servlet, but that can be modified.

Looking for the most efficient way to render the data in terms of
responsiveness.

I would suggest a combined WMS/WFS solution: render your map using
WMS, and use WFS GetFeature with a click handler to retreive the
features for the region the user clicked.

For this, you could use the WFSGetFeature control that OpenGeo is
about to contribute to OpenLayers. You can see it in action at
http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html

Comments on the usefulness and test reports for this control are appreciated.

Regards,
Andreas.

--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

Something I failed to mention before is that we're currently displaying these
points based on how long they've been around and also where they are in
terms of lat, long. The data changes a fair amount too on the fly. Does
this change anything?

Our main goal was to be able to zoom out far on the map and still see the
data and it not take forever to load. Once the user zooms in further and
the data makes more sense, popups would be enabled on the points.

Thanks a lot for the help!

Andreas Hocevar-3 wrote:

Hi,

On Fri, Jan 9, 2009 at 12:43 AM, vjalfxweb <juddy.g@anonymised.com> wrote:

Using OpenLayers and GeoServer. Essentially we have lots (>10,000)
points
(lat, lon with other string data) that we would like to overlay on some
WMS
layer (google maps, virtual earth, etc.). User must be able to click
points
to display pop ups. The data is currently stored in mysql db(essentially
lat, lon, and some other data) and we're using JSON to retrieve it from
a
java servlet, but that can be modified.

Looking for the most efficient way to render the data in terms of
responsiveness.

I would suggest a combined WMS/WFS solution: render your map using
WMS, and use WFS GetFeature with a click handler to retreive the
features for the region the user clicked.

For this, you could use the WFSGetFeature control that OpenGeo is
about to contribute to OpenLayers. You can see it in action at
http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html

Comments on the usefulness and test reports for this control are
appreciated.

Regards,
Andreas.

--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
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/Design-Thoughts--Lots-of-point-data.--WFS--WMS--tp21363194p21383467.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Hey,

You should also be aware of the getfeatureinfo templates in
geoserver.. assuming that your attribute data is stored in the same
mysql table as the geometries you can use the templates to present the
attribute data and straight WMS to draw the points on the map.. if
the attribute data is not on the same table (or in multiple tables)
then you will need to register a click event in openlayers to fetch
the html content of the identify-servlet based on an ID.. and then
display in a popup the same as for the getfeatureinfo. one downside
features are not available as such in openlayers (as variables
themseves) this way as they are using WFS, so your app cant 'use' the
data so readily.. but it maybe a slightly simpler setup. anyway just
suggesting a plan b.

using either wms or wfs to fetch the content openlayers can create a
persitant popup marker with the pretty content when you click on the
map.. i believe there is an example of this in the openlayers install.

http://geoserver.org/display/GEOSDOC/GetFeatureInfo+templates

-i

2009/1/9 Andreas Hocevar <ahocevar@anonymised.com>:

Hi,

On Fri, Jan 9, 2009 at 12:43 AM, vjalfxweb <juddy.g@anonymised.com> wrote:

Using OpenLayers and GeoServer. Essentially we have lots (>10,000) points
(lat, lon with other string data) that we would like to overlay on some WMS
layer (google maps, virtual earth, etc.). User must be able to click points
to display pop ups. The data is currently stored in mysql db(essentially
lat, lon, and some other data) and we're using JSON to retrieve it from a
java servlet, but that can be modified.

Looking for the most efficient way to render the data in terms of
responsiveness.

I would suggest a combined WMS/WFS solution: render your map using
WMS, and use WFS GetFeature with a click handler to retreive the
features for the region the user clicked.

For this, you could use the WFSGetFeature control that OpenGeo is
about to contribute to OpenLayers. You can see it in action at
http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html

Comments on the usefulness and test reports for this control are appreciated.

Regards,
Andreas.

--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi Andreas,

i dont know if its old version, but one (maybe more?) API property is
missing in wfsgetfeature module: geometryName. Now it always takes
"the_geom", default to wfs protocol.

Regards,
Ivan

On Fri, Jan 9, 2009 at 4:32 PM, Andreas Hocevar <ahocevar@anonymised.com> wrote:

Hi,

On Fri, Jan 9, 2009 at 12:43 AM, vjalfxweb <juddy.g@anonymised.com> wrote:

Using OpenLayers and GeoServer. Essentially we have lots (>10,000) points
(lat, lon with other string data) that we would like to overlay on some WMS
layer (google maps, virtual earth, etc.). User must be able to click points
to display pop ups. The data is currently stored in mysql db(essentially
lat, lon, and some other data) and we're using JSON to retrieve it from a
java servlet, but that can be modified.

Looking for the most efficient way to render the data in terms of
responsiveness.

I would suggest a combined WMS/WFS solution: render your map using
WMS, and use WFS GetFeature with a click handler to retreive the
features for the region the user clicked.

For this, you could use the WFSGetFeature control that OpenGeo is
about to contribute to OpenLayers. You can see it in action at
http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html

Comments on the usefulness and test reports for this control are appreciated.

Regards,
Andreas.

--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ivan Grcic

Hi Andreas,

I loved the hover functionality in the WFSGetFeature control. I realize the
overhead it may impose and hence it came to my mind whether it could be
benefited from an extra GetFeature optional parameter to decimate the
geometries based on the map's dimensions, the same way the WMS does..

That is, we could add this extra parameter to GeoServer's GetFeature operation
and get smaller geometries as good for the map as the rendered ones are.

What do you think?

Gabriel

On Friday 09 January 2009 13:32:05 Andreas Hocevar wrote:

Hi,

On Fri, Jan 9, 2009 at 12:43 AM, vjalfxweb <juddy.g@anonymised.com> wrote:
> Using OpenLayers and GeoServer. Essentially we have lots (>10,000)
> points (lat, lon with other string data) that we would like to overlay on
> some WMS layer (google maps, virtual earth, etc.). User must be able to
> click points to display pop ups. The data is currently stored in mysql
> db(essentially lat, lon, and some other data) and we're using JSON to
> retrieve it from a java servlet, but that can be modified.
>
> Looking for the most efficient way to render the data in terms of
> responsiveness.

I would suggest a combined WMS/WFS solution: render your map using
WMS, and use WFS GetFeature with a click handler to retreive the
features for the region the user clicked.

For this, you could use the WFSGetFeature control that OpenGeo is
about to contribute to OpenLayers. You can see it in action at
http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html

Comments on the usefulness and test reports for this control are
appreciated.

Regards,
Andreas.

--
Gabriel Roldan
OpenGeo - http://www.opengeo.org

Hi Gabriel,

On Sun, Jan 25, 2009 at 7:36 PM, Gabriel Roldan <groldan@anonymised.com> wrote:

I loved the hover functionality in the WFSGetFeature control. I realize the
overhead it may impose and hence it came to my mind whether it could be
benefited from an extra GetFeature optional parameter to decimate the
geometries based on the map's dimensions, the same way the WMS does..

You mean by resolution? That would be awsome! This is one of the
frequently requested features on the openlayers-users list: to have a
server that returns geometries with just that much detail as required
for the current resolution.

That is, we could add this extra parameter to GeoServer's GetFeature operation
and get smaller geometries as good for the map as the rendered ones are.

What do you think?

If possible, this would be a killer feature (at least in my opinion).

Andreas.

On Friday 09 January 2009 13:32:05 Andreas Hocevar wrote:

Hi,

On Fri, Jan 9, 2009 at 12:43 AM, vjalfxweb <juddy.g@anonymised.com> wrote:
> Using OpenLayers and GeoServer. Essentially we have lots (>10,000)
> points (lat, lon with other string data) that we would like to overlay on
> some WMS layer (google maps, virtual earth, etc.). User must be able to
> click points to display pop ups. The data is currently stored in mysql
> db(essentially lat, lon, and some other data) and we're using JSON to
> retrieve it from a java servlet, but that can be modified.
>
> Looking for the most efficient way to render the data in terms of
> responsiveness.

I would suggest a combined WMS/WFS solution: render your map using
WMS, and use WFS GetFeature with a click handler to retreive the
features for the region the user clicked.

For this, you could use the WFSGetFeature control that OpenGeo is
about to contribute to OpenLayers. You can see it in action at
http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html

Comments on the usefulness and test reports for this control are
appreciated.

Regards,
Andreas.

--
Gabriel Roldan
OpenGeo - http://www.opengeo.org

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

On Monday 26 January 2009 14:19:50 Andreas Hocevar wrote:

Hi Gabriel,

On Sun, Jan 25, 2009 at 7:36 PM, Gabriel Roldan groldan@anonymised.com wrote:

I loved the hover functionality in the WFSGetFeature control. I realize

the overhead it may impose and hence it came to my mind whether it could

be benefited from an extra GetFeature optional parameter to decimate the

geometries based on the map’s dimensions, the same way the WMS does…

You mean by resolution? That would be awsome! This is one of the

frequently requested features on the openlayers-users list: to have a

server that returns geometries with just that much detail as required

for the current resolution.

Yeah, it seems there’s concensus on its usefulness and that we can do that. Next to see whether to do that on spare time or not

[14:02] hey guys, it seems the OL guys would love us if we add decimation/generalization support to WFS

[14:02] (and its not the first time someone asks)

[14:03] so it seems pretty easy to me, a custom parameter to getfeature and some JTS generalization

[14:03] am I being too naive?

[14:04] → SEWilco2 has joined this channel (n=sewilco@anonymised.com).

[14:04] → iwillig has joined this channel (n=ivan@anonymised.com).

[14:04] ( and yeah I know that sort of fall into the wcs scope)

[14:05] but how many times wfs is used for rendering? lots

[14:05] aaime, jdeolive?

[14:05] sorry?

[14:05] hi, should of pinged before my speech

[14:05] ah, I see

[14:06] yeah, i can def see the use case… i guess its just a custom parameter along with a query hint?

[14:06] groldan, that seems to fall squaredly in the wps use case

[14:06] do we have a query hint for generalization? used for rendering?

[14:06] thought I agree it would be useful in wfs too

[14:06] aaime: I know

[14:06] yet…

[14:06] jdeolive, the generalization is part of the renderer code

[14:06] it’s not an hint

[14:07] gotcha

[14:07] we should wrap teh returned feature collection with a decimating wrapper

[14:07] right

[14:07] so it woudl be a matter of setting a decimation vendor option

[14:07] using it in GetFeature to decide wheter the returned feature collections should be decimated or not

[14:08] I would not be against it, thought it seems to add complexity in the wrong place

[14:08] yet, wps is another protocol and I understand that it would require a different client

[14:09] soo… I guess open a jira issue about that?

[14:09] and eventually decide wheter you want to sponsor it for a certain release

[14:09] yeah, I share your concern

[14:09] or let’s decide if OpenGeo wants to sponsor that

[14:09] but I guess the use case is wide spread enough as to deserve it

[14:09] (cholmes, where are you when we need you most? ;.) )

[14:10] http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html

[14:10] Title: WFS: GetFeature Example (GeoServer) (at dev.openlayers.org)

[14:10] groldan, I know about the use case all too well :wink:

[14:10] that’s my primary goal, helping out Andreas with the hover functionality

[14:11] aaime: sure you do, it’s related to performance :slight_smile:

That is, we could add this extra parameter to GeoServer’s GetFeature

operation and get smaller geometries as good for the map as the rendered

ones are.

What do you think?

If possible, this would be a killer feature (at least in my opinion).

Andreas.

On Friday 09 January 2009 13:32:05 Andreas Hocevar wrote:

Hi,

On Fri, Jan 9, 2009 at 12:43 AM, vjalfxweb juddy.g@anonymised.com wrote:

Using OpenLayers and GeoServer. Essentially we have lots (>10,000)

points (lat, lon with other string data) that we would like to overlay

on some WMS layer (google maps, virtual earth, etc.). User must be

able to click points to display pop ups. The data is currently stored

in mysql db(essentially lat, lon, and some other data) and we’re

using JSON to retrieve it from a java servlet, but that can be

modified.

Looking for the most efficient way to render the data in terms of

responsiveness.

I would suggest a combined WMS/WFS solution: render your map using

WMS, and use WFS GetFeature with a click handler to retreive the

features for the region the user clicked.

For this, you could use the WFSGetFeature control that OpenGeo is

about to contribute to OpenLayers. You can see it in action at

http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html

Comments on the usefulness and test reports for this control are

appreciated.

Regards,

Andreas.

Gabriel Roldan

OpenGeo - http://www.opengeo.org


----- This SF.net email is sponsored by:

SourcForge Community

SourceForge wants to tell your story.

http://p.sf.net/sfu/sf-spreadtheword


Geoserver-users mailing list

Geoserver-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geoserver-users

Gabriel Roldan

OpenGeo - http://www.opengeo.org