[Geomoose-users] Identify Tolerance

Mon Oct 20 06:15:35 PDT 2014

I'm posting this final reply to ensure that it gets documented for others.

As an brief aside, this is a MapServer thing done for security purposes.

On Wed, Oct 15, 2014 at 11:30 AM, Clinton Olsen <clintono at emery.utah.gov> wrote:
> FINALLY! The last piece of the puzzle.  After you asked me that question I
> noticed that the ones working had <!-- MapServer Template --> on the front.
> I have added a polygon layer, a point layer, and a line layer with 100%
> success.  Thanks so much for all your suggestions and help with identifying.
>
> On Wed, Oct 15, 2014 at 9:26 AM, Dan Little <theduckylittle at gmail.com>
> wrote:
>>
>> Are you making sure to have
>> "<!-- MapServer Template -->"
>> at the top of your .html files?
>>
>> On Wed, Oct 15, 2014 at 10:24 AM, Clinton Olsen <clintono at emery.utah.gov>
>> wrote:
>> > Bob,
>> >
>> > I have tried to use the box option but it doesn't give a result either.
>> >
>> > Dan,
>> >
>> > I used the copy of the parcel point map book and I got one of the point
>> > layers to work.  However, when I tried to follow the same process on my
>> > other point layers that I needed to identify they will not work.  I am
>> > not
>> > getting any consistency with the new versions of Geomoose.  When I used
>> > 1.6
>> > it was little more work but it worked everytime.  I like how these new
>> > versions seem to be easier to understand and to add a layer.  But not
>> > all of
>> > my layers are working.  I have tried to put the layers in different
>> > projections, I have tried different extents.  The only thing I have
>> > ntoiced
>> > is that once I get a layer to identify, it will identify no matter what
>> > the
>> > extent is, or the projection I use.
>> >
>> > I have attached a layer I am trying to get to identify.  Just as a way
>> > to
>> > troubleshoot the problem, and if you are interested or have the time.
>> > You
>> > can place this in a testing map and see if it will identify.  I am not
>> > sure
>> > what else to do from here.   Thanks.
>> >
>> > On Thu, Oct 9, 2014 at 10:02 AM, Bistrais, Bob <Bob.Bistrais at maine.gov>
>> > wrote:
>> >>
>> >> If you haven't tried this already, try using the Box option with the
>> >> identify tool, see if you can at least Identify those layers with the
>> >> box
>> >> option.  At least that way you'll know if those layers can be
>> >> identified at
>> >> all.
>> >>
>> >> Also (and maybe I missed that part of the discussion) - have you
>> >> adjusted
>> >> the search tolerances?
>> >>
>> >> -----Original Message-----
>> >> From: geomoose-users-bounces at lists.osgeo.org
>> >> [mailto:geomoose-users-bounces at lists.osgeo.org] On Behalf Of Dan Little
>> >> Sent: Thursday, October 09, 2014 11:56 AM
>> >> To: Clinton Olsen
>> >> Cc: geomoose-users at lists.osgeo.org
>> >> Subject: Re: [Geomoose-users] Identify Tolerance
>> >>
>> >> You're going to hate me for this but mine seems to just be working.
>> >> I've attached a minimalistic example.  The points will all be in
>> >> Minnesota.
>> >>
>> >> Maybe try taking this and building off of it.  The shapefile is stored
>> >> in
>> >> UTM15N.
>> >>
>> >> On Thu, Oct 9, 2014 at 10:16 AM, Clinton Olsen
>> >> <clintono at emery.utah.gov>
>> >> wrote:
>> >> > I think my problem might be the projection.  I can see all my
>> >> > shapefiles when I am using geomoose and they are placed where they
>> >> > need to be.  I am using ESRI ARCMAP to reproject my shapefiles into
>> >> > the Web Mercator projection (3857).  In the shapefile .prj file it
>> >> > shows "PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere", in my
>> >> > mapfiles I
>> >> > have:
>> >> >
>> >> > WEB
>> >> > METADATA
>> >> > 'ows_title' 'Boulders'
>> >> > 'ows_srs' 'epsg:3857 epsg:900913 epsg:2281 epsg:3566'
>> >> > 'ows_enable_request' '*'
>> >> > 'ows_onlineresource' 'http://www.geomoose.org'
>> >> > END
>> >> > END
>> >> >
>> >> > PROJECTION
>> >> > 'init=epsg:3857'
>> >> > END
>> >> >
>> >> > In my mapbook I have: <param name="projection">EPSG:3857</param>
>> >> > and in my geomoose.html file I have: <script type="text/javascript"
>> >> > src="projections/EPSG3857.js"></script>.  Is there anything I am
>> >> > missing?
>> >> > What do other people use to reproject their shapefiles?
>> >> >
>> >> > On Wed, Oct 8, 2014 at 11:07 AM, Clinton Olsen
>> >> > <clintono at emery.utah.gov>
>> >> > wrote:
>> >> >>
>> >> >> Yes, I am still unable to successfully identify lines and points.  I
>> >> >> had to step away from it for a little bit for my head to clear.  And
>> >> >> I am willing to try any suggestions.
>> >> >>
>> >> >> On Wed, Oct 8, 2014 at 7:27 AM, Dan Little
>> >> >> <theduckylittle at gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Clinton, is this still a problem?
>> >> >>>
>> >> >>> On Fri, Sep 19, 2014 at 10:51 AM, Clinton Olsen
>> >> >>> <clintono at emery.utah.gov>
>> >> >>> wrote:
>> >> >>> > Sorry about that.  Try this one:
>> >> >>> >
>> >> >>> > You can look at my map at:
>> >> >>> > http://168.179.236.3/geomoose2/geomoose.html.
>> >> >>> >
>> >> >>> > On Fri, Sep 19, 2014 at 8:48 AM, Brent Fraser
>> >> >>> > <bfraser at geoanalytic.com>
>> >> >>> > wrote:
>> >> >>> >>
>> >> >>> >> Your site times out,
>> >> >>> >>
>> >> >>> >> Best Regards,
>> >> >>> >> Brent Fraser
>> >> >>> >>
>> >> >>> >> On 9/18/2014 4:15 PM, Clinton Olsen wrote:
>> >> >>> >>
>> >> >>> >> You can look at my map at:
>> >> >>> >> http://168.179.236.58/geomoose2/geomoose.html.
>> >> >>> >> The layer I am having trouble with is the boulder layer under
>> >> >>> >> the
>> >> >>> >> testing folder on the legend.  The only layers I have been able
>> >> >>> >> to get identify to work on is the parcel and NRCS layer.  I am
>> >> >>> >> trying to figure out how to identify points and line layers on
>> >> >>> >> the map before I create more maps.
>> >> >>> >>
>> >> >>> >> This is what I get when I try to identify the boulder layer,
>> >> >>> >> using the
>> >> >>> >> f12
>> >> >>> >> debug mode in chrome, with network traffic capturing enabled.
>> >> >>> >>
>> >> >>> >> Remote Address:
>> >> >>> >> 168.179.236.58:80
>> >> >>> >> Request URL:
>> >> >>> >> http://168.179.236.58/geomoose2/php/identify.php
>> >> >>> >> Request Method:
>> >> >>> >> POST
>> >> >>> >> Status Code:
>> >> >>> >> 200 OK
>> >> >>> >> Request Headersview source
>> >> >>> >>
>> >> >>> >> Accept:
>> >> >>> >> */*
>> >> >>> >> Accept-Encoding:
>> >> >>> >> gzip,deflate
>> >> >>> >> Accept-Language:
>> >> >>> >> en-US,en;q=0.8
>> >> >>> >> Connection:
>> >> >>> >> keep-alive
>> >> >>> >> Content-Length:
>> >> >>> >> 211
>> >> >>> >> Content-Type:
>> >> >>> >> application/x-www-form-urlencoded
>> >> >>> >> Host:
>> >> >>> >> 168.179.236.58
>> >> >>> >> Origin:
>> >> >>> >> http://168.179.236.58
>> >> >>> >> Referer:
>> >> >>> >> http://168.179.236.58/geomoose2/geomoose.html
>> >> >>> >> User-Agent:
>> >> >>> >> Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
>> >> >>> >> like
>> >> >>> >> Gecko)
>> >> >>> >> Chrome/37.0.2062.120 Safari/537.36
>> >> >>> >> X-Requested-With:
>> >> >>> >> XMLHttpRequest
>> >> >>> >>
>> >> >>> >> Form Dataview sourceview URL encoded
>> >> >>> >>
>> >> >>> >> layers:
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> blank%3Ablank/blank%3AEMERY_BOULDERS%3AEMERY_BOULDERS/EMERY_BOULD
>> >> >>> >> ERS%3Asketch
>> >> >>> >> projection:
>> >> >>> >> EPSG%3A3857
>> >> >>> >> shape:
>> >> >>> >> POINT%28-12374046.690745%204790938.2334565%29
>> >> >>> >> dojo.preventCache:
>> >> >>> >> 1411078405554
>> >> >>> >>
>> >> >>> >> Response Headersview source
>> >> >>> >>
>> >> >>> >> Connection:
>> >> >>> >> Keep-Alive
>> >> >>> >> Content-Type:
>> >> >>> >> application/xml
>> >> >>> >> Date:
>> >> >>> >> Thu, 18 Sep 2014 22:13:34 GMT
>> >> >>> >> Keep-Alive:
>> >> >>> >> timeout=5, max=100
>> >> >>> >> Server:
>> >> >>> >> Apache/2.2.22 (Win32)
>> >> >>> >> Transfer-Encoding:
>> >> >>> >> chunked
>> >> >>> >> X-Powered-By:
>> >> >>> >> PHP/5.4.3
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> Response Body -
>> >> >>> >> <results><script> GeoMOOSE.clearLayerParameters('highlight');
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> GeoMOOSE.turnLayerOff('highlight/highlight');</script><html><![CD
>> >> >>> >> ATA[<!--
>> >> >>> >> MapServer Template -->
>> >> >>> >> Detailed information for the area you clicked on the map...
>> >> >>> >> <table border="0">
>> >> >>> >> <tr>
>> >> >>> >> <td colspan="2"><b><u>Ground Coordinates</u></b> <br>
>> >> >>> >> <b>X: </b>-12374046.690745
>> >> >>> >> <br>
>> >> >>> >> <b>Y: </b>4790938.2334565</td>
>> >> >>> >> </tr>
>> >> >>> >> <tr>
>> >> >>> >> <td> </td>
>> >> >>> >> <td> </td>
>> >> >>> >> </tr>
>> >> >>> >> </table>
>> >> >>> >> <table border="0" cellpadding="1" cellspacing="2">
>> >> >>> >> ]]></html><footer><![CDATA[<b>Disclaimer: This information is
>> >> >>> >> being distributed as demonstation data only.  You should not use
>> >> >>> >> the data for any other purposes.</b> ]]></footer></results>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> On Mon, Sep 8, 2014 at 11:51 AM, Clinton Olsen
>> >> >>> >> <clintono at emery.utah.gov>
>> >> >>> >> wrote:
>> >> >>> >>>
>> >> >>> >>> You can look at my map at:
>> >> >>> >>> http://168.179.236.58/geomoose2/geomoose.html.  The layer I am
>> >> >>> >>> having trouble with is under the testing folder on the legend.
>> >> >>> >>> The only layers I have been able to get identify to work is the
>> >> >>> >>> parcel and NRCS layer.
>> >> >>> >>> I am
>> >> >>> >>> using the boulder layer on the map to try and get it working
>> >> >>> >>> before I move it to one of my other maps.  Let me know if you
>> >> >>> >>> want to look at anything else.
>> >> >>> >>>
>> >> >>> >>> This is what I get when I try to identify the boulder layer,
>> >> >>> >>> using the
>> >> >>> >>> f12 debug mode in IE, with network traffic capturing enabled.
>> >> >>> >>>
>> >> >>> >>> Request Body-
>> >> >>> >>>
>> >> >>> >>>
>> >> >>> >>>
>> >> >>> >>> layers=blank%253Ablank%2Fblank%253AEMERY_BORDER%253AEMERY_BORDER
>> >> >>> >>>
>> >> >>> >>> %2FEMERY_BORDER%253AEMERY_BOULDERS%253AEMERY_BOULDERS%2FEMERY_BO
>> >> >>> >>>
>> >> >>> >>> ULDERS%253Asketch&projection=EPSG%253A3857&shape=POINT%2528-1237
>> >> >>> >>>
>> >> >>> >>> 6561.885991%25204763185.2284383%2529&dojo.preventCache=141019688
>> >> >>> >>> 5123
>> >> >>> >>>
>> >> >>> >>> Response Body -
>> >> >>> >>> No data to view
>> >> >>> >>>
>> >> >>> >>> Clinton Olsen
>> >> >>> >>> EMERY COUNTY
>> >> >>> >>> IS/GIS Technician
>> >> >>> >>> 435-381-3592
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> --
>> >> >>> >> --
>> >> >>> >> *Please note my email address has changed to
>> >> >>> >> clintono at emery.utah.gov.
>> >> >>> >> Please update your records.  Thanks.
>> >> >>> >> --
>> >> >>> >> Clinton Olsen
>> >> >>> >> EMERY COUNTY
>> >> >>> >> IS/GIS Technician
>> >> >>> >> 435-381-3592
>> >> >>> >>
>> >> >>> >>
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > --
>> >> >>> > --
>> >> >>> > *Please note my email address has changed to
>> >> >>> > clintono at emery.utah.gov.
>> >> >>> > Please update your records.  Thanks.
>> >> >>> > --
>> >> >>> > Clinton Olsen
>> >> >>> > EMERY COUNTY
>> >> >>> > IS/GIS Technician
>> >> >>> > 435-381-3592
>> >> >>> >
>> >> >>> > _______________________________________________
>> >> >>> > Geomoose-users mailing list
>> >> >>> > Geomoose-users at lists.osgeo.org
>> >> >>> > http://lists.osgeo.org/mailman/listinfo/geomoose-users
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> --
>> >> >> Clinton Olsen
>> >> >> EMERY COUNTY
>> >> >> IS/GIS Technician
>> >> >> 435-381-3592
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > --
>> >> > Clinton Olsen
>> >> > EMERY COUNTY
>> >> > IS/GIS Technician
>> >> > 435-381-3592
>> >
>> >
>> >
>> >
>> > --
>> > --
>> > Clinton Olsen
>> > EMERY COUNTY
>> > IS/GIS Technician
>> > 435-381-3592
>
>
>
>
> --
> --
> Clinton Olsen
> EMERY COUNTY
> IS/GIS Technician
> 435-381-3592