Joined: Aug. 2003
||Posted: Aug. 20 2003,4:58 pm
Sorry to bring back an old thread, but it doesn't seem this functionality is in yet.
I wrote a program to parse those .LOC from gc.com into something I could use, but the info is still incomplete. For instance, I want to know which caches are virtual, but the file doesn't seem to have that information in it.
I can have more than 6 characters for a waypoint name on my etrex, so I'd definitely want to label the cache type and difficulty, like so:
Which would be cache "NC0000", a virtual cache, difficulty 2.5, terrain difficulty 3. Or something like that.
If this information was in the file we downloaded, I could parse it as I choose. If it's not, then I'm up the creek.
Regarding waypoint naming schemes, beware those that would lead to collisions (like based on peoples initials, hardly unique). Also, beware that there is only so much space in there.
If the waypoints are "NCXXXX", we have 4 characters to play with. If there are 36 different characters (0-9, A-Z), that's 36^4 different possible caches; that's only 1,679,616 unique IDs. Making the waypoints with "NXXXXX" gives over 60 million unique IDs, which is significantly better. However, this increases the chances of having a collision with some other organization that uses "N" as the prefix.
One possible solution: have the navicache ID be a 5-character number using all 36 digits so you get the full 60-million. Then have a user-defined prefix letter which could default to "N" for "Navicache", but the user could change to be whatever they wanted if "N" happens to collide with something else they have.
All this being said, maybe 1.6M is enough IDs for all the active caches in the world at any one time. I fear it, though.
[After writing this and actually looking, it looks like you are doing the 5-digit ID already. Hooray!]
Edited by beej71 on Aug. 20 2003,5:00 pm