<div dir="ltr"><div><br></div>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"<br><br>Would any of those be appropriate for these tests?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 27, 2015 at 11:06 AM, Brent Fraser <span dir="ltr"><<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
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.)<br>
<pre cols="72">Best Regards,
Brent Fraser</pre><span class="">
<div>On 7/27/2015 11:42 AM, Basques, Bob
(CI-StPaul) wrote:<br>
</div>
</span><blockquote type="cite">
All,
<div><br>
</div>
<div><span class="">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.
<div><br>
</div>
<div>I think it would be better to have an entirely
separate dataset with another projection as an example.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>bobb</div>
<div><br>
</div>
<div><br>
</div>
</span><div><br>
<div>
<blockquote type="cite"><span class="">
<div>On Jul 27, 2015, at 12:38 PM, Brent Fraser
<<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>>
wrote:</div>
<br>
</span><div>
<div bgcolor="#FFFFFF" text="#000000"><span class="">Bobb,<br>
<br>
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%).<br>
<pre cols="72">Best Regards,
Brent Fraser</pre>
<div>On 7/27/2015 8:17 AM,
Basques, Bob (CI-StPaul) wrote:<br>
</div>
</span><blockquote type="cite">
All,
<div><br>
</div>
<div><span class="">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.
<div><br>
</div>
<div>bobb</div>
<div><br>
</div>
<div><br>
</div>
</span><div><br>
<div>
<blockquote type="cite"><span class="">
<div>On Jul 26, 2015, at 12:37 PM,
TC Haddad <<a href="mailto:tchaddad@gmail.com" target="_blank">tchaddad@gmail.com</a>>
wrote:</div>
<br>
</span><div><span class="">
<div dir="ltr">
<div>
<div>
<div>
<div><br>
</div>
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.<br>
<br>
</div>
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.<br>
<br>
</div>
Probably worth a review of the docs to
see how we might improve in this
area...<br>
<br>
</div>
Tanya<br>
</div>
</span><div class="gmail_extra"><br>
<div class="gmail_quote"><span class="">On Sun, Jul 26,
2015 at 10:12 AM, Brent Fraser <span dir="ltr">
<<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>></span>
wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">Tanya,<br>
<br>
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!<br>
<br>
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.<br>
<pre cols="72">Best Regards,
Brent Fraser</pre>
</span><div>
<div><span class="">
<div>On 7/26/2015
10:57 AM, TC Haddad wrote:<br>
</div>
</span><blockquote type="cite">
<div dir="ltr">
<div>
<div><span class="">
<div><br>
</div>
There was a bug that
was fixed recently
that may relate:<br>
<br>
</span><a href="https://github.com/geomoose/geomoose/issues/90" target="_blank"></a><a href="https://github.com/geomoose/geomoose/issues/90" target="_blank">https://github.com/geomoose/geomoose/issues/90</a><br>
<br>
</div><span class="">
You could try grabbing
the relevant changes to
query.php:<br>
<br>
</span><a href="https://github.com/geomoose/geomoose-services/commit/dacfa7e2648c5bcd3ec38308cb1199621a07c390" target="_blank"></a><a href="https://github.com/geomoose/geomoose-services/commit/dacfa7e2648c5bcd3ec38308cb1199621a07c390" target="_blank">https://github.com/geomoose/geomoose-services/commit/dacfa7e2648c5bcd3ec38308cb1199621a07c390</a><br>
<br>
</div><span class="">
Or you could try a 2.8
install to see if the same
problem is present (before
filing a new issue...).<br>
<br>
<br>
</span></div>
<div class="gmail_extra"><br>
<div class="gmail_quote"><div><div class="h5">On
Sun, Jul 26, 2015 at
9:32 AM, Brent Fraser <span dir="ltr">
<<a href="mailto:bfraser@geoanalytic.com" target="_blank"></a><a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>></span>
wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hi Developers (and
others),<br>
<br>
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):<br>
<br>
$ext =
$queryLayer->getExtent();<br>
<br>
then the layer's
extent is used for the
query a little later:<br>
<br>
$queryLayer->queryByRect($ext);<br>
<br>
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:<br>
<br>
//
re-project the layer's
extent into the map
SRS for querying:<br>
$map_projection_def =
$map->getProjection();<br>
$map_projection_obj =
ms_newProjectionObj($map_projection_def);<br>
<br>
if($queryLayer->getProjection()
!= NULL) {<br>
$projection =
$queryLayer->getProjection();<br>
}<br>
if($projection !=
NULL) {<br>
# reproject the
query shape as
available.<br>
$projection =
ms_newProjectionObj($projection);<br>
}<br>
if($projection) {<br>
$ext->project($projection,
$map_projection_obj);<br>
}<br>
if($DEBUG) {<br>
error_log(implode(',',
array($ext->minx,$ext->miny,$ext->maxx,$ext->maxy)));<br>
error_log("<br/>extent
for query in map
SRS.<br/>");<br>
}<br>
<br>
I thought I would get
comments before filing
an Issue.<br>
<br>
So any comments?</div></div><span><font color="#888888"><div><div class="h5"><br>
<br>
-- <br>
Best Regards,<br>
Brent Fraser<br>
<br>
<br>
_______________________________________________<br>
Geomoose-users
mailing list<br>
</div></div><a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank"></a><a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank"></a><a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
</font></span></blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div><span class="">
_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br></blockquote></div><br></div>