Jump to content

jri

Members
  • Posts

    325
  • Joined

  • Last visited

Everything posted by jri

  1. Thanks for sharing this. I'll build it in to the next release of the script.
  2. I wrote a Greasemonkey script a few years back which adds the height in metres to a cache listing, next to the coordinates. You can get it from https://openuserjs.o...Geocache_Height - there's also a version which works in feet. The height data comes from Google, and has the usual caveats about taking its accuracy with a pinch of salt.
  3. I've had a look at this, and it's not related to GME. I switched off Greasemonkey, so I was just using the plain website, with no scripts, then did a filtered search. When I clicked the "Map These Geocaches" button, it worked about 50% of the time, showing just the four caches from my search. The rest of the time, the four caches appeared, then disappeared to be replaced by the normal, unfiltered map. An intermittent fault like this implies that either its another overloading problem, similar to the issues GME was having, or that some of Groundspeak's servers are configured differently to others, and it's pot luck which you get.
  4. Glad GME's working for you again. And yes, GME should already have the feature you want! If you turn on the 'I' tool and click on the map, there should be a link to hide cache icons (and turn then on again).
  5. I had a meeting in London today and used some of the time on the train to finish fixing GME. Strangely, the dodgy 3G internet signal in the Wiltshire countryside gave just what I needed for testing how the script reacted to slow website load times! The result is on Github at https://github.com/JRInge/userscripts/raw/GME-Development/GeocachingMapEnhancements/Geocaching_Map_Enhancements.user.js (same link as before). It would be great if anyone could be a victim volunteer for testing, and let me know how well it works, as I haven't had a chance to do much testing. In particular, I've not really tried out how the script works on pages other than the main maps page (i.e. trackable maps, cache listings, cache placement, etc.). If it all seems to be working, in a few days I'll post the update on OpenUserJs.org, which should auto-update people who haven't manually installed the Github version.
  6. I think most of these problems are caused by Groundspeak's server issues. From what I figured out yesterday, the symptoms with GME are caused by GME trying to modify the map page before all the scripts from the geocaching.com servers have loaded and run properly. I can work around the issues to an extent by building more checking into the GME script, but it's hard to test and figure out what needs fixing: if the server is running too well, everything works fine and I can't see a problem. If it's too bad, then I get the 500 error and nothing works! The same problems are probably also behind the issue where the map page loads, but clicking on a cache icon doesn't do anything. Whenever you move the mouse over a map tile, there is a request to the server to ask whether any caches are in the area, which has to be answered before you can click on the icon. After you've clicked, there's another request to fetch the information about the cache. Overloaded servers can break the website at any of these stages.
  7. OK, I've fixed the first part of the problem (no GME icons). For the desperate, a somewhat-working version of the script is available on GitHub at https://github.com/JRInge/userscripts/raw/GME-Development/GeocachingMapEnhancements/Geocaching_Map_Enhancements.user.js If you do try the GitHub version, it may break the auto-update in Greasemonkey. Be sure to re-install the "official" version when I announce it here. I still need to fix the extra map selection icon, and I was going to do some work to the cache page maps too. Unfortunately I'm just getting "500 - Server Error" from the website right now, which probably means it's overloaded again. As I can't do any more testing at the moment, I'm going to go out caching instead.
  8. Just discovered the same problem myself today (grr, no alert from the forums). I've got some kid-free time over the next few days, so I'll try to get a fix sorted out.
  9. I've now released a bugfix update: GME v0.7.3.2. Greasemonkey / Tampermonkey ought to auto-update in due course, but if you are impatient or installed a modified version, you might need to get it directly from https://openuserjs.org/users/JRI/scripts Hopefully this will fix the current problems, but I've not done much testing, so let me know if there are other issues. This version should remove all trace of Mapquest from GME, and set OSM to be the default map. The reason the changes to the website broke GME so badly was that Groundspeak now include Google Maps as an option even when you have Leaflet Maps selected in your Map Preferences. As both map engines are loaded at the same time, GME couldn't work out which you were using, and quit because it assumed you had the wrong one. I've now disabled this test, so GME should work fine again when your preference is Leaflet. As before, it won't work when Google is selected as your preferred mapping engine, but as my Premium membership lapsed some while ago, I can no longer test quite how gracefully it fails (or not). If any PM knows enough Javascript to give me a reliable test, let me know!
  10. I'll have a go at fixing this properly tonight after I'm back from work - screaming children and wife permitting! I'll post here once it's done - not everyone seems to get automatic updates.
  11. Just a thought, but have you recently cleaned out your browser by deleting cookies, temporary internet files, etc ? If so, that's where your custom mapsource data is held. Been there, done that. You just need to add the OS Maps source back in using the same method you did originally. Earlier posts in this thread #705, #706, #708, & #711 discuss this. If that doesn't solve the problem for you, I'll need more details about what's happening (or not) before I can help. Have you tried the tips on the troubleshooting page? http://geo.inge.org.uk/gme_trouble.htm
  12. PM'd you with the full text Looks like we're probably OK, but I'll try to check in more detail when I've got my current uni assignment out of the way. I'm hoping to get time over the summer to do some major work on GME that may mean it can get OS maps without going through Bing, but either way, I should be able to make sure there aren't any problems come November.
  13. This won't affect the GME script itself (for non-Bing maps), as it doesn't use Bing's software. However, if retiring their old version means map tiles are no longer served up in the way GME uses, that could cause a problem. If you PM me the message, I'll look at the details (I'm not actually using the Bing service myself at the moment).
  14. I had this problem too, but it seems to have been fixed now - thanks!
  15. jri

    View larger map

    Looks like a website bug. The small maps on the cache listing pages work fine, but the big map at http://www.geocaching.com/map seems to be broken - I've checked in Edge, Chrome and Firefox. I see the header bar and search sidebar, but the map pane is blank and none of the sidebar functions work. Looking in the browser console, it seems there's a javascript error that's crashing the whole page before it attempts to load the map. I guess that means I won't be looking for too many caches today...
  16. This always irks me. People get caught up in the politics and miss the website bug. I can see that Groundspeak's decision to use geographic boundaries rather than political ones is deeply annoying to many, but that's the decision they've made. The bug is that while logging caches follows the geographic boundary (logging a Belfast cache ticks off "Ireland"), the statistics map follows political boundaries (logging a cache in London colours in Northern Ireland on the map). While I accept we're unlikely to see the regions change for logging caches, could we at least get the stats map consistent with those regions?
  17. Rather than spend time making the script configurable, I've created a second version that displays the height in feet instead. You can get either script from https://openuserjs.org/users/JRI . You can even install both, and see the cache height in both metres and feet at the same time!
  18. I hadn't been maintaining that script, as I built a height tool into GME, but I've now re-witten it and put it on OpenUserJS.org, at https://openuserjs.o...Geocache_Height It now has an icon, and behind the scenes I've put together a test suite so I can fix it again quicker next time it breaks. Let me know how it works for you!
  19. Those aren't single quotes - they're arc minute signs (or at least they are in the source code)! Seriously, are they causing any particular problem? The idea of including them in the example was to show that the Freeform Coordinates box will let you cut'n'paste in coordinates copied from other places without having to worry too much about odd punctuation. You can use most relatively sane formats too: decimal degrees or degrees, minutes and decimal seconds (with or without punctuation) should work too.
  20. It annoyed me too that the driving directions at the top of the cache pages ignore any Parking Area waypoint. I built a workaround into my Geocaching Map Enhancements Greasemonkey script. With GME, you get an extra Parking icon to the right of the waypoint details. The link at the top of the page still gives you directions to the cache location (which may be unhelpful), but the icons by each Parking Area or Trailhead waypoint give you the Google directions from your home coordinates to that waypoint. If there's more than one Parking Area or Trailhead waypoint, each one gets its own directions icon. If you're not using a script, it's rather tedious to have to edit the driving directions link by hand, or manually enter the parking waypoint into Google Maps to get directions. It may not be high on their priorities list, but as all the necessary information to do this is already on the cache pages at the moment, I would have thought that Groundspeak could implement directions links for waypoints without taking much extra load on their servers.
  21. This problem seems to occur because of the way the map page loads data about where the caches are. Although you can see the cache icons on the map, they're just pictures (actually, transparent map tiles), and not clickable on their own. As you move the mouse over each map tile, your web browser requests data from the servers to tell it whereabouts the caches are, relative to that tile. When the response comes back, the clickable hotspots get activated. At this point, you see the cursor start to change shape when you move it over cache icons, and you can click them to get the popup information. Presumably, this is done to limit the amount of database lookups the servers need to do. The problem is worse when you have a slow or unreliable network connection, if you are using a touchscreen rather than a mouse, or if you are particularly fast and accurate in clicking the mouse. To make things work better, move the mouse near to the cache you're interested in, wait a second, then click the icon. With a touchscreen, tap the icon, wait a second, then tap it again. If nothing's coming up at all, it may be that your internet connection had dropped out at the time your web browser tried to get the cache location data. If its request fails the first time, the browser doesn't try again until you zoom in or out, or refresh the page. Change the zoom and try again.
  22. So I guess the forum shouldn't still show me in the "Premium Members" group either... It doesn't. Interesting... it did when I made the post! And it's by no means the first post I've made since my PM status lapsed some months back. I guess that implies that The Powers That Be do read these forums, even if they don't always reply.
  23. So I guess the forum shouldn't still show me in the "Premium Members" group either...
  24. When I log a cache as found, at the bottom of the form there is a checkbox for the option to "Add to your Favorites (114 remaining)". When I tick this and Submit the log, the log is posted OK, but the cache does not receive a Favorite Point and the count of my points does not decrement. I assume that this behaviour happens because my Premium Membership has lapsed. I would have hoped that, having earned the points while a PM, I could still reward COs with them on the odd occasion I find something more worthy than a nano cache with a damp piece of papier mâché inside. If being an ex-PM, I'm not allowed to hand out Favorites, I don't think I should see the prompt to do so. Alternatively, I should receive some kind of error message when I try.
  25. GME does this already! On the main map page, type a "p" in the search box, followed by a space and some lat/lon coordinates. Click the magnifying glass button and it should plot a small marker at that point. Various coordinate formats should work. I must get round to documenting this at some point... Also, on the cache page for a puzzle or multi-cache, you'll notice a little pencil symbol next to the coordinates. You can click this to correct the coordinates to match the final location of the puzzle (this is a standard website feature). If you do this, then GME will show the the coordinates on the little map on the cache page, with a green tick mark next to the cache symbol and a blue line going back to the original location. If you click the "View larger map" link, then you should see the same (plus any waypoints) on the main map page. If a cache has corrected coordinates or waypoints, you can also display them on other maps by dragging the cache icon from next to the title of a cache listing page, and dropping it onto a GME-enabled map. You can use this to show the correct locations of several completed puzzles on the same map at the same time.
×
×
  • Create New...