[Geomoose-users] getProjection error - select.php

[TC Haddad]

Oh - but I guess an additional question is: is this really a Mapserver
problem?

It seems like GeoMoose should be passing the LAYER name to Mapserver, not
the GROUP name. That would solve the problem....

Your workaround is a good temp solution too, just more difficult to
maintain.


On Mon, Jun 10, 2013 at 11:46 AM, TC Haddad <tchaddad at gmail.com> wrote:

> Yes -I was able to test and confirm that if I explode my GROUP back into
> individual layers everything works again, so that is the temporary solution
> to the problem.
>
> Tanya
>
>
> On Mon, Jun 10, 2013 at 7:16 AM, Bistrais, Bob <Bob.Bistrais at maine.gov>wrote:
>
>>  I think that’s a likely culprit (the Group issue).  AFAIK, that is not
>> resolved, but I’m still on MapServer 6.0.2.  It would be worth checking
>> with the experts on the MapServer project.****
>>
>> ** **
>>
>> Bob from Maine****
>>
>> ** **
>>
>> *From:* geomoose-users-bounces at lists.osgeo.org [mailto:
>> geomoose-users-bounces at lists.osgeo.org] *On Behalf Of *TC Haddad
>> *Sent:* Friday, June 07, 2013 6:34 PM
>> *To:* geomoose-users at lists.osgeo.org
>> *Subject:* [Geomoose-users] getProjection error - select.php****
>>
>> ** **
>>
>> ** **
>>
>> I've crashed into the same issue that Bob (from Maine) posted about on
>> the Mapserver list last September:
>>
>>
>> http://lists.osgeo.org/pipermail/mapserver-users/2012-September/073223.html
>> ****
>>
>> I was wondering if it ever got solved?
>>
>> ++++++****
>>
>> In my version of events, I can say that the layer being queried seemed to
>> work fine as an individual layer (yesterday), but as soon as it was
>> combined in a GROUP with other related layers, this 500 server error occurs:
>> ****
>>
>> Call to a member function getProjection() on a non-object in \htdocs\php\select.php on line 215****
>>
>> This is happening with the buffered_select tool in GM 2.6.1. All layers
>> in the group have the same projection defined in their LAYER descriptions..
>> ****
>>
>> Maybe the flaw is that GM looks for the GROUP name and not for the LAYER
>> name when it looks for the projection? and a GROUP does not (cannot?) have
>> a projection definition?****
>>
>> ** **
>>
>> Tanya ****
>>
>> ** **
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20130610/4dbf6ce6/attachment.html>