Just a note to leave a trace of the solution : the reason why I couldnīt spit the GetFeatureInfo call result into a div (see previous posts in this thread for a complete history) was that I was using an html file through the file:/// protocol (e.g. file:///mydir/index.html). The minute I shoved my html file in my Apache DocumentRoot folder, all problems disappeared because I could reference my file through http (http://myserver:myport/index.html). <br><br>NOTE : I still could do a window.open or use an external JS function (see thread history) with my index.html file accessed via the file:/// protocol, so my focus was on why the OpenLayers.loadURL function did not work whereas the other ways of displaying the info did work ...<br><br>So if anyone gets this kind of an error :<br><br>This proxy does not allow you to access that location.<br><br>{'TMP': 'C:/Program Files/ms4w/tmp', 'HTTP_COOKIE': ...)<br><br>think about *not* using file:///
:-).<br><br>Yves<br><br><b><i>Yves Moisan <yves.moisan@boreal-is.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Hi All,<br><br>Audience of this message : users of MapServer (WMS).<br><br>I'm trying to find examples of how to retrieve attributes from a postgis<br>table served via MapServer WMS. I have my points in OL, now I want and<br>"info" on them. I understand I have to enable the layer to be queryable<br>in my mapfile. So I googled and found a top level directive (QUERY \n<br>STATUS ON), but that was found to be an offending command. I also found<br>a bunch of other directives, so my mapfile now looks like this : <br><br> METADATA<br> # OGC:WMS specific tags<br> "ows_title" "Resettlement Sites" <br> "ows_abstract" "RAP Resettlement Sites"<br> "ows_keywordlist" "Resettlement, TFM" <br> "ows_srs" "EPSG:32735"<br> "wms_opaque" "0"<br>
"wms_group_title" "Data"<br> "wms_group_abstract" Data"<br> "wms_dataurl_href" "http://someserver:8081/data/"<br> "wms_dataurl_format" "text/html"<br> "ows_metadataurl_type" "FGDC"<br> "ows_metadataurl_href"<br>"http://someserver:8081/ms_ogc_workshop/index.html"<br> "ows_metadataurl_format" "text/html"<br> "ows_extent" "389443 8816705 442791 8858984"<br><br> # OGC:WFS specific tags<br><br># /WFS_Capabilities/FeatureTypeList/FeatureType[*]/MetadataURL/@format<br> "wfs_metadataurl_format" "TXT"<br> # specify which fields to include when returning queries<br> "gml_include_items" "all" <br><br>The mapfile top level projection is set to 900913 and that gets<br>translated fine overtop of a Google base layer. <br><br>On the OL side, I found some InfoButton code which I think I have<br>adapted correctly for my layer. I don't see anything when I click on my<br>map. I'm obviously missing something and I won't go into the details,<br>but rather I will just
ask for pointers to example MapServer served WMS<br>layers that are queryable through OL (that is, one clicks and some div<br>gets populated with attribute content or better some popup appears)<br>showing all settings. I am a bit flabergasted by the number of moving<br>parts. <br><br>Just for the sake of it, I extracted my data and turned it into a<br>textfile which I then used in OpenLayers.Layer.Text (as per<br>http://wiki.openstreetmap.org/index.php/Openlayers_POI_layer_example).<br>OOTB, one gets a nice popup, default icon and default html formatting.<br>I wonder if one could get as easy a popup solution for a WMS served<br>queryable layer ? I wouldn't be so crazy as to generate a textfile on<br>the fly to duplicate my layer so that it becomes easily queryable ...<br><br>Thanx for pointers,<br><br>Yves Moisan<br><br>_______________________________________________<br>Users mailing
list<br>Users@openlayers.org<br>http://openlayers.org/mailman/listinfo/users<br></blockquote><br>