<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman","serif";
color:black;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Yes, I also just attempted the geodesic:true setting both in main.js and compiled.js and it has no effect on the scale line. Was it not implemented in 2.8 perhaps? Well never mind; I just saw your followup indicating just that.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>On point 2, if no OL function currently exists to perform the necessary correction, might it be possible to crudely apply a correction factor somewhere in the GM code for the selection buffer? It won’t be accurate, but it will be substantially less inaccurate than the current state. Since mine appear to range from 0.89 to 0.86 (south to north) I might chose to use 0.875, which at worst results in a 2% deviation from the “true” value. Applied to the earlier example my 1-mile selection radius might then only be 0.98 miles (~100 feet to short), but this is far better than the current result of 0.86 miles.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Brent Fraser [mailto:bfraser@geoanalytic.com] <br><b>Sent:</b> Friday, December 17, 2010 10:01 AM<br><b>To:</b> Johan Forsman<br><b>Cc:</b> 'geomoose-users@lists.sourceforge.net'<br><b>Subject:</b> Re: [Geomoose-users] Scalebar & Measure<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Johan,<br><br> Interesting stuff.<br><br> Looking at my experimental source from a few months back, I had added a property to main.js around line 98:<br><br> if(CONFIGURATION.scale_line.enabled) {<br> Map.addControl(new OpenLayers.Control.ScaleLine({<br> bottomOutUnits: CONFIGURATION.scale_line.bottom_units,<br> topOutUnits: CONFIGURATION.scale_line.top_units,<br> geodesic: true, /* bfraser */<br> maxWidth: CONFIGURATION.scale_line.width<br> }));<br> }<br><br>but testing today it seems to have no effect in "correcting" the scalebar length. I'll have to do more investigation. Note from the OpenLayers doc:<o:p></o:p></p><h3>geodesic<o:p></o:p></h3><div><p>{Boolean} Use geodesic measurement. Default is false. The recommended setting for maps in EPSG:4326 is false, and true EPSG:900913. If set to true, the scale will be calculated based on the horizontal size of the pixel in the center of the map viewport.<o:p></o:p></p></div><p class=MsoNormal><br><br>Your point 2 is a tough one. The search radius is a map projection distance and would have to be corrected by the map projection point scale factor, or adjusted to be a geodesic distance. I don't know if OpenLayers has a function to do either of those. <br><br><br><o:p></o:p></p><pre>Best Regards,<o:p></o:p></pre><pre>Brent Fraser<o:p></o:p></pre><p class=MsoNormal><br>On 12/17/2010 8:04 AM, Johan Forsman wrote: <o:p></o:p></p><pre>All:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I just discovered this issue. After applying Brent's fix below the measure tool appears to return the correct values, but there are other remaining issues.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I am using the 900913 projection for all data.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>1. The scale bar is off. 500 meters on the scale bar measures to 431 meters, or a factor of ~0.86. This is not a critical issue, but it would be "nice" if it measured the same.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>2. The select feature, using By Point, is a very clever way to get all features within a certain radius of a point location. However this function will return a radius that is shorter by about the same amount as the scale bar. This is an important issue. I have attached 3 screenshots illustrating the problem. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The GM shot shows what is supposed to be a 1-mile radius, plus the new measurement (post-fix) to the most distant feature of interest.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The GE-EC shot shows the measured distance using an all-Google application.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The ArcGIS shot shows the actual size of a circle with an (presumably ArcGIS is authoritative) 1-mile radius in the same location. These data are in NAD83 UTM 15N.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I measured the scale factors on a 200 meter scale bar (1:6771) for my state (Louisiana) and found them to be about 0.86 at the northern extreme and 0.89 at the southern extreme.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Is there any way I can implement some type of automatic correction to the select tool, and any other tool that may be affected by this behavior? Certainly I can inform the users that they need to add x % to their chosen buffer, but I am not prepared to trust the users to really do that.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thanks!<o:p></o:p></pre><pre>/Johan.<o:p></o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original Message-----<o:p></o:p></pre><pre>From: Brent Fraser [<a href="mailto:bfraser@geoanalytic.com">mailto:bfraser@geoanalytic.com</a>]<o:p></o:p></pre><pre>Sent: Wednesday, May 26, 2010 1:53 PM<o:p></o:p></pre><pre>To: Len Kne<o:p></o:p></pre><pre>Cc: '<a href="mailto:geomoose-users@lists.sourceforge.net">geomoose-users@lists.sourceforge.net</a>'<o:p></o:p></pre><pre>Subject: Re: [Geomoose-users] Scalebar & Measure<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Len(and others interested in measuring),<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> Here's my solution to the measure problem:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>In main.js somewhere around line 138 add the two lines below marked with a<o:p></o:p></pre><pre>"//BWF":<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> Tools['measure'] = new<o:p></o:p></pre><pre>OpenLayers.Control.GeoMooseMeasure(OpenLayers.Handler.MeasurePath,<o:p></o:p></pre><pre>measureToolOptions);<o:p></o:p></pre><pre> Tools['measure'].geodesic = true; //BWF<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> Tools['measurearea'] = new<o:p></o:p></pre><pre>OpenLayers.Control.GeoMooseMeasure(OpenLayers.Handler.MeasurePolygon,<o:p></o:p></pre><pre>measureToolOptions);<o:p></o:p></pre><pre> Tools['measurearea'].geodesic = true; //BWF<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thoughts?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Brent<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Brent Fraser wrote:<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Paul, Len,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> Our scale problem is a (mostly) map projection issue. All map<o:p></o:p></pre></blockquote><pre>projections<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>introduce distortions in trying to represent a round(ish) Earth on a<o:p></o:p></pre></blockquote><pre>flat plane.<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre> Mercator is no different: it is like wrapping an up-right cylinder<o:p></o:p></pre></blockquote><pre>around the<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Earth, projecting light from the center onto the cylinder<o:p></o:p></pre><pre>(<a href="http://en.wikipedia.org/wiki/Mercator_projection">http://en.wikipedia.org/wiki/Mercator_projection</a>). As you can imagine<o:p></o:p></pre></blockquote><pre>the<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>distortions get "worse" the further from the equator. The distortions<o:p></o:p></pre></blockquote><pre>can be<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>modeled as a Point Scale Factor. At the equator the Point Scale Factor<o:p></o:p></pre></blockquote><pre>is 1.0,<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>at latitude 60 degrees North (or South), the scale factor is 0.5!<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> So what's the solution? Here's mine:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> 1. Enhance Proj4 (and Proj4js) to return the Point Scale factor<o:p></o:p></pre></blockquote><pre>(given the<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>projection and a location)<o:p></o:p></pre><pre> 2. Enhance MapServer and Openlayers to use the Point Scale Factor in<o:p></o:p></pre><pre>calculating distances and scale.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I'm trying to drum up interest, but so no takers....<o:p></o:p></pre><pre> <a href="http://osgeo-org.1803224.n2.nabble.com/Point-Scale-factor-service">http://osgeo-org.1803224.n2.nabble.com/Point-Scale-factor-service</a>-<o:p></o:p></pre></blockquote><pre>td4938743.html<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre><a href="http://osgeo-org.1803224.n2.nabble.com/Re-3265-Scale-dependent-layer">http://osgeo-org.1803224.n2.nabble.com/Re-3265-Scale-dependent-layer</a>-<o:p></o:p></pre></blockquote><pre>switching-error-with-Mercator-td4966902.html<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre>Best Regards,<o:p></o:p></pre><pre>Brent Fraser<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Len Kne wrote:<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>The scale bar issue with the web Mercator projection is a limitation of<o:p></o:p></pre><pre>OpenLayers, the application GeoMOOSE 2.x uses to render the map frame.<o:p></o:p></pre><pre> There has been discussion on the OpenLayers site about providing a<o:p></o:p></pre><pre>patch (this link offers a patch <a href="http://trac.openlayers.org/ticket/1890">http://trac.openlayers.org/ticket/1890</a><o:p></o:p></pre></blockquote></blockquote><pre>)<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>in the next version 2.9. I'm sure GM will upgrade to OL 2.9, but not<o:p></o:p></pre><pre>sure there is any schedule in place to do this.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>The cursor issue is also kind of fun because it seems each browser<o:p></o:p></pre><pre>handles the custom icons differently. Here's the attribute in the<o:p></o:p></pre><pre>mapbook which defines the query for the Identify service:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>cursor="url('cursors/identify2.cur') 9<o:p></o:p></pre></blockquote></blockquote><pre>9,url('cursors/identify2.cur'),auto"<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>This makes three attempts to draw the cursor, the first offsets the<o:p></o:p></pre><pre>mouse click 9 pixels from the top and the left. Firefox can use this<o:p></o:p></pre><pre>value and seems to line the mouse click up pretty good with the<o:p></o:p></pre><pre>crosshair. However, IE cannot handle the offset adjustment, so it<o:p></o:p></pre></blockquote></blockquote><pre>reads<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>the second cursor definition. There are tools like AT File Mole which<o:p></o:p></pre><pre>can be used to edit the hotspot of a cursor. Attached is the latest<o:p></o:p></pre><pre>version I have been using for Identify service, again this seems to<o:p></o:p></pre></blockquote></blockquote><pre>line<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>the crosshair up pretty well with the mouse click. If you are using<o:p></o:p></pre><pre>Safari or Chrome, these setting don't seem to work at all and I would<o:p></o:p></pre><pre>recommend not using customer cursors with those browsers.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Len<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>*From:* Wirth, Paul [<a href="mailto:Paul.Wirth@kniferiver.com">mailto:Paul.Wirth@kniferiver.com</a>]<o:p></o:p></pre><pre>*Sent:* Saturday, May 01, 2010 9:03 PM<o:p></o:p></pre><pre>*To:* '<a href="mailto:geomoose-users@lists.sourceforge.net">geomoose-users@lists.sourceforge.net</a>'<o:p></o:p></pre><pre>*Subject:* [Geomoose-users] Scalebar & Measure<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Two questions:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>1. I have a web Mercator application, and I noticed that the<o:p></o:p></pre><pre>scalebar does not display the correct distance. For instance, when the<o:p></o:p></pre><pre>scalebar shows a distance of 20 miles, it measures only 13.8 miles. I<o:p></o:p></pre><pre>know the measure tools are working correctly, so I assume this is a<o:p></o:p></pre><pre>scalebar issue. Any thoughts on how to fix this?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>2. I think this question was asked before, but I can't seem to<o:p></o:p></pre><pre>find it on the e-mail list. With the measure tools, the cursor does<o:p></o:p></pre></blockquote></blockquote><pre>not<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>start measuring at the "crosshairs" when the user clicks, but rather in<o:p></o:p></pre><pre>the NW quadrant of the crosshairs. Is there a way to change it so the<o:p></o:p></pre><pre>measure start point will be on the crosshairs?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>-----------------------------------------------------------------------<o:p></o:p></pre></blockquote></blockquote><pre>-<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre>-----------------------------------------------------------------------<o:p></o:p></pre></blockquote></blockquote><pre>-------<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>-----------------------------------------------------------------------<o:p></o:p></pre></blockquote></blockquote><pre>-<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>Geomoose-users mailing list<o:p></o:p></pre><pre><a href="mailto:Geomoose-users@lists.sourceforge.net">Geomoose-users@lists.sourceforge.net</a><o:p></o:p></pre><pre><a href="https://lists.sourceforge.net/lists/listinfo/geomoose-users">https://lists.sourceforge.net/lists/listinfo/geomoose-users</a><o:p></o:p></pre></blockquote><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>------------------------------------------------------------------------<o:p></o:p></pre></blockquote><pre>------<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>_______________________________________________<o:p></o:p></pre><pre>Geomoose-users mailing list<o:p></o:p></pre><pre><a href="mailto:Geomoose-users@lists.sourceforge.net">Geomoose-users@lists.sourceforge.net</a><o:p></o:p></pre><pre><a href="https://lists.sourceforge.net/lists/listinfo/geomoose-users">https://lists.sourceforge.net/lists/listinfo/geomoose-users</a><o:p></o:p></pre><pre><o:p> </o:p></pre></blockquote><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>--------------------------------------------------------------------------<o:p></o:p></pre><pre>----<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>Geomoose-users mailing list<o:p></o:p></pre><pre><a href="mailto:Geomoose-users@lists.sourceforge.net">Geomoose-users@lists.sourceforge.net</a><o:p></o:p></pre><pre><a href="https://lists.sourceforge.net/lists/listinfo/geomoose-users">https://lists.sourceforge.net/lists/listinfo/geomoose-users</a><o:p></o:p></pre></blockquote></div></div></body></html>