Hi list,
I tried pmapper 3.2-beta2 with ms4w 2.26, mapserver 5.0, and had a few
problems with database connectivity. I use an XY layer which connects to
a MSSQL database using the PEAR module (1.3.2 stable with MDB2 2.4.1
stable and MDB2_Driver_mssql 1.2.1 stable).
- When I use MDB2 I can't use ODBC, it is not supported in the
package
- When I define the layer as mssql layer ( "XYLAYER_PROPERTIES"
"mssql://@myserver/mydatabase||[EMAIL PROTECTED]>0||X,Y,0") I can retrieve a
visible layer. Fine so far. But the identify tool does not work unless I
switch to the "good old" DB package (1.7.13 stable) in squery.php
(function dumpXYQueryResults()) instead of MDB2.
- Mssql driver only works if my laptop is connected to the
network, if I try to connect to my local mssql database when laptop is
standalone, no connection is possible, so ODBC is better for external
demo's
- There is a incomplete call in query.php line 730: $this->map
must be included.
//echo $this->qStr;
//$this->query = new XYQuery($this->qLayer,
$this->glayer, $this->qStr, 1, $this->zoomFull);
$this->query = new XYQuery($this->map,$this->qLayer,
$this->glayer, $this->qStr, 1, $this->zoomFull);
- There are problems with checking and setting the SESSION() in
initgroups.php at line 172. If you use XY layers this variable should
always be set to 1.
// Set in sessionid that XYLayer exists
$_SESSION["existsXYLayer"] = 1;
} else {
$_SESSION["existsXYLayer"] = 0;
}
- In map.php there is no check on layer scale for XY layers:
the next line should be included in line 883
if
(checkScale($this->map,$mLayer,$this->map->scale)){
- Even if all these problems are fixed the identify tool works
only on XY layers if they are switched on, It does not work on shp or
ogr point layers anymore. If I switch off XY Layers in the layer panel,
identify works fine on all other shp and ogr layers. I don't know why,
anyone can help me on this one?
My questions: It looks like XY layers are not used very much anymore,
which is a pity because it is very fast on display and querying. Also:
XY layers make it possible to use filters (e.g Country = "The
Netherlands") without using a database view. I suggest that it should be
clear if this functionality is maintained and tested or not. If it is
maintained I would be very pleased.
Of course there is an alternative (by using OGRVRTLayer, PointFromColums
geometry field), but this has some disadvantages. This is slower, and
besides the speed, it is necessary to use a unique identifier (FID),
this is not always possible if a view or a filter is used. And is
necessary to create the view inside the database, instead of defining it
in the definition of SrcLayer (as a sql statement, like select * from
mytabe where X>0) outside the database
Is there anyone who can give me some useful hints?
Thanks
Andre van Atten
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
pmapper-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pmapper-users
