[Geomoose-users] Problem in query.php if layer SRS different from map SRS
TC Haddad
tchaddad at gmail.com
Mon Jul 27 11:27:18 PDT 2015
This is drifting into other topics now, but I notice that there are other
data sets already packages with the demo, that are not currently being used
in the interface. e.g. "feedlots", "fire stations", and "pipeline_not_real"
Would any of those be appropriate for these tests?
On Mon, Jul 27, 2015 at 11:06 AM, Brent Fraser <bfraser at geoanalytic.com>
wrote:
> Wait a minute. If the parcel data is in UTM then we are already testing
> the multiple SRS case. Must be the magnitude of the lat/lon coordinates
> causing the problem in queryByRect (and the precision in the search
> template.)
>
> Best Regards,
> Brent Fraser
>
> On 7/27/2015 11:42 AM, Basques, Bob (CI-StPaul) wrote:
>
> All,
>
> Should we use the same data in both projections, or two different
> datasets? I would need to search around for another dataset complete with
> attributes for searching on.
>
> I think it would be better to have an entirely separate dataset with
> another projection as an example.
>
> The current Parcel dataset is already vetted for redistribution, and
> adding more data to it may take a bit to get going. Another chunk of data
> alongside of it would be nice, use a different color, different projection
> for sourcing, etc.
>
> bobb
>
>
>
> On Jul 27, 2015, at 12:38 PM, Brent Fraser <bfraser at geoanalytic.com>
> wrote:
>
> Bobb,
>
> Yes! Change the parcel data to EPSG:4326 and test the rendering,
> Identify, Select Features, Search Parcels, Printing, and Feature Report
> functions (that would likely decrease my support workload by 80%).
>
> Best Regards,
> Brent Fraser
>
> On 7/27/2015 8:17 AM, Basques, Bob (CI-StPaul) wrote:
>
> All,
>
> I wonder if it wouldn’t be prudent to include data from more than one
> projection in order to insure that all reprojection conversions are
> working.
>
> bobb
>
>
>
> On Jul 26, 2015, at 12:37 PM, TC Haddad <tchaddad at gmail.com> wrote:
>
>
> Just as an overall comment, there are 2 very distinct user groups for the
> demo - people who only care about Web Mercator stuff working, and people
> who are trying to work in a local projection.
>
> What we have in the demo is working pretty well for the first group, and
> it is a bit unfriendly to beginners in the second group, as projections
> show up in multiple places where beginners are likely to run into trouble
> (e.g. even setting up your zoom levels in the Mapbook.xml). It's compounded
> if a user runs into a bug, and doesn't know it's a bug.
>
> Probably worth a review of the docs to see how we might improve in this
> area...
>
> Tanya
>
> On Sun, Jul 26, 2015 at 10:12 AM, Brent Fraser <bfraser at geoanalytic.com>
> wrote:
>
>> Tanya,
>>
>> Just by looking at the code in Github I see that there is still no
>> re-projection of the extent before the query call, so i expect that is is
>> still broken (but I will try v2.8). Now that I'm getting results back I
>> ran into the "zoom to results" bug you've referenced, so that saved me some
>> time. Thanks!
>>
>> Personally, I think the parcel data in our demo should be in EPSG:4326 so
>> we can discover these problems in our testing before release.
>>
>> Best Regards,
>> Brent Fraser
>>
>> On 7/26/2015 10:57 AM, TC Haddad wrote:
>>
>>
>> There was a bug that was fixed recently that may relate:
>>
>> <https://github.com/geomoose/geomoose/issues/90>
>> https://github.com/geomoose/geomoose/issues/90
>>
>> You could try grabbing the relevant changes to query.php:
>>
>>
>> <https://github.com/geomoose/geomoose-services/commit/dacfa7e2648c5bcd3ec38308cb1199621a07c390>
>> https://github.com/geomoose/geomoose-services/commit/dacfa7e2648c5bcd3ec38308cb1199621a07c390
>>
>> Or you could try a 2.8 install to see if the same problem is present
>> (before filing a new issue...).
>>
>>
>>
>> On Sun, Jul 26, 2015 at 9:32 AM, Brent Fraser < <bfraser at geoanalytic.com>
>> bfraser at geoanalytic.com> wrote:
>>
>>> Hi Developers (and others),
>>>
>>> While debugging a user's problem with using his data with query.php, I
>>> see that line 376 in github (or line 420-ish in GM 2.7.1):
>>>
>>> $ext = $queryLayer->getExtent();
>>>
>>> then the layer's extent is used for the query a little later:
>>>
>>> $queryLayer->queryByRect($ext);
>>>
>>> This fails to find any features since in my case the coordinate systems
>>> of the map and layer are different, and the queryByrect must be done using
>>> a rectangle in the MAP's SRS not the LAYER's SRS. I did a little hack to
>>> re-project the extent just before the queryByRect:
>>>
>>> // re-project the layer's extent into the map SRS
>>> for querying:
>>> $map_projection_def = $map->getProjection();
>>> $map_projection_obj =
>>> ms_newProjectionObj($map_projection_def);
>>>
>>> if($queryLayer->getProjection() != NULL) {
>>> $projection = $queryLayer->getProjection();
>>> }
>>> if($projection != NULL) {
>>> # reproject the query shape as available.
>>> $projection = ms_newProjectionObj($projection);
>>> }
>>> if($projection) {
>>> $ext->project($projection, $map_projection_obj);
>>> }
>>> if($DEBUG) {
>>> error_log(implode(',',
>>> array($ext->minx,$ext->miny,$ext->maxx,$ext->maxy)));
>>> error_log("<br/>extent for query in map
>>> SRS.<br/>");
>>> }
>>>
>>> I thought I would get comments before filing an Issue.
>>>
>>> So any comments?
>>>
>>>
>>> --
>>> Best Regards,
>>> Brent Fraser
>>>
>>>
>>> _______________________________________________
>>> Geomoose-users mailing list
>>> <Geomoose-users at lists.osgeo.org>Geomoose-users at lists.osgeo.org
>>> <http://lists.osgeo.org/mailman/listinfo/geomoose-users>
>>> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>>>
>>
>>
>>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
>
>
>
>
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20150727/2f08e7e9/attachment-0001.html>
More information about the Geomoose-users
mailing list