🞋 Round coordinates to ensure safe numbers

[mvillasante]

Description

• Round the coordinates to 6 decimal positions to ensure safe numbers. Seabird tracking database error
• Rename write_bl_table() -> write_birdlife_table()

Relevant commits

• ✅ Pass tests
• ♻️ Refactor: 🧑🏽‍💻 deprecation message
• 🚚 rename files: no abbreviations
• 🆙✍🏼 fix version following semver

---

Checklist for the author

• Small: The pull request has fewer than 100 lines.
• Passing: The CI pipeline is passing.
• Comments: Did we replace unnecessary comments with clear variable names, well-named functions, and small cohesive blocks?
• Complexity: Could the code be made simpler? Would another developer be able to easily understand and use this code when they come across it in the future? Is this code adding functionality that isn't presently needed?
• Design: Is the code well-designed and appropriate for your system?
• Documentation: Did the developer also update relevant documentation? Does the exposed functions have docstrigns?
• CHANGELOG.md: Are the changes recorded in this file following this standard?
• Versioning: Are version numbers updated according to semantic versioning guidelines (e.g., MAJOR.MINOR.PATCH)?
• CITATION.cff: Is the citation files included and updated following the this standard?
• Functionality: Does the code behave as the author likely intended? Is the way the code behaves good for its users?
• Interface: Any interface changes are sensible and look good.
• Naming: Did the developer choose clear names for variables, classes, methods, etc.?
• Style: Does the code follow our style guides?
• Tests: Does the code have correct and well-designed automated tests?
• YAGNI: The developer is not implementing things they might need in the future but don’t know they need now.

[devarops]

Va muy bien, @mvillasante. Aquí están mis comentarios.

• Add documentation to the function that are exported (#' @export)
• Add the CITATION.md

[devarops]

Checklist for the reviewer

• Small: The pull request has fewer than 100 lines.
• Passing: The CI pipeline is passing.
• Comments: Did we replace unnecessary comments with clear variable names, well-named functions, and small cohesive blocks?
• Complexity: Could the code be made simpler? Would another developer be able to easily understand and use this code when they come across it in the future? Is this code adding functionality that isn't presently needed?
• Design: Is the code well-designed and appropriate for your system?
• Documentation: Did the developer also update relevant documentation? Does the exposed functions have docstrigns?
• CHANGELOG.md: Are the changes recorded in this file following this standard?
• Versioning: Are version numbers updated according to semantic versioning guidelines (e.g., MAJOR.MINOR.PATCH)?
• CITATION.cff: Is the citation files included and updated following the this standard?
• Functionality: Does the code behave as the author likely intended? Is the way the code behaves good for its users?
• Interface: Any interface changes are sensible and look good.
• Naming: Did the developer choose clear names for variables, classes, methods, etc.?
• Style: Does the code follow our style guides?
• Tests: Does the code have correct and well-designed automated tests?
• YAGNI: The developer is not implementing things they might need in the future but don’t know they need now.
• Good Things: If you see something nice in the pull request, tell the developer, especially when they addressed one of your comments in a great way.

[devarops]

@mvillasante Muchas gracias for addressing all my comments. I liked that you included the ORCID to the authors and their GitHub usernames. Good work!