Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by jri

  1. Jim, I'm going to try to have a look at the problem this weekend. Can you confirm which version of Firefox you're using, and whether you're using Windows or a different OS. Mallah, you're not imagining it - I'm aware of the cause of this and should shortly be able to publish an update to fix it.
  2. As some of you will have noticed, it's been a bit quiet from me recently. Alas, the real world has intervened and between a combination of work and personal issues, I haven't had much time for GME or geocaching in general recently. That said, I am working on bugfix update to GME, which I hope to be able to get out in the next week or two. I tend to use Firefox for development, so that's always going to be the browser that gets the best support. I'd like to keep GME working with Chrome and Opera too, but they're a lower priority for me at the moment. I know that Opera is moving over to being based on the Chromium engine (the same as Chrome), so there is likely to be some commonality in how extensions work on both browsers. At the moment, I'm not sure that I would be able to turn GME into a proper Chrome extension, because of how it works. As it inserts scripts into web pages to modify what they do, it might fall foul of the reviewing policy. That said, it looks hopeful that GME should continue to work in Chrome using Tampermonkey, which is a bona fide extension. Hopefully I'll get a chance to test out some of this soon!
  3. I'm not sure if GME can do precisely what you want, but it can do something fairly close. OutSide Maps uses OS Openspace data. This isn't compatible with GME because it uses a different datum to Google Maps (essentially, north is in a different direction!), and the mapping library on the Geocaching website isn't smart enough to rotate the map tiles to make everything line up. However, other historic Ordnance Survey maps are available from OpenStreetMap in a compatible format. To add these mapsources into GME, you paste a string of JSON code into the script's configuration screen. Go to Geocaching Maps and click on the GME configuration icon (the gear), click onto the 'Custom Maps' tab, paste one of the codes below into the 'Mapsource' box, then click on 'Add' then 'Save'. The page should re-load, and you should be able to select the new map. To use OS New Popular Edition maps from 1945-55 at 1:50000 scale, paste in this code: {"alt":"OS NPE","tileUrl":"http://{s}.ooc.openstreetmap.org/npe/{z}/{x}/{y}.png", "minZoom":6, "maxZoom": 15, "attribution": "Ordnance Survey maps from <a href='http://www.openstreetmap.org/'>OpenStreetMap</a>, <a href='http://creativecommons.org/licenses/by-nc/2.5/'>CC-BY-NC</a>"} The code above loads the NPE maps as a baselayer, i.e. they replace your normal map when you select them. These maps don't work great as an overlay, as the tiles are opaque - they weren't designed to sit on top of another map. However, you can still make them work as an overlay by making them semi-transparent: {"alt":"OS NPE","tileUrl":"http://{s}.ooc.openstreetmap.org/npe/{z}/{x}/{y}.png","minZoom":6,"maxZoom":15,"attribution":"Ordnance Survey maps from <a href='http://www.openstreetmap.org/'>OpenStreetMap</a>, <a href='http://creativecommons.org/licenses/by-nc/2.5/'>CC-BY-NC</a>","overlay":true,"opacity":0.75} The two codes are the same apart from the addition of 'overlay' and 'opacity' parameters in the second version. The opacity parameter can be from 0 (totally transparent) to 1 (opaque), and might take a bit of fiddling with to get a result that looks good. A few other OS map editions are also available, see http://geo.inge.org...._maps.htm#oocos for details.
  4. As of a few weeks ago, GC.com started experimenting with new layouts for the cache pages. Users would get randomly diverted to the new designs, which have different URLs to the old-style cache pages. That means that GME doesn't recognise them as cache listings any more, and so doesn't do its magic. In the long term, I'll be able to update GME to work with whatever pages we end up with. At the moment it's a bit of a moving target while Groundspeak play with their designs. I was getting the new versions quite regularly a fortnight ago, but more recently I seem to have been getting the old style fairly consistently. When I was getting the new versions, the workaround seemed to be to hit the back and forward buttons until the cache page loaded in the old style, which would let GME work again.
  5. Well I don't use a Garmin (or Field Notes of any kind), and I haven't got one of these devices, but it looks as though it should work. It's running Android 4.0, so it should be able to read the Field Notes file from USB, if your Garmin works the same way as a USB memory stick does when you plug it in to a computer. I've got an Android tablet myself (an Asus Transformer), which works fine with normal memory sticks. It does have trouble reading from devices like my smartphone though. I think that the problem is that when you plug my phone into the USB port, the phone asks what mode you want it to use for the connection; the tablet is expecting to be able to read the device straight away, and gets confused waiting while the phone figures out how to connect. If your Garmin connects straight away when you plug it into a PC/Mac, and shows up the same way as a memory stick, then you ought to be OK. That said, that tablet looks pretty low tech. The screen is small and low resolution, and from the reviews I don't think it's got a touch screen. You should be OK with a simple web browser and email, but it may be a bit low powered for some Android apps. The reviews look positive, but I guess you get what you pay for... If you do get it, one app I would recommend is the ES File Explorer. This is a free file manager that you can use to copy files, rename them, and move them around your device (and do lots more). It may be helpful for finding the field notes file on your Garmin, making copies, and putting them somewhere the web browser can find them. Hope this helps!
  6. I think that probably counts as a bug What happens is this: when you load a cache page that has waypoints or corrected coordinates, GME stores the details of those waypoints, and adds "&pop=true" to the View Larger Map link. When GME runs on the map page, if the URI contains "&pop=true", it retrieves the stored coordinates and displays them on the map. It then pans the map to the centre of the group of coordinates. Since the last Groundspeak update to the maps, panning the map updates the URI, which explains why you see the link update. Where it seems to be going wrong is that if you open a second map page before following the View Larger Map link, the waypoint details get overwritten, and the map page shows that cache instead. I'll have a think about how I can improve this behaviour in the next version. It will be a little tricky to solve, as it's difficult to use scripts to communicate between open web pages, but I'll see what I can do.
  7. My configuration: Chrome v27 running on Win XP (problem doesn't occur in other web browser, but might affect other versions of Chrome). No browser extensions enabled. Default language set to en-gb in Chrome, with en-us and en also selected. How to replicate the bug: Go to http://www.geocaching.com/ Use the language pull-down on the right of the green menu bar to choose a language that isn't one of your default languages for Chrome. I used Francais. Go to http://www.geocaching.com/map/ If nothing untoward happens, try dragging the map a little. What happens: The map starts bouncing up and down the screen, with a translation message appearing and disappearing above it. In the address bar, the URL being displayed keeps changing, with the latitude parameter gradually decreasing. In more detail: When you go to the maps page, Chrome detects that the page is in French (or whatever language) and pops up a message offering to translate it. This message appears at the top of the browser window, reducing the size of the map. The map page detects the change of size, and updates the hash in the document location to reflect new coordinates for the centre of the map - you see this update in the address bar. Chrome notices the location hash change and thinks you are navigating to a new page. It hides the translation message, then pops up another one for the "new" page. This repeats indefinitely until you navigate away or close the tab. Trying to click the "no, don't translate this" buttons doesn't seem to work. What I would expect to happen: Ideally, you should only get prompted once by Chrome to translate the page. If you can click "Nope" at the time the first prompt appears, Chrome doesn't ask again on the same page - even if the URI hash changes. However, if you don't respond to the prompt, it keeps getting hidden and redisplayed on every hash change. There is a workaround: there is a tick-box in Chrome's advanced settings to disable the translation prompts. However, that applies to all websites, and you might actually want to translate some of them. I think the problem could be avoided if the Geocaching Map page ignored resize events, and only updated its URI when the map is dragged or zoomed.
  8. It's still working for me, so I guess you might have accidentally disabled GME somehow. Is Greasemonkey or Tampermonkey still enabled? What you've got is now the default list of maps supplied by the website. They changed the list a while back but I didn't bother incorporating it into GME as none of them looked especially helpful.
  9. Generally I like the look of the new layout - it looks cleaner than the old one. However... At first glance I couldn't find the "Log a new visit" link, as it looked like a heading. It isn't styled consistently with any of the other links / buttons on the page. The "Watch" link should change to "Un-watch" when you're already watching a cache - or at least pre-select the cache when it takes you to view your whole watch list. The "Found it" smiley (or accompanying text) should link to your log for the cache. As a bit of a feature request, it would be nice to see a blue frown icon here with a link to your DNF log, for caches you've already failed to find.
  10. What Chris said for the menu settings! (I haven't got a Magellan), but here's the explanation for why there's a difference in the coordinates: A geodetic datum is a mathematical description of the shape of the world. Because the world isn't perfectly spherical, it's hard to describe its shape accurately. OSGB36 is a datum that gives a relatively good match to the shape of the part of the world around Great Britain, but is somewhat ropey everywhere else. The WGS84 datum isn't such a good fit for GB (or anywhere else), but overall gives a reasonable match for the whole planet. The National Grid and Ordnance Survey grid references are based on the OSGB36 datum, so if you want to give an accurate grid ref, you need to set your datum to OSGB. Geocaching (and most other GPS applications) use the WGS84 datum, so if you want to share lat/lon coordinates with other geocachers, you need to be using WGS84. Where the confusion comes in is that you can use the OSGB datum with latitude/longitude coordinates as well as grid references. However, these coordinates are based on a different shape planet from WGS84. What this means is that the same numerical latitude and longitude can refer to two different points in the two datums. The difference varies across the UK, but can be over a hundred metres. In practice, accuracy isn't really a problem. The issue is that OSGB and WGS84 are two different systems, and to share their coordinates correctly, you need to know which system the people you share with are using. Further reading: the first few sections of https://en.wikipedia.org/wiki/Ordnance_Survey_National_Grid and the Coordinates & Map Datums section of http://www.follow-the-arrow.co.uk/resources/gps.html Hope that helps!
  11. I think that this is just normal behavior for the website. When you click "View Larger Map" on a cache page, the map opens in a new browser tab. Because it is a new tab, it doesn't have its own back history, and the back button doesn't work. However, the tab with the cache page should stay open, so if you just close the new map tab, you should get back to where you were. I could change GME to make the larger map open in the same tab, but I think it's more helpful to be able to have both the description and the map open at the same time, so you can flick back and forth between them. If you really want to open the map in the same tab (so the back button works), drag'n'drop the 'View Larger Map' link into the address bar.
  12. I'd not come across Opera Mobile 14 yet, so I just downloaded a copy to try. The good news is that GME pretty much works in OM14 (in fact, at least one OM12 bug is fixed). The bad news is that using the script isn't exactly user-friendly in the current beta version. OM14 doesn't currently have support for extensions or userscripts, so the only way to get GME working is to paste a line of javascript into the address bar on every page you want to use it with. Not exactly convenient. Once running, it's rather hard to use the GME icons, as the bottom edge of the map is pushed off the bottom of the display. This seems to be because the address bar is permanently displayed at the top of the screen. That could be worked around relatively easily, but looks like a bug in Opera. The other problem I had was in using the i menu: Opera seemed to prefer some links to others, making it very difficult to click on what you want. Again, I might be able to work around that. The final issue was that OM14 seems a bit buggy in how it displays new tabs. I'm not going to be making any changes to GME to support OM14 just yet, not until it looks a bit more mature. However, once I've had a chance to play a little more, I will post instructions for how to make GME work in browsers without userscript support, by the page-by-page manual method... It ought to work in the Android browser, Chrome Mobile, IE, and possibly more.
  13. I've updated GME to v0.6.6.2 to fix the link to the MAGIC site. I pinched the layer selection from Gary & Jane's Magic MapIt site, but next time I do an update, I'll check the wiki to see what the reviewers are using. At the moment, the new MAGIC Map looks a lot better than the old one, but still has a few bugs. When you click through from GME, you get an error message about an Aerial Photography layer, and the map itself may either be blank or show an outline of the UK superimposed on top. This seems to correct itself if you pan or zoom slightly. The map also looks rather squashed along the north-south axis when viewed in WGS84 mode. You can correct it by switching to OSGB, although remember to switch back if you need to copy down coordinates to use on a GPS (the same point has a different lat & lon in each system).
  14. It looks like DEFRA have totally updated the MAGIC site as of 22 May - see their news page. I've just had a quick look and it seems like I should be able to make GME link nicely to MAGIC again, but it will take a little playing around to get the format of the new link right. Anyone have a view on which layers should be displayed in MAGIC when you follow the link from GME? I've not checked to see whether the selection available is the same as in the old version of the site.
  15. I'm lousy with smart phones, but... Can you create a text file on your phone? And can you save that in a set place with a set name? If you can then you can simply copy the contents of the javascript file that opens up when you press the green button into the text file and save it - the name will, presumably, need to be a js file type - not sure if it needs to be 109145.user.js or not. On my desktop I only use the script with Opera. Every time I need to update it I can simply copy the code from the web and paste it on top of the code I already have and save it again. Makes life very, very simple indeed - so massive thanks go to jri for making something work really easily in Opera!! :-) I'm using Opera on Android rather than Symbian, but I couldn't see an easy way to save the file directly either. However, you don't have to do the download in Opera itself, so Blue Square Thing's copy'n'paste technique may well work, as should using the cable. I use the Android browser to save the file (long-press on the Install button, then "Save link"), then ES File Explorer to move it to the right place. For Opera, the important thing is that the file is saved in the folder that you've set in Opera:config, and the filename ends in .user.js (the first part of the name can be anything you like). Also, check you've got Opera Mobile rather than Opera Mini. The Mini version doesn't support userscripts.
  16. Well, I suppose I should announce the latest version of GME, v0.6.6 v0.6.6.1 Mainly this was going to be a minor bugfix release, to fix some problems with GPX handling pointed out by G4UYG and stretch.kerr, and to try to restore some of the IE functionality that got broken by the site update last month. However, I've also had to add in a fix to keep cache labelling working after the 14th May site update (the "performance improvements" mentioned here), and work around the Chrome issue described in the posts above. Somewhere along the way I got sucked into adding some more features: a new map server type (to support an Austrian map for ErichSt), and some improved integration for Android. It's the last bit I'm most excited about. When you use the i tool, the popup should now include the coordinates as a geo: link. When you click on the link, a browser should be able to interpret the coordinates and do something interesting with them. In Opera Mobile on Android, the browser pops up a choice of apps to use to view that point. On my tablet, I get a choice of Google Maps, Locus Maps, or the radar navigation widget from the GPS Status app. Unfortunately, geo: links don't seem to be widely supported by desktop browsers yet, and Opera Mobile is the only full-featured Android browser I know of that supports userscripts. I am tempted to write a script to enable geo: support in other browsers, and I've gone a bit further for Android too: when GME detects an Android or mobile browser, it should include links to start the Google Navigation and Google Streetview apps directly too, instead of just going to the GMaps website. This is a bit experimental, so any feedback is welcome!
  17. I wasn't seeing any problems until I updated to the latest version of Chrome this afternoon. It turns out that Google have fixed a security bug in Chrome, and in doing so broke Tampermonkey. The morbidly interested can read about the gory details here and here. I've now updated the script to v., having put in a small tweak to avoid triggering the problem. The upshot is, people like me who hadn't updated Chrome yet wouldn't have noticed a difference, and people who install GME as a native Chrome extension (rather than using Tampermonkey) shouldn't have noticed either. The issue only occurs with Tampermonkey and Chrome v27 and up. While there are complicated workarounds involving tweaking Tampermonkey's settings, the easy solution for everyone should be to install GME v0.6.6.1. Fingers crossed it works!
  18. Yup Well, something's going wrong anyway. From what you describe, it sounds like GME isn't loading at all - those extra maps have been on the basic site since the Groundspeak update about a month ago. The simplest cause could be that you accidentally switched off Greasemonkey/Tampermonkey by clicking on its icon. Otherwise, try restarting your web browser, and reinstalling GME from http://geo.inge.org.uk/gme.htm#install If that doesn't work, you'll need to post more details: what web browser are you using? Do you see any of GME's modifications to the web pages? Are there any errors in your browser console?
  19. Since the security restrictions changed in Chrome, you need to follow these instructions to install GME.
  20. I use an HTC Desire for geocaching. It's fairly elderly now, but the GPS accuracy is pretty good, certainly comparable with my standalone GPS units. One tip, whichever Android you get, is to get the GPS Status app. It lets you easily update the phone's AGPS (Assisted GPS) data. AGPS gives the phone orbital data that helps it lock onto the GPS satellite signals. It doesn't improve the accuracy, but having current AGPS data makes the time to first fix much shorter. The data is normally good for a few days, but gets progressively worse with time, hence the need to keep it updated.
  21. I think they should get rid of this forum all-together, because, let's face it, 99% of these requests won't be implemented. This forum is just a tease. Not necessarily, it does provide a list of interesting ideas for anyone who wants to set up a competing web site. Of course top on the list of requests for any competition would be one that takes no technical effort at all, namely to communicate with users. I actually look in this forum for interesting ideas that I can implement myself. There's quite a few features of my Geocaching Map Enhancements script that have started out as ideas here. And if I can implement them in a client-side script, it means that Groundspeak could probably implement them themselves with no extra burden on their servers. Making the website location-aware is one good example.
  22. Are you using a Mac by any chance? There's a thread running in the Website Bug Reports forum about not being able to print maps. Looks like Groundspeak are hoping to fix it in about a fortnight.
  23. In Chrome, you need to right-click on the Install button and choose the Save Link As option, or whatever it is that Chrome calls it (the Install button is just a link in disguise). That should let you save it, then you can use the instructions above.
  24. My Pebble arrived last week, so I'm pondering the possibilities of geocaching apps. It was one of the applications the Pebble folk mentioned early on, but I've not spotted anything since. However, I'm vaguely thinking about writing my own app. What would you see a Pebble geocaching app actually doing? My first thought would be a really simple app that ran on the phone and sent out a notification to the Pebble when you went within a certain distance of a waypoint. You'd then get out your GPSr/Smartphone for the business of reading the cache description and doing the actual navigation. A more complicated version would send extra details to the Pebble (name, hint, range, bearing, etc), and might keep it updated as you got closer. But what information is actually useful to have on your wrist? How would you navigate it? Remember that the Pebble has a small display and only a few buttons, and you're already carrying a GPSr/Smartphone with you. From what I gather (I haven't read the specs yet), I think that you would also have to actually be running the app on the Pebble (rather than a watch face) in order to do anything other than receive alerts. PS the possibility of me actually writing this app is distinctly hypothetical. I've not got much time to put towards it and I've never written an Android app before. And don't even get any ideas about iOS!
  25. Right. I think I have cracked it. I've uploaded Geocaching Map Enhancements v0.6.5 to userscripts.org The new version should fix the problems that were caused when Groundspeak made the 17th April update to Geocaching.com. OS maps should work again, and the configuration system has been totally re-vamped. It should now look better, and can also be accessed via a link on the Profile menu from most pages on the site. The upside of Groundspeak's upgrade to a more recent version Leaflet Maps is that I've been able to make various other under-the-hood improvements to the script code, and remove some of the bug-fixes and workarounds that were there before. That said, I've not done too much testing (none on Internet Explorer), so do let me know if you come across bugs. With this update, there should be no need for any awkward manual editing of scripts. I've also disabled the link to the work-in-progress version - just go for the new official version on userscripts.org. As always, the full feature list, installation instructions, change log, etc. is available at http://geo.inge.org.uk/gme.htm
  • Create New...