ioos
TCI Spiny Lobster Assessment for the past decade
Contact details
Dataset Title
TCI Spiny Lobster Morphometrics
Describe your dataset and any specific challenges or blockers you have or anticipate.
I have data on biological measures of the Spiny Lobster. However, the data is inconsistently obtained, but covers a number of years. There is concern that some data is lost with regards to the local consumption and non reporting of landings and therefore biological information as well. This is also found in our conch data.
Info about "raw" Data Files.
The "raw" data is in an excel file, large but downloadable. There are multiple tabs for other data that are related
Sounds complex, but fun! To be clear, this includes observations and morphometrics that correspond to lobster fishing? Or are they general measurements corresponding to museum/collection specimens?
Good morning,
The lobster landings are through documents taken by the officers and the also provided by the processing facilities. The morphometrics are taken as samples from the catches at the processing facilities.
Kathy Lockhart
From: Stephen Formel @.> Sent: Sunday, September 07, 2025 9:13 PM To: ioos/bio_data_guide @.> Cc: Kathy Lockhart @.>; Author @.> Subject: Re: [ioos/bio_data_guide] TCI Spiny Lobster Assessment for the past decade (Issue #302)
[https://avatars.githubusercontent.com/u/21973147?s=20&v=4]sformel left a comment (ioos/bio_data_guide#302)https://github.com/ioos/bio_data_guide/issues/302#issuecomment-3264260717
Sounds complex, but fun! To be clear, this includes observations and morphometrics that correspond to lobster fishing? Or are they general measurements corresponding to museum/collection specimens?
Reply to this email directly, view it on GitHubhttps://github.com/ioos/bio_data_guide/issues/302#issuecomment-3264260717, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BWUI6IU5ISYTNH6BDKNW7VD3RTJ3RAVCNFSM6AAAAACFBWQ4JKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENRUGI3DANZRG4. You are receiving this because you authored the thread.Message ID: @.@.>>