Difference between revisions of "Virtual GPS"
m (Don't see a point in linking an old QA with incorrect info so I removed it while correcting a typo.) |
(→Share corrected coordinates) |
||
| Line 30: | Line 30: | ||
=== Details === | === Details === | ||
| − | Only geocaches included in the VGPS | + | Only geocaches that were included in the VGPS when the sharer selects "Share" will be updated for the receiver when selecting "Fetch". If more geocaches are added to the VGPS later, the sharer must select "Share" again to make the corrected coordinates for the new caches available for the receiver (who has to run another "Fetch"). This also applies when removing and re-adding a geocache to the VGPS. |
| − | Corrected coordinates are, as usual, looked for both in Personal cache notes (the first parsable has | + | Corrected coordinates are, as usual, looked for both in the Corrected coordinates field and the Personal cache notes field (the first parsable has prescedence). |
| − | Project-GC's Share corrected coordinates system never overwrites a solution for the Receiver. If the Receiver already has corrected coordinates those are kept for the Receiver. | + | Project-GC's Share corrected coordinates system never overwrites a solution for the Receiver. If the Receiver already has corrected coordinates those are kept for the Receiver (which means that if the receiver has an incorrect solution, it will be kept instead of an offered correct solution - Project-GC doesn't know which solution is better). |
| − | The Fetch mechanism writes to the | + | The Fetch mechanism also writes to the receiver's Personal cache note. If there already is content Project-GC puts its text at the beginning. It will look something like: |
PGC-VGPS (<vgpsId>,<timestamp>): <coordinates> | PGC-VGPS (<vgpsId>,<timestamp>): <coordinates> | ||
Latest revision as of 17:34, 10 February 2024
This page is a Work in progress and needs severe fixes.
Feel free to contribute by editing the page. When it has the information needed in a readable form and in a decent formatted way, remove the FIXME template-tag.
The Virtual GPS system is one of Project-GC's core features, and also one of the more powerful ones. Imagine a shopping cart for Geocaches, that's what Virtual GPS is. Where ever you are at Project-GC, you can add hand picked, or a group of, geocaches into a list. This list can layer in be sorted, filtered, shared and exported. It's the perfect tool to handpick target geocaches for your trips, badges or challenges. Only Project-GC's paid members can use this feature.
Contents
Creating a list
Details to follow
Filtering
The caches in the Virtual GPS can be filtered by the following:
- Remove found
- Remove owned
Sorting
The caches in the Virtual GPS can be sorted based on:
- By ascending Cache ID
- If the user has found them
- Alphabetically by GC-code, cache name, type, size, cache owner, country, region, county, placed by name, added by, or any of the usernotes entered
- By ascending cache ID, difficulty, terrain, latitude, longitude, elevation, number of finds, number of FPs, FP percent, or Wilson score
- If the cache is locked, archived, disabled, or premium only
- By earliest hidden date, publish date, last find date, or last archive date
- Latest logs - how many of the last 7 logs were finds
- Source page / link - the page the cache was added from. Source link gives the link rather than the page title.
Sharing
Flow
- Add geocaches
- Sharer: Manage list -> Share corrected coordinates -> Share
- Receiver: Manage list -> Share corrected coordinates -> Fetch
Details
Only geocaches that were included in the VGPS when the sharer selects "Share" will be updated for the receiver when selecting "Fetch". If more geocaches are added to the VGPS later, the sharer must select "Share" again to make the corrected coordinates for the new caches available for the receiver (who has to run another "Fetch"). This also applies when removing and re-adding a geocache to the VGPS.
Corrected coordinates are, as usual, looked for both in the Corrected coordinates field and the Personal cache notes field (the first parsable has prescedence).
Project-GC's Share corrected coordinates system never overwrites a solution for the Receiver. If the Receiver already has corrected coordinates those are kept for the Receiver (which means that if the receiver has an incorrect solution, it will be kept instead of an offered correct solution - Project-GC doesn't know which solution is better).
The Fetch mechanism also writes to the receiver's Personal cache note. If there already is content Project-GC puts its text at the beginning. It will look something like:
PGC-VGPS (<vgpsId>,<timestamp>): <coordinates>
Importing
Users can import geocaches from Bookmark lists existing at Geocaching.com. Note that the bookmark list needs to be public or shareable, except for the users own lists which can be private.
Exporting
The caches can be exported in the following ways:
- Map
- Gallery
- Bookmark list
- CSV file
- GPX file
