Have you ever opened a dendro .pos file with a text editor like e.g. Notepad++ or Epsilon and compared it with what you see on screen with CooRecorder? Here is some basic info on how points are represented:
You can add seasonwood points and even a label:
Here comes a selection from the .pos (text) file created from the second image above.
Labels are very useful as you can easily see how a line in the text file corresponds to a labeled point in the image.
Be aware of the decimal point (.) which is used as such, and the comma (,) which is used as a separator between X,Y coordinates.
The "D" was originally used to mark a "disabled" point but was later also used together with the "W" tag to tag a Season wood point.
Sounds inconsistent but was done so to keep compatibility with older versions of CooRecorder which could not read season-wood files.
There is also a format for adding various comments to the .pos file and also of blue channel data.
Experiments is probably the way for you to find out how this works.
CooRecorder can be used for many more things like measurements on bee wings. And even for software development where
you can "tag" a screen with positions for various items and use the "label-field" text to specify what should be present at that point.
I have used that for a few process supervision systems built in Visual Basic!
Within dendrochronology, CooRecorder was also used to retrieve/digitize the published ring width curves (!) by Ernst Hollstein
https://www.cdendro.se/forfun/dendro/ho ... /index.htm
CooRecorder has been on the market since 2005 (almost 20 years) and the format of its .pos files has been successively updated.
If you are only interested in ring widths, then consider to export .pos file data as .wid file data for your further processing.
