TrigPointing
- Richary
- 8000 or more caches found
- Posts: 4189
- Joined: 04 February 04 10:55 pm
- Location: Waitara, Sydney
Re: TrigPointing
Hmmm, next question then is should they be there by default? Or a separate download those who are interested can find?
Then to expand the topic, I was at a couple of TPs in New Zealand last week. Obviously they won't be listed so should there be the ability for people to add ones that aren't in the database (either because they are overseas or because of a mistake in the listing?). Sorry more coding work if that happens though
Then to expand the topic, I was at a couple of TPs in New Zealand last week. Obviously they won't be listed so should there be the ability for people to add ones that aren't in the database (either because they are overseas or because of a mistake in the listing?). Sorry more coding work if that happens though
- caughtatwork
- Posts: 17017
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: TrigPointing
They will be there by default. There is too much special coding to sprinkle around site to include them on "this" list but not on "that" list. I'll be loading them all with a special date (TBD) which will hopefuilly push them to the bottom of most of the state lists.
They are a GCA virtual cache, albeit a special type called TrigPoint which will show up as a <type>benchmark</type> in GSAK and other programs.
The ability to upload TrigPoints is being investigated. A GPX file is probably the easiest way to upload one (using the import functionality), although there may just be a simpler version containing the NAME, COUNTRY, STATE (if applicable), LAT, LON and ELEVATION. The rest can be defaulted to the standard text which you can then edit at your convenience. This is on the cards so no more work, just the expected volume of work.
They are a GCA virtual cache, albeit a special type called TrigPoint which will show up as a <type>benchmark</type> in GSAK and other programs.
The ability to upload TrigPoints is being investigated. A GPX file is probably the easiest way to upload one (using the import functionality), although there may just be a simpler version containing the NAME, COUNTRY, STATE (if applicable), LAT, LON and ELEVATION. The rest can be defaulted to the standard text which you can then edit at your convenience. This is on the cards so no more work, just the expected volume of work.
- caughtatwork
- Posts: 17017
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: TrigPointing
GPX and GPXLite files from WM are the suxxors
They don't conform to the GC GPX file schema and their own schema doesn't appear to exist.
<gpx xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" creator="Groundspeak, Inc. All Rights Reserved. http://www.groundspeak.com" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.waymarking.com http://www.waymarking.comwaymark.xsd" xmlns="http://www.topografix.com/GPX/1/0">
i.e. http://www.waymarking.comwaymark.xsd
GCA is run by volunteers, but sheeeet, we get most things right.
GC is run by paid professionals, have 30 people on their staff and they can't get this right? WTF?
Speaking of WTF?
http://www.faqs.org/patents/app/20090094214
Anyway, there is not enough data in WM GPX or GPXLitefile to import and have the WM identified as a TrigPoint. i.e. You could load ANY WM GPX file and it will be just as useless. I cannot assume that a WM GPX file should be used to generate a TrigPoint at GCA.
I think we're going to have to think up something else to import additional TrigPoints but at the moment I am at a loss to find something easy. Nothing that comes out of GSAK works either as they cannot be identified as a TrigPoint vs. any other waymark.
They don't conform to the GC GPX file schema and their own schema doesn't appear to exist.
<gpx xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" creator="Groundspeak, Inc. All Rights Reserved. http://www.groundspeak.com" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.waymarking.com http://www.waymarking.comwaymark.xsd" xmlns="http://www.topografix.com/GPX/1/0">
i.e. http://www.waymarking.comwaymark.xsd
GCA is run by volunteers, but sheeeet, we get most things right.
GC is run by paid professionals, have 30 people on their staff and they can't get this right? WTF?
Speaking of WTF?
http://www.faqs.org/patents/app/20090094214
Anyway, there is not enough data in WM GPX or GPXLitefile to import and have the WM identified as a TrigPoint. i.e. You could load ANY WM GPX file and it will be just as useless. I cannot assume that a WM GPX file should be used to generate a TrigPoint at GCA.
I think we're going to have to think up something else to import additional TrigPoints but at the moment I am at a loss to find something easy. Nothing that comes out of GSAK works either as they cannot be identified as a TrigPoint vs. any other waymark.
- The Spindoctors
- Posts: 1767
- Joined: 08 October 03 8:00 pm
- Location: Sydney
- Contact:
Re: TrigPointing
It gets better - http://www.faqs.org/patents/app/20090177486caughtatwork wrote: Speaking of WTF?
http://www.faqs.org/patents/app/20090094214
I'm not a patent lawyer, but doesn't The Hidden Park infringe on this one.
LOL
BTW - Keep going with the Trig points. I'll be supporting it 100% once available.
-
- 200 or more found
- Posts: 67
- Joined: 29 June 07 10:10 pm
- Location: Benalla VIC
Re: TrigPointing
Yeah i will be supporting it as much as i can!Spindoc Bob wrote:
BTW - Keep going with the Trig points. I'll be supporting it 100% once available.
Thanks for the work you have put in so far caught at work!!
- Rigger64
- 950 or more random things achieved
- Posts: 451
- Joined: 10 November 07 11:36 pm
- Location: Seaford
Re: TrigPointing
Same here i wish there was something i could do to help but im not that good @ doing that programing Stuff.Sons of Callum wrote:Yeah i will be supporting it as much as i can!Spindoc Bob wrote:
BTW - Keep going with the Trig points. I'll be supporting it 100% once available.
Thanks for the work you have put in so far caught at work!!
Keep up the good work caught at work.
- Facitman
- 1400 or more caches found
- Posts: 463
- Joined: 18 June 04 3:58 pm
- Location: Melbourne
- Contact:
Re: TrigPointing
If the Trigpoints are going to be in with all the other cache types and if there's going to be a lot of them (when compared to the number of caches) it would be good to have the filtering available in the Query generator well before they start being added. I would probably want to separate the feed of these from "regular" caches. Can we have an exclude option in the cache type on queries? At the moment I would need to check all types except Trigpoints/Benchmarks to maintain my current query contents. Not a deal breaker, just a suggestion.
PS. I am fully supportive of adding TrigPoints to GCA, it's just that I only find physical caches, no virtual, no locationless for me.
Thanks
Peter
PS. I am fully supportive of adding TrigPoints to GCA, it's just that I only find physical caches, no virtual, no locationless for me.
Thanks
Peter
- caughtatwork
- Posts: 17017
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: TrigPointing
The code (with the exception of the MyQuery filter) is now on the site and is presumably not causing any issues.
Good suggestion Facitman.
The MyQuery filter has been coded and tested will be going up tonight and I'll post when it is available.
What you will now have as part of the Cache Type selection is a radio button for Include cache types and Exclude cache types.
By default Include cache types is selected. This means any cache type you select will be INCLUDED in your MyQuery. If you leave them all blank, they will be ALL included.
If you select Exclude cache types, any cache type you select will be EXCLUDED from your MyQuery. If you leave them all blank, it will ignore EXCLUDE and will INCLUDE them all. What's the point of creating a query EXCLUDING all cache types?
That way you can select EXCLUDE and tick TrigPoints and TriPoints will be excluded from your
results.
Good suggestion Facitman.
The MyQuery filter has been coded and tested will be going up tonight and I'll post when it is available.
What you will now have as part of the Cache Type selection is a radio button for Include cache types and Exclude cache types.
By default Include cache types is selected. This means any cache type you select will be INCLUDED in your MyQuery. If you leave them all blank, they will be ALL included.
If you select Exclude cache types, any cache type you select will be EXCLUDED from your MyQuery. If you leave them all blank, it will ignore EXCLUDE and will INCLUDE them all. What's the point of creating a query EXCLUDING all cache types?
That way you can select EXCLUDE and tick TrigPoints and TriPoints will be excluded from your
results.
-
- Posts: 222
- Joined: 17 September 09 6:44 pm
- Location: Home of the cache
Re: TrigPointing
My new cache is here
http://geocaching.com.au/cache/tp0001
This is caughtatwork, aka Geocaching Australia as owner of the new TrigPoints.
NOTE:
This listing is for testing purposes.
Please edit it.
Please log it.
The cache and logs will be deleted on Friday before the real load next week.
Any problems, issues, concerns please provide feedback here.
http://geocaching.com.au/cache/tp0001
This is caughtatwork, aka Geocaching Australia as owner of the new TrigPoints.
NOTE:
This listing is for testing purposes.
Please edit it.
Please log it.
The cache and logs will be deleted on Friday before the real load next week.
Any problems, issues, concerns please provide feedback here.
- CraigRat
- 850 or more found!!!
- Posts: 7015
- Joined: 23 August 04 3:17 pm
- Twitter: CraigRat
- Facebook: http://facebook.com/CraigRat
- Location: Launceston, TAS
- Contact:
- Rigger64
- 950 or more random things achieved
- Posts: 451
- Joined: 10 November 07 11:36 pm
- Location: Seaford
Re: TrigPointing
So we can log this one regardless of not going to ths location?
- caughtatwork
- Posts: 17017
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: TrigPointing
Up and ready to use.caughtatwork wrote:The code (with the exception of the MyQuery filter) is now on the site and is presumably not causing any issues.
Good suggestion Facitman.
The MyQuery filter has been coded and tested will be going up tonight and I'll post when it is available.
What you will now have as part of the Cache Type selection is a radio button for Include cache types and Exclude cache types.
By default Include cache types is selected. This means any cache type you select will be INCLUDED in your MyQuery. If you leave them all blank, they will be ALL included.
If you select Exclude cache types, any cache type you select will be EXCLUDED from your MyQuery. If you leave them all blank, it will ignore EXCLUDE and will INCLUDE them all. What's the point of creating a query EXCLUDING all cache types?
That way you can select EXCLUDE and tick TrigPoints and TriPoints will be excluded from your
results.
- caughtatwork
- Posts: 17017
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: TrigPointing
Yep as a test. The logs will be deleted when we're done testing. You can try to archive / unarchive it too.Rigger64 wrote:So we can log this one regardless of not going to ths location?
-
- 1350 or more caches found
- Posts: 180
- Joined: 06 October 07 6:55 pm
- Location: Tumut
Re: TrigPointing
My testing completed, seems to work well from my end. Archive and disable are all good here, also (and probably most importantly) unarchiving and enabling working well. Queries also good from here and GSAK import.
Thanks
Thanks
- Facitman
- 1400 or more caches found
- Posts: 463
- Joined: 18 June 04 3:58 pm
- Location: Melbourne
- Contact:
Re: TrigPointing
Query appears to work well, include......exclude.....include.....exclude.....include....exclude... Oh, this is fun....