Jump to content

ExTechOp

+Premium Members
  • Posts

    62
  • Joined

  • Last visited

Everything posted by ExTechOp

  1. I mistakenly logged a travel bug drop on a wrong date, and found that to be able to change the log date, the system also requires that you have to add a comment. That's a bit silly, as you can't create a drop log with comments in the first place!
  2. As I previously asked someone else, can you name a place where YYYY-DD-MM is commonly used in all-numbers dates, as neither I nor Wikipedia has heard of such? USA commonly uses the "middle-endian" format of MM-DD-YY.
  3. Only in those areas where the Y-M-D convention is used. There are areas where the convention is Y-D-M, in which case the example you give translates to 7th January, 2007. I agree that Y-M-D makes a lot more sense, but it is not universal.Would you care to name a place (on this planet, please) where Y-D-M is commonly used in all-numbers dates, as neither I nor Wikipedia has heard of such? Being a part-time website designer, I can see there is the not-so-small problem of having the month code change from 1 to 4 characters in length, and the fact that in many fonts all digits are the same width (making tables line up nicely), but I, V and X are different. BTW, I've seen roman numerals being used in gravestones from the 1700's and 1800's, pretty much the way you propose, though often in a very obscure way like 18-27/X-08 (which would mean 27th of October 1808). My original suggestion was only for the places on the website where all-numbers dates are used for brevity, like when listing several caches that match a given criteria on one page. Places where the date can be written out "in full" are of course a whole different kettle of fish. I18N is a horrible mess, you don't want to go there. Why do I suddenly feel like I'm reading the "Freedom2Measure" website? IF you had actually read the ISO 8601 link that I've now twice provided, you would have found that the standard is fine with giving YYYY-DD-MM as a date stamp in places where no time information is required.
  4. The whole geocaching site is kinda wonky at the moment, maybe that's it.
  5. I'm so glad you looked up the ISO 8601 link I put in my post; "ISO 8601 prescribes a four-digit year to avoid the year 2000 problem." Thus, the ISO 8601 date for today (Finland is UT+3) is 2007-07-01 which doesn't really leave much room for confusion anywhere in the world.
  6. I assume this means you've never heard of GLONASS or EGNOS nor seen a receiver that can use multiple systems? I would also like to point out that one of the reasons the Galileo system is so delayed is that the US Government officially stated in 2002 that they still wanted to have selective availability if need be.
  7. A quick hack (cribbed from the TB Forum): open the travel item home page, and edit the URL, replacing details with edit and you'll get the edit page.
  8. Well, clear to all who read English. If "7th-Feb-2007" became the standard, wouldn't that also become an issue for non English speakers? I know the months in German, and they are close enough to English that it should not be a problem. But I have no clue how close any other language is.For example, the month names in Finnish have nothing to do with the romance language -originated versions: tammikuu, helmikuu, maaliskuu, huhtikuu, toukokuu, kesäkuu, heinäkuu, elokuu, syyskuu, lokakuu, marraskuu and joulukuu. And, generally speaking, three-letter abbreviations for month names are not used and look extremely odd when forced on us by too-rigid computer systems. I would prefer to see the ISO 8601 format in use, it is at least fairly well understandable to everyone on the planet. Of course the best alternative would be for the date format to be selectable per user, just like the distance units are. I believe one of the reasons for the existence of Geocaching.ru is that at the time, the Russians found Geocaching.com to be lacking in support for non-latin character sets and non-american notations (like the distance, maybe also the date format). I know these things had a part in the birth of Geocaching.fi, which has a cache owner-maintained "backup" of Finnish cache listings from Geocaching.com. Developments like this of course in the end can mean this hobby ends up being split up into numerous non-connected national niches, which is not good for anyone.
  9. What I find makes it even more confusing is that all traveller events (travel bug and geocoin picks, drops and discoveries) get added to the start of the daily listing in forward chronological order, just opposite to the way cache finds are listed. I suspect this is the way it was originally hacked together, and "everyone" is so used to it the geocaching.com crew does not feel comfortable changing it. I wouldn't complain, pretty please?
  10. Currently, the only choice for the date format on the website is mm/dd/yyyy (which is sometimes called "middle-endian"). This is a format commonly used in the United States, Canada, Palau, Philippines and Micronesia. The rest of the world mostly uses either dd/mm/yyyy or yyyy/mm/dd (see Wikipedia for more on the subject). Currently it is possible to select per-user the measurement units (metric/imperial) shown on the website, would it be possible to have the date format be a similar selectable feature in "account details"?
  11. Kaksi kysymystä:1) Mielestäni on melkoista hölmöilyä laittaa kätkö jossa on jo paljon findeja takaisin hyväksyntäjonoon, eikö ole mitään mahdollisuutta pakottaa kätköä vaikka disabloiduksi? 2) Onko jatkossa tarkoitus, että minkäänlaisissa vaarallisissa paikoissa olevia kätköjä ei enää hyväksytä -- tähän saakka virallisina pitämissäni guidelineissä poikkeuksia on tehty vain rautateiden lähellä olevien kätköjen suhteen? Mikäli kyseessä on uusi virallinen hyväksyntälinja, voisiko asian todellakin saada ohjeistukseen ettei tarvitse mennä tällaiseen pelleilyyn? Mikäli kyseessä on Captain Morganin oma idea, voisiko tämänkin saada selvästi sanottua?
  12. When I was reporting a cache as needing maintenance, I mistakenly initially entered a second "found" log. When I corrected this by changing the log type, the attribute "needs maintenance" did not get set for the cache, nor did I get the warning one usually gets about logging "needs maintenance". The log did get save normally, though.
  13. Good for "them" if they did, there are very few things I find as annoying as having a sound file endlessly squeaking away while I'm reading a web page. Only animated images come close...
  14. In spite of having selected kilometers as my distance unit, travelbug travel history is still shown in miles. Would it be possible to fix this to be the same unit as is used everywhere else?
  15. We will probably be visiting New England some time in the autumn, and I'm looking for good digital topo maps of the region. As the trip will be at most a couple of weeks, I would prefer not to buy software which will probably be obsolete by the next time we visit. Here in Finland, the cheapest (free!) way to get high-quality digital topo maps for use in a PDA or such equipment is to access the National Land Survey website "Citizen's MapSite" using a piece of python software called fetch_map which extracts the map squares, removes the watermarks, and combines the small image squares into a larger calibrated map which can then be loaded into your equipment with OziExplorer or similar software. Is there a similar piece of software to extract info from the USGS TopoZone or other similar online maps?
  16. Kuinka yhteensopiva tällaisen eventin järjestäminen on kapineen goalin kanssa?
  17. Since there is a ready almost-working feature on the website, why not use it? In this case, we were clambering on a terrain 4 cliffside through which a 6-lane highway is cut about 20 meters down. The calculated point of the mystery seems to erroneously point down between the lanes, and I want to make sure that the people looking for it start on the correct side of the highway. Otherwise they'll have to climb down and walk quite a way to get around to the other side! Also, the cliffside is riddled with nooks and crannies, and then there's the undergrowth on the hillside, so looking for a "small" cache is pretty bad, specially given the terrain rating. If the cache owner had updated the point appropriately based on earlier logs, there would be no reason to post this info, but it seems he's not terribly active these days -- so I'm mostly trying to help other cachers with my log.
  18. When you log a find for mystery where the end point seems to be a bit off, you of course can't include the correct end point with your log. Until now, I've assumed you could log a small "delta" (difference) value as the location. Turns out this mostly works, but now I ended up logging a cache where the difference was N0°0.003' and E0°0.017' (around 25 meters off in these corners of the woods). On the website this was displayed as: Being a programmer I can sorta figure out where this comes from, but of course 0°0.003' is not 3E-05° since we are talking base-60 stuff here. A fix for the website so that it is able to display the difference as it was entered would be fine.
  19. Try out Decimal Primes -- it depends on your background if it's extremely hard or trivial for you.
  20. We either log them as we find them using my Nokia 7710, or then just jot down small notes on the cache printouts we normally use.
  21. When you log a find for mystery where the end point seems to be a bit off, you of course can't include the correct end point with your log. Until now, I've assumed you could log a small "delta" (difference) value as the location. Turns out this mostly works, but now I ended up logging a cache where the difference was N0°0.003' and E0°0.017' (around 25 meters off in these corners of the woods). On the website this was displayed as: Being a programmer I can sorta figure out where this comes from, but of course 0°0.003' is not 3E-05° since we are talking base-60 stuff here. Just being able to display the difference as it was entered would be fine.
  22. ExTechOp

    Date Format

    Using the ISO 8601 standard convention of yyyy-mm-dd would have an advantage of not having to remember english month names -- many languages use quite similar (latin-derived) names, but for example finnish does not.
  23. ExTechOp

    Date Format

    I'm sure this has been requested several times before, but here it is again: make the date format an user-adjustable parameter like the local timezone and the miles/kilometers setting are. Living in Finland, we normally use day-month-year, and in other parts of the globe year-month-day is also very popular. The US system of using month-day-year can be very confusing for people from other parts of the world unless one stops to think about it.
  24. Deletoin sen pois hölmöilynä, ei tuo "Juu" ole missään tapauksessa riittävä log entry.
  25. Myöskään muinaismuistoalueella olevia kätköjä ei kannattane arkistoida, koska Morganin oma GCE78D on yksi sellainen. Onkos luvat varmasti kunnossa? 295/1963 Muinaismuistolaki 1 luku Kiinteät muinaisjäännökset. 1§ Kiinteät muinaisjäännökset ovat rauhoitettuja muistoina Suomen aikaisemmasta asutuksesta ja historiasta. Ilman tämän lain nojalla annettua lupaa on kiinteän muinaisjäännöksen kaivaminen, peittäminen, muuttaminen, vahingoittaminen, poistaminen ja muu siihen kajoaminen kielletty.
×
×
  • Create New...