<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">Hello all,<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I know it is a bit of a broad question, but after quite a few experiments I still feel a bit puzzled as to which way I want to set up a map in our application. The map displays certain areas (catchments, bay areas, etc.). The user should be able to click on those areas, which then shows detailed information in a side bar (div on the same level as the map's div).<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>We are using a stack with PostGIS and GeoServer and I managed to get the basic functionality working in different ways, e.g. using GeoServer's map previews as example as well as http://openlayers.org/dev/examples/getfeature-wfs.html .<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>But getting it to work is only one thing, I'd like to get some more understanding on the implications of different approaches. The two main concerns for me at the moment are the browser support and the number of roundtrips some approaches seem to take.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I saw http://trac.openlayers.org/wiki/Browsers -- does that mean all OpenLayers features are fully supported in each of these? Can I e.g. use an all-vector approach for the overlays and expect them to work?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>And regarding the round trips: I would like the map view not to hit our server more than once per interaction -- mostly to keep the map snappy, but also to not but unnecessary burden on the server. The UI won't allow arbitrary zooming and panning, so bounds should get invalidated only as a result of some custom callback.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I was thinking along the lines of loading all polygons as WFS layer -- is that the way to do it? Should I set a specific strategy? I can't find much documentation on strategies.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Thanks for any hints/experiences you are willing to share.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Cheers,<br>
Peter</p></body></html>