[Chameleon-dev] [Bug 1222] New: Query widget hilite raster fatal error

bugzilla-daemon at bugzilla.maptools.org bugzilla-daemon at bugzilla.maptools.org
Tue Dec 20 12:58:49 EST 2005


http://bugzilla.maptools.org/show_bug.cgi?id=1222

           Summary: Query widget hilite raster fatal error
           Product: Chameleon
           Version: 2.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
        AssignedTo: chameleon-dev at lists.maptools.org
        ReportedBy: mcgrawj at agr.gc.ca


The emails leading up to the filing of this bug and solution. First my original 
post, followed by Paul Spencer's response:

On 24-Nov-05, at 5:04 PM, McGraw, Joanne wrote:
> I have a map file that contains a raster, a couple polygon layers  
> and a point layer. All are queryable and with the Query widget I  
> can easily get the attributes for the raster, the polygons and the  
> points near where I click.
>
> The problem occurs when I then try to use the querymap to hilite  
> the respective elements and turn the Query widget's  
> "highlighresults" attribute to true. No image is created and I  
> receive the following errors at the " $oImage = $oMapSession->oMap- 
> >drawQuery();" line in 'drawmap.php':
>
> Warning: [MapServer Error]: msDrawShape(): Unknown layer type. in C: 
> \ms4w\apps\htdocs\php_test.php on line 27
> Fatal error: Call to a member function on a non-object in C:\ms4w 
> \apps\htdocs\php_test.php on line 28
>
> If I turn the querying capabilities on the raster off, the hiliting  
> of the polygon and point layers works fine. So, the problem appears  
> to be that Mapserver is, for some reason, trying to create a hilite  
> shape for the raster.
>
> Now, I want to be able to query the raster values, but do not  
> require (or even expect) anything to be hilited for it. Mapserver,  
> really, should just ignore those for that process and continue with  
> the rest of the layers.
>
> Has anyone else come up against this? And, gotten around it  
> somehow? I don't really want to make changes to the "drawmap.php"  
> which could be lost with deployment of an upgrade. The only other  
> thing I can think of is to extend the Query object and create a new  
> hidden variable that lists all the queryable layers and overrides  
> the QueryWMouseClick function, passing a list of gszQueryLayers  
> that doesn't include the raster layer to the drawmap.php call. If  
> that's my best option, that's okay but I thought I'd see if anyone  
> else had dealt with this in some other way first.
> Cheers,
> jtm


Joanne,
if you can find a solution to this, please file it as a bug and we  
will incorporate it into the 2.4 release that should happen around  
Christmas.  If you think a change to drawmap.php is required, please  
make the change there.  If you think another solution is more  
generic, that would be find too.
Cheers
Paul



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


Please do NOT reply to this email, use the link above instead to 
login to bugzilla and submit your comment. Any email reply to this
address will be lost.


More information about the Chameleon-dev mailing list