steeltkb

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About steeltkb

  • Rank
    Member
  1. I love how EasyGPS can display the same symbols that my plotter uses. I have a Lowrance HDS-7. Unfortunately, the symbol for a rock pile gets exported from EasyGPS as "<sym>rock</sym>", and Lowrance [at least for HDS-7] calls this symbol "<sym>rocks</sym>", with the plural "s". When Lowrance imports the EasyGPS-exported GPX, it doesn't understand "rock" and makes it the default blue circle. It only understands "rocks". I am attaching a sample GPX exported from my HDS-7 with a WPT with the correct "rocks" symbol. Reimporting this GPX into the HDS-7 results in the correct symbol being displayed. EasyGPS just needs to call this symbol "rocks" instead of "rock". Any way to change the symbol name map in user settings somewhere? Otherwise, maybe you can include this in a future update. Thanks very much! sample.gpx
  2. That's a good idea. Thanks. I'll keep notes out on the water of any waypoints I adjust. I already keep notes about which WP's I visit and what type of fishing I found there, so that won't be too bad. A suggestion for future development, then. Thanks!
  3. I have a Lowrance HDS-7. It "communicates" with EasyGPS by importing/exporting files on the SD card. I am able to send and receive fine. I am curious what is happening with waypoints that I've edited on the device, though. I couldn't find anything in the help files that really addresses the intended behavior here. Here's what I'm seeing: say I have my main GPX file on my computer that holds *all* of my waypoints. Let's assume that my GPS has all the exact same waypoints. Maybe they were even just imported fresh from EasyGPS. Then let's say I slightly edit the position of one "WP01". It was N28 11.200, W83 15.105 (in EasyGPS), and now on the device I've changed it to N28 11.202, W83 15.107. A difference of about 15 feet. When I "receive" these waypoints back into EasyGPS, the program does not update the position of WP01. It retains the old position. If I change the position of WP01 in the GPS by 1 minute (a little over a mile), then when I receive the waypoints, EasyGPS adds the waypoint as a duplicate entry with a different position (i.e., there would then be two WP01 entries - one with the old coords, one with the new.) My ideal setup is that I would use EasyGPS to manage my waypoints, make notes, etc..., and then I would be able to tweak the positions of the waypoints while I'm on-location using the GPS device. When I returned to my computer, I would upload and merge my waypoints into my "master" GPX in EasyGPS, and have EasyGPS update waypoints that had locations [or other data] changed. It would actually be nice if EasyGPS told you that a waypoint was moving by "xx feet" or "xx miles", and is that OK? Or maybe "Easy GPS is creating a new waypoint named "WP01" because the waypoint's imported position is more than 1,000 feet [user-settable?] from the existing waypoint in this GPX file." Am I doing something wrong, is this future functionality, or is this something you have to buy ExpertGPS if you want to do? - Tyson
  4. Feature request to improve user experience I find myself wishing that I could double-click a waypoint "row" to open up the edit dialog. I'd like to be able to have the whole row be the double-click target. The other option would be to have only the row header be a double click target and make double-clicks on any other data initiate a "quick / in-place edit". However, since you use "F2" as a shortcut to do a quick edit, it might be nice to have the analogous "slow double-click" also trigger a quick edit (thus, same behavior as Windows Explorer file renaming). So, my vote is that quick double-clicks anywhere on the waypoint data row would bring up the Edit dialog, while slow double-clicks would initiate quick edit on the datum clicked (just like single click, "F2"). Thanks so much.
  5. In using the "map display" on the right panel of EasyGPS, I found it slightly hard to zoom because my natural tendency was to point the mouse at the waypoints I wanted to zoom towards and spin the scroll wheel. EasyGPS, however, always zooms toward the center of the display. Obviously, I could change my behavior: pan the waypoints to the center of the display, and then zoom in and out. This is actually harder than it sounds. As you zoom in closer & closer, the positioning error is magnified, and eventually the waypoints go off the page. Unless you stop zooming to pan them back into place. I would suggest, instead, that the map always zoom in toward and out from the point over which the mouse is hovering. The mechanics would be that after the zoom is complete, the point over which the mouse was/is hovering should not have changed its position in the display window. I would point to Google Maps (and most other online mapping services) as a shining example of how user friendly this behavior is. You can fly in and out, because you can constantly (and unconsciously) make small corrections in the zoom trajectory by simply moving your hand, instead of stopping the zoom operation, panning, and then starting to zoom again. Most image editing programs (Photoshop) use the "zoom towards / away from pointer" method, too. Thank you for your work on the EasyGPS software. I've been tearing my hair out trying to find a decent solution for working with waypoints from my Lowrance HDS-7 for a long time, now, and I think I'm taking to your software. - Tyson
  6. In EasyGPS, if you're using US units like feet for depth data associated with a waypoint, when you save the GPX file and subsequently reopen it, the *displayed* values are annoyingly modified due to the US > METRIC > US conversion. This conversion is performed because, of course, the GPX format is metric-based. For example, if you enter "65 ft", after saving and reopening the file, EasyGPS will display "64.99 ft". 60 becomes 60.01, 30 becomes 29.99, etc... For one, it's silly to display values this precise, especially for water depth in particular, where the measurement error can be 5ft+. I would propose that the user be allowed to set the precision or rounding with which these values are displayed. For me, rounding the values (up or down) to the nearest whole number would be what I'm looking for. I haven't tested it at all, but I'd imagine that a similar problem would exist for elevation? Thanks! - Tyson