Search results

Page title matches

• Tucson format
  ...ogies with not exactly the same syntax). The name comes from the city of [[Tucson]] in [[Arizona]]. ==Basics of the Tucson format for ring width data==
  23 KB (2,324 words) - 12:25, 11 January 2017
• Tucson-format
  #Redirect[[Tucson format]]
  26 bytes (3 words) - 10:57, 11 June 2009

Page text matches

• .crn
  ...sed for a variant of the [[Tucson format#The Tucson chronology .crn format|Tucson format]], used by the [[ITRDB]] for [[Chronology|chronologies]].
  223 bytes (32 words) - 23:40, 29 January 2010
• Filename extensions
  *[[.crn]] Tucson chronology format, used by ITRDB, CDendro *[[.dec]] Obsolete extension for Tucson format, commonly used by early versions of CDendro. For compatibility with
  1 KB (146 words) - 23:26, 22 May 2010
• Decadal
  #Redirect[[Tucson format]]
  26 bytes (3 words) - 21:34, 30 December 2009
• .dec
  #Redirect[[Tucson format]]
  26 bytes (3 words) - 16:15, 16 May 2009
• Tucson-format
  #Redirect[[Tucson format]]
  26 bytes (3 words) - 10:57, 11 June 2009
• Rwl
  #Redirect[[Tucson format]]
  26 bytes (3 words) - 15:52, 16 May 2009
• Tuc
  #Redirect[[Tucson format]]
  26 bytes (3 words) - 15:53, 16 May 2009
• .rwl
  #Redirect[[Tucson format]]
  60 bytes (6 words) - 21:39, 23 June 2009
• .tuc
  #Redirect[[Tucson format]]
  61 bytes (6 words) - 21:39, 23 June 2009
• Cofecha
  ...It is a part of [[The Dendrochronology Program Library]]. It works with [[Tucson-format]]ed dendro data files.
  602 bytes (93 words) - 22:49, 23 June 2009
• Corina
  * Support for standard dendro file format including [[Tucson format|Tucson]], [[Heidelberg format|Heidelberg]] and [[TSAP format]].
  668 bytes (88 words) - 20:52, 23 June 2009
• TRIMS
  ...''Tree Ring Incremental Measuring System'', developed by Madera Software, Tucson, Arizona, released 1988.
  141 bytes (15 words) - 23:10, 1 January 2010
• CDendro naming standard
  .... Otherwise the identities will be truncated when the data is written to a Tucson format file.
  921 bytes (159 words) - 18:28, 22 May 2009
• WSL Dendro Database
  ...vailable also by the [[ITRDB]]. The data format used in this database is [[tucson format]] with the [[filename extension]] [[.tuc]].
  767 bytes (111 words) - 22:49, 19 June 2009
• Småland
  ...available online]. [http://taxelson.se/dendro/LofstrandSmaland.rwl Data in tucson-format] ([[PISY]])
  2 KB (257 words) - 12:57, 12 November 2019
• Tucson format
  ...ogies with not exactly the same syntax). The name comes from the city of [[Tucson]] in [[Arizona]]. ==Basics of the Tucson format for ring width data==
  23 KB (2,324 words) - 12:25, 11 January 2017
• CATRAS
  ...re are programs available (e.g. [[Convert5]]) to convert such files into [[tucson-format]].<ref>See list in '''Henri D. Grissino-Mayer's'''
  6 KB (780 words) - 17:07, 20 March 2012
• List of references useful for violins
  *{{itrdb|swit177|europe|w}}<ref>The [[tucson format]] of this file is special</ref>, 987-1976, Lauenen + div. Stao CH, 1 ...liff<ref>Syntax error: the end marks should be -9999 and not 999 in this [[Tucson-format|rwl-file]].</ref>
  11 KB (1,469 words) - 20:11, 18 May 2011
• SNorwQ
  In some reports the data is in a [[.fh]]-like (or [[Tucson-format|Tucson]]-like format) which needs some manual editing to become readable by [[CDen
  19 KB (2,733 words) - 00:44, 13 December 2017

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)