Jump to content

Include GPX-file in notice mails


pstray

Recommended Posts

Just a suggestion. I would really like it if the notice mails i get when new caches are published, or old ones are disabled or enabled again to contain the updated cache as an GPX-file attachment. It would make it much easier to update my GPS, than having to start a browser, go to the cache and download the file myself :)

Link to comment

Groundspeak wants you to visit the cache page for several reasons, not the least of which is to have an opportunity to read all the information on the cache page, as well as business related issues.

 

Not much info on the page besides images that isn't included in the GPX-file... so I don't see your point there. And it's not like I wouldn't visit the web page every day even with this feature added.

 

Also, including the GPX files will increase the size of the mail load.

 

Sure, but it could reduce web-server load. And implementing such a feature doesn't mean that it should be enabled by default. It should be an option that you check off when you set up your notifications.

Link to comment

Groundspeak wants you to visit the cache page for several reasons, not the least of which is to have an opportunity to read all the information on the cache page, as well as business related issues.

 

Not much info on the page besides images that isn't included in the GPX-file... so I don't see your point there. And it's not like I wouldn't visit the web page every day even with this feature added.

 

Also, including the GPX files will increase the size of the mail load.

 

Sure, but it could reduce web-server load. And implementing such a feature doesn't mean that it should be enabled by default. It should be an option that you check off when you set up your notifications.

 

Agreed.

 

All the talk of "Server load" is bogus. Most new notifications are regional so they have very low server load. The GPX files are text so they carry a VERY low load on the servers.

 

As you said. Adding the GOX file to the new notification makes sense if one is worried about server load. Less web traffic means less "on demand" load. Emails are not "on demand" load and que rather than actually stealing bandwidth from other applications. Or, i should say, thats how they should be set up.

 

For all those who go after FTFs using their phone, I think it's a great idea to have the GCX file included in the notification.

Link to comment

Groundspeak wants you to visit the cache page for several reasons, not the least of which is to have an opportunity to read all the information on the cache page, as well as business related issues.

 

Also, including the GPX files will increase the size of the mail load.

And yet it will show up in a PQ the next morning, all without ever visiting the site.

 

What "cache info" is on the page thats not in the .gpx? Wouldn't that mean that gc isn't sending out valid .gpx files to start with? If thats the case, they need to fix the .gpx files, not make you come grab them manually off a page your not going to read anyway, because you know your going to read it later in the .gpx file.

Link to comment

Groundspeak wants you to visit the cache page for several reasons, not the least of which is to have an opportunity to read all the information on the cache page, as well as business related issues.

 

Also, including the GPX files will increase the size of the mail load.

And yet it will show up in a PQ the next morning, all without ever visiting the site.

 

What "cache info" is on the page thats not in the .gpx? Wouldn't that mean that gc isn't sending out valid .gpx files to start with? If thats the case, they need to fix the .gpx files, not make you come grab them manually off a page your not going to read anyway, because you know your going to read it later in the .gpx file.

Pictures. All the logs.

Link to comment
Attributes are...

Are they back again?

There are no attributes in the PQ I ran just a few minutes ago...

What attributes are you speaking of?

Markwell's post implied cache attributes were included in the PQ GPX. That was briefly true for a couple of days after the last code release but Groundspeak rolled it back quite quickly because it caused issues with <ahem>certain applications</ahem>. Last time I checked (last night), the attributes were not back in the GPX files.

Link to comment

:antenna: Per Lep, I and other reviewers retract caches from time to time. Retract is a sort of "unpublish". They go back to the invisible status that they had prior to publication. Mostly this happens within seconds of publication (that D'oh moment - or perhaps the publication itself was done by a keyboard kitty).

 

If the .gpx file went out with the notification, the retraction would be even more painful then it is already. You'd go out after the cache, possibly find it - and then get a "you cannot see this listing" notice. If the cache was retracted because it's in an unsuitable location, then you've been taken to that spot. You might NEVER get to log that find.....

Link to comment

Groundspeak wants you to visit the cache page for several reasons, not the least of which is to have an opportunity to read all the information on the cache page, as well as business related issues.

 

Also, including the GPX files will increase the size of the mail load.

And yet it will show up in a PQ the next morning, all without ever visiting the site.

 

What "cache info" is on the page thats not in the .gpx? Wouldn't that mean that gc isn't sending out valid .gpx files to start with? If thats the case, they need to fix the .gpx files, not make you come grab them manually off a page your not going to read anyway, because you know your going to read it later in the .gpx file.

Pictures. All the logs.

Links to the pics ARE included, and I'm not going to read 1500 logs just because a cache has that many finds, if logs are important, then include more in the .gpx (I would prefer 10 be included, and when I'm out caching, I carry the last 10 logs if I have them).

Link to comment

I seldom read the cache page information when I download a pocket query of an area for a day's caching expedition. Yes, I do happen to load them up in my Nuvi, but don't routinely check the cache page before looking for the cache. So, as long as pocket queries are available, I'm afraid that argument doesn't make much sense to me.

 

 

The retraction of published caches, however, does make some sense, but it would still be possible, if one were quick enough, to get to the cache page and grab the GPX before the cache was retracted, right?

 

 

That said, since I don't maintain an offline database, and am not an FTF hound, having the GPX file in the email notification doesn't matter to me. If we're voting on this, don't count mine as a "yes" vote. :antenna:

Link to comment

I think it is far more likely that folks will actually read and see the cache description if they are forced to retrieve it in another way.

 

Including the GPX in the email notification will almost certainly lead to methods to transfer the waypoints into a GPS solution and hit the trail a bit too fast for the FTF types.

 

BTW - not all relevant photos have thier links in the GPX file.

Link to comment
Guest
This topic is now closed to further replies.
×
×
  • Create New...