Jump to content

churinga

+Premium Members
  • Posts

    23
  • Joined

  • Last visited

Everything posted by churinga

  1. Android Car hab ich nicht wirklich zum laufen gebracht und ich will ja mit dem Amundsen navigieren und nicht mit dem Handy
  2. also draussen in den pampas gibt's des öftern keine adresse, sondern höchstens koords einer geeigneten parkfläche. die idee vom "ich hab alle dosen des jagdbezirks auf dem navi" ist eigentlich dass spontan entschieden werden kann was angefahren wird, ohne dass das vorher jedes mal auf's gerät geladen wird. ausser dem kann ich, wenn alle dosen auf dem navi angezeigt werden, auch mal irgendwo spontan bei einer wegranddose anhalten. mein ursprünglicher wunsch war eigentlich, das anzufahrende ziel per bluetooth vom handy auf's navi zu übertragen, so wie das z.b. bei garmin geräten möglich ist, aber diese möglichkeit scheint das amundsen ja leider nicht zu bieten ;-(
  3. ist denn vcard nicht vor allem zum übernehmen von adressen geeignet? hat doch bei angabe von koords bloss eine grobauflösung (hundertstel grad oder so) oder seh ich das falsch? hab einige bedenken dass ich da einen datensatz von 500'000 poi als vcard importieren kann. hat da jemand erfahrung?
  4. ich hab neu ein amundsen navi in meinem cachemobil. leider hab ich noch nirgends ne anleitung gefunden wie ich meine gc pois von gsak aufs amundsen rüber krieg. sind aktuell so um die 500'000. hab bislang auf's garmin autonavi vertraut, aber da ich nun neu ein eingebautes navi hab würde ich eigentlich gerne dieses verwenden. alle anleitungen die ich bislang gefunden hab basieren auf irgendwelchen onlinetools von vw oder skoda, die jedoch nicht mehr verfügbar sind. gibt's einen weg die daten aus gsak in eine form zu bringen die das amundsen versteht? und wenn ja, wo kopier ich die datei dann hin damit das amundsen sie findet? ich hoffe dass da jemand erfahrung hat. das amundsen scheint ja auf den strassen europas nicht eben selten unterwegs zu sein ;-)
  5. it's a fujitsu-siemens pocket loox 718, but there are lots of other pocket pc models around with this display resolution. so i think it's really a requirement to support this. as it's 2x the resolution of a standard ppc in both directions, i think this shouldn't be such a big thing to realize. btw: all software i used until now had no problem with this resolution.
  6. how do i have to setup Wherigo to run on a pocket pc with a vga display (640x480)? just installing it gives horrible graphics and text is not readable!
  7. i agree that it makes not a lot of sense, to get waypoints without coords as individual child waypoints. but nevertheless, i think such waypoint data should be included in the main cache description of a pocket query, in the way i see it on the online html page. how can i get an official statement from Groundspeak about this? i think if Groundspeak is not willing to do any changes to pocket queries, this should be written in the rules for additional waypoints, as users of pocket queries won't get the full cache description, the way it is today.
  8. When getting a pocket query by email, this contains 2 files - a main waypoint file and a child waypoint file, containing (almost) all child or additional waypoints. why almost? it looks like only those waypoints which have public coordinates are included. this may be a problem! take e.g. the cache GC10K2Y. this cache has 6 additional waypoints, numbered 01-06. waypoint 01 is parking coords and has public coords. this waypoint is contained in the child waypoint file. waypoints 02-06 have no public coords, but have the 'questions to answer' attached. these waypoints are not contained in the child waypoint file, but the text, attached to them is also missing in the main waypoint file, i.e. if i base on pocket queries, i have no chance to solve this cache, as i do not get the questions to answer. i think there are two possible ways for Groundspeak to solve this. - also child waypoints without coords are included into the child waypoint file - text, attached to waypoints, is also included into the main cache description i hope that groundspeakers read this and provide a quick solution for this problem.
  9. naviguesser74, where can i find these utilities? do you have a link? will such a spreadsheet work on a pocket pc? thanx! churinga
  10. i'm looking for a tool, calculating azimuth and distance between two waypoints (and vice versa), as described above, but running on a POCKET PC! is there anything available?
  11. when trying to upload a spoiler image for a new cache, i always get the message: Server Error in '/' Application. There is not enough space on the disk. is there a problem with the Groundspeak server?
  12. it looks like since about 2 days, the pocket queries i get have no more log entries. there is just the name of the cacher, who loged, but the text is missing. is there actually a problem with pocket queries, or what do i have to do to get them again with all logs? thanx!
  13. really a great job! first, i didn't like gsak at all, but now, the more i use it, the more i like it!! and the support is almost better than perfect! i just updated from b56 to b57, and right, the renaming of the pq's according to the subject line works. unfortunately, this does not reflect in the statistics. these still show the number instead of the pq name - would be really nice cosmetics, if these could also be changed to a more senseful name ;-) thanx for the great job!
  14. i'm not yet on beta56 (still have beta51) but i don't think that there have been any changes with the mail download. my reports do not really concern errors, but options i would like to see in future releases: 1: gsak downloads a few pocket queries a day, and places the files in the selected folder. all these files get just meaningless numbers as filenames, not really nice to find out which one of the queries hit it's head at 500 waypoints. does it really make sense to use numbers as filenames? wouldn't it be better to name the files according to the subject line of the mail, the file is extracted from? i think the files would be easier to be handled by humans ;-) 2: all pocket queries, downloaded by gsak, are placed within the same folder, so after a few days, there are lots of files there. unfortunately, gsak seems not only to import the actually downloaded files, but all files it finds within this folder, and all it's subfolders, taking a lot of time. isn't it possible to let gsak only import the files it has just downloaded, ignoring all files it has already imported earlier? or it might download the files to a temporary import folder, moving them to the final download folder right after importing them. so it only finds the actually downloaded files for import. what do you think about adding these features? churinga
  15. maps in gsak -------------------- than problem would be to get the maps on the local harddisk, and link them to the gsak note, together with the spoiler images. is there a tool grabbing the maps, based on a gpx file (or a loc file)? is there a gsak macro linking these map files?
  16. Add Maps into Cache Descriptions ---------------------------------------------- is there a way to add maps into cache descriptions? using spoiler sync and a gsak script, it is possible to add spoiler pictures to gsak's html output. is there a way to also add maps?
  17. Smaller Font in HTML Output --------------------------------- I'm actually trying to switch from yagcu to gsak, to generate my palm database. using yagcu, i got a font size, allowing me to read the cache description on the palm without horizontal scrolling for each line (html page width did fit on palm display because of small font). using gsak, the html font is really big, so i have to horizontal scroll for each line. how can i reduce the html font size for gsak? btw: i tried this with isilox for converting to palm database.
  18. when i do a pocket query, which results in more than 500 waypoints, how will the PQ generator decide which 500 WPs i will get? will i get the 500 nearest? will it decide randomly? will i get the same 500 each day? will i get the first 500 one day, and the next 500 the other day? any info? thanx! churinga
  19. is there a printable manual for gsak? (i'd like to read the manual while travelling)
  20. i first did geocaching, using a garmin gps45. that was not very satisfying, as i never got to an accuracy below 35ft in the open, rising up to 70ft under trees. so next step was to buy a garmin vista, which people recommended for geocaching. this unit is quite good in the open, but in wooden areas, i often have no satellite, or reliability is not very high. so now, i had the chance to test a gps60cs for one day (results see below) and really think about switching to such a unit myself. please read my 'test' below. what do you think about my 'test'? what do you recommend? should i buy a gps60cs, or is there anything even better, especially more sensitive? can sensitivity of the 60cs be increased with an external antenna? i feel like the vista really bluffs. i think that it usually shows a better reliability than it really has: i.e. it tells me the cache is within a circle of 6ft, with a reliability of 15ft, i.e. i have to search within a circle of 21ft. but i expect that the reliability is only about 30-50ft and i would have to search within an circle of 36-56ft. what is actually the most recommended device for geocaching? is it better to carry a single gps device with high reliability, or several units of lower cost? thanks for your hints! churinga ------------------------------------------ MY TEST RESULTS: vista stands for garmin vista with latest firmware 60cs stands for garmin gps 60cs heading for the 1st cache, i got a bearing of about 20deg in difference from the 2 units, even if i recalibrated the compass. in the open, both units reported a reliability of 15ft which seems to be quite well, as i think i did not get any egnos/waas data, even if this should be working now and bot units are expected to support it. entering the forest, reliability got instable and showed between 20-40ft. then, the 60cs indicated me, that i'm about 10ft from the cache, while vista indicated that i have to go about 150ft further. the reality is, that i was standing about 6ft from the cache, and it was place in the direction the 60cs showed me. the vista first sent me the 150ft further, to a more open area in the forest, then about 100ft back. both units showed a reliability of about 25-30ft. that's it. heading for the 2nd cache, i still had the 20deg difference in bearing (must be because of the compass calibration). this cache was located in an open area of about 300x300ft (all trees cut down) within a forest. in this location, both units showed me more or less the same results (indicated reliability about 20ft): standing on the track, they indicated me that the cache is about 15ft north - going 2 steps north, they indicated me that it is 45ft south - going 2 steps south, they indicated me that it is 15ft north - and so on... it really was about 20ft south. 3rd cache, a light wooden area on top of a hill, both units show about 20ft reliability. while one unit indicated the position to be about 20ft north, the other indicated it to be 20ft south...while i was about to stand on the cache. 4th cache. area with lots of high trees. bearing of both units were really instable. the 60cs sent me around in an area of about 100x100ft, while the area with the vista was about 200x200ft. both units showed the same reliability (about 30ft).
  21. i'm looking for a gps for geocaching. it should be accurate, robust, and give everything i need. so i think i would like to have waas and a compass. looking through ads and forums, i found the following gps to match my requirements: geko 301: + small + relatively cheap - small display - bad compass, as only working when completely horizontal - short life time of nimh batteries when compass on - bad operation of battery compartment - aaa batterie size vista: + good display + aa battery size - bad compass, as only working when completely horizontal - not really cheap sportrak color: + good compass - expensive meridian platinum: + good compass - really expensive what more pro's and con's? which one is the most recommended? are there other 'relatively cheap' gps with compass? any experience on battery lifetime? thanx!
  22. what special screen for geocaching do the gps60 and gps76 have?
  23. until now, i use a garmin gps45. this unit hat 2 things i do not really like: - position is shown with a tolerance of about 35ft at it's best. when entering a forest, tolerance increases to about 70ft, which is quite a lot to find a cache. - to get a reliable bearing, you have to walk at about 2mph, or the bearing indicator directs you to 'anywhere'. so i think about buying another gps device, and limit the usage of the gps45 to the car, where it works quite well with the external antenna. which gps receiver is the most recommended for geocaching? i read about the new garmin geko 301. it has waas, to reduce tolerance downto 3-10ft, as well as an integrated compass, to get reliable bearing even when standing still (according to advertisement). does anyone have experience with this device? is another one more recommended? thanks for your help! churinga
×
×
  • Create New...