<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi<div class=""><br class=""></div><div class="">Just to echo what Régis is saying Calvin, as the original author of the coordinate capture plugin shipped with QGIS, your changes would probably be quite simple to add to the core plugin. I am actually planning to merge the coordinate capture tool into the status bar coordinates widget in QGIS 3.0 so it would be good to get your suggestions so that we actually don’t need to have a bunch of different plugins for this.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 10 Jun 2016, at 10:18, Régis Haubourg <<a href="mailto:regis.haubourg@gmail.com" class="">regis.haubourg@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi Calvin, <div class="">you made a great comparing existing tools for coordinate handling. I was annoyed too with that mess. Could you make a feature request in <a href="http://hub.qgis.org/" class="">hub.qgis.org</a> asking for more rational in core QGIS ? I imagine that we could just have some tweaking of current coordinate widget so that it can have different formatting options, and have all addintional tools being merged to only one, handling all use cases. making one more plugin is the right short term option to meet your actual need (plugins are great for that). Toavoiding too much efforts in maitaining those plugins, and also avoid plugin clutering, a feature request is the right thing to do :)</div><div class="">Cheers</div><div class="">Régis</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2016-06-09 21:48 GMT+02:00 C Hamilton <span dir="ltr" class=""><<a href="mailto:adenaculture@gmail.com" target="_blank" class="">adenaculture@gmail.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">I just uploaded my
latlontools plugin to the QGIS plugin site. I know it is going to need some
explanation as it duplicates some existing functionality, but it was born out
of frustration with the existing plugins. Let me clarify that I am not saying
there is anything wrong with how these plugins work. They may be perfectly
suited for the needs of their users, but my work flow was such that they did
not satisfy my needs and even the time I spent in writing the plugin was well
worth the time I saved later with my work flow. LatLonTools is designed to work
in conjunction with Google Maps and other on-line mapping.</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">The plugins that
LatLonTools has the most similarity with are Coordinate Capture, Copy_Coords,
and ZoomToCoordinates, and Zoom to Point.</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">The reason I wrote
LatLonTools was because I was looking at archaeological sites in Lidar hill
shade and was comparing what I was viewing in QGIS with imagery in Google Map,
Google Earth, and some other mapping tools. I was also working with coordinates
in Wikipedia. All of these represent coordinates as geographic latitude and
longitudes either in decimal or DMS notation. They all specify latitude
followed by longitude usually with a comma separator. LatLonTools uses latitude
and longitude coordinates no matter what the CRS of the QGIS project is - hence
the name LatLonTools. It was also important to be able to copy the coordinates
verbatim usually in the format "latitude, longitude" with slight
variations and paste them into my plugin in one text field (not two) and zoom
to that point. Conversely I wanted a single click in QGIS to copy a coordinate
that I could paste in Google Maps or Google Earth and zoom to that point. For
my use this is the problem with the existing plugins:</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">Zoom to Point: </div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">1. Does not support
DMS coordinates.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">2. Has separate text
fields for entering coordinates.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">3. Requires
coordinates in the CRS of the QGIS project and this may not be in degrees.</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">Zoom to Coordinates</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">1. Does not support
DMS coordinates.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">2. Has separate text
fields for entering coordinates.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">3. Requires
coordinates in the CRS of the QGIS project and this may not be in degrees.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">4. Not dockable. </div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">Coordinate Capture</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">Although I have
listed this one, it really doesn't compare to LatLonTools because LatLonTools
only captures to the clipboard so I am going to rule it out as a similar
plugin. </div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">1. Does not support
DMS notation.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">2. Can capture the
coordinate to the clipboard but it is in the format of<span class=""> </span>"Longitude, Latitude, Native CRS X,
Native CRS Y" and is not suitable to paste into Google Earth.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">3. Even if you could
click on the Capture button to get the right coordinate you still have an extra
click. With LatLonTools you only need to click on the map and the coordinate is
captured to the clipboard in the right format for Google Earth.</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">Copy_Coords</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">1. Copies the
coordinate in the format of "Longitude, Latitude" or in the native
CRS of "X, Y". This is not suitable to paste into Google Earth.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">2. Does not support
DMS notation.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">3. Does not give any
indication to the user that the coordinate was captured.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">4. If the CRS is
anything other than 4326 the output will not be in degrees.</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">The major difference
with LatLonTools is that it assumes degrees as input and output no matter what
the project CRS is and it formats them in the order of on-line maps. Here is
what LatLonTools offers:</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">1. Has a single
string input of "Latitude, Longitude". Actually, the delimiter can be
one or more comma, space, tab, semicolon, or colon. Note that with a tab you
can paste the coordinates into a spread sheet in adjacent columns.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">2. Supports DMS on
input and output.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">3. Single click
coordinate capture in the proper format for on-line maps.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">4. Displays the
coordinate in the lower left as the mouse moves over the map.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">5. In settings you
can configure the capture format as decimal degrees, DMS, DDMMSS or even the
Native CRS, but will be in the order Y,X or Latitude, Longitude.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">6. In settings you
can specify the delimiter between the two coordinates as a comma, tab, space or
anything you want.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">7. Two tools in one
plugin.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">8. I may add an
additional capability to paste in a block of coordinates that create a list to
click on and view.</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">9. Input is in a
dockable window which I prefer to a popup window.</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">For anyone who uses
QGIS in conjunction with Google Earth, Google Maps or the like are really going
to appreciate LatLonTools. </div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">My goal was not to
duplicate the work flow of the similar plugins, but to optimize my work flow,
but there are several easy modifications that I could make in the
"Settings" so that it could operate in the same manner as 3 of the
plugins. I would only do this if the community wanted it, because I would never
work with coordinates the way they do. LatLonTools will only have a single
string as input so if the other plugins want two input text boxes then there is
no overlap. In the "Settings" it would be easy to support coordinates
is in the order of "X, Y" like the other plugins for those who need
that ordering. And in the settings I could also provide an option for Native
CRS input if others were interested.</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">I know this has been
an incredibly long e-mail, but wanted to lay out the reasons for this plugin and am requesting that you consider adding it to the plugin repository.
The plugin will likely expand with a bulk zoom to point feature.</div><p style="margin:0in;font-family:Calibri;font-size:11pt" class=""> </p><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">Thanks,</div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class=""><br class=""></div><div style="margin: 0in; font-family: Calibri; font-size: 11pt;" class="">Calvin<br class=""></div>
</div>
<br class="">_______________________________________________<br class="">
Qgis-developer mailing list<br class="">
<a href="mailto:Qgis-developer@lists.osgeo.org" class="">Qgis-developer@lists.osgeo.org</a><br class="">
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br class="">
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br class=""></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature">Régis Haubourg<br class=""><br class="">Attention, changement d'adresse mail! <br class="">Mon adresse principale devient désormais regis.haubourg at <a href="http://gmail.com/" target="_blank" class="">gmail.com</a><br class=""><br class=""></div>
</div>
_______________________________________________<br class="">Qgis-developer mailing list<br class=""><a href="mailto:Qgis-developer@lists.osgeo.org" class="">Qgis-developer@lists.osgeo.org</a><br class="">List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer<br class="">Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer</div></blockquote></div><br class=""><div class="">
<span><img height="65" width="59" apple-inline="yes" id="A9623F98-C8B0-4900-88A1-9B6866EFB784" apple-width="yes" apple-height="yes" src="cid:879A6E78-CA46-47B2-AA0E-1810BD833229" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class="">QGIS Project Steering Committee Chair</div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
</div>
<br class=""></div></body></html>