Add template files in

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,17 @@
+## Expected Behavior
+
+
+## Actual Behavior
+
+
+## Steps to Reproduce the Problem
+
+  1.
+  1.
+  1.
+
+## Specifications
+
+  - Version:
+  - Platform:
+  - Subsystem:

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+# One-line summary
+
+> Issue : #1234 (only if appropriate)
+
+## Description
+A few sentences describing the overall goals of the pull request's
+commits.
+
+## Types of Changes
+_What types of changes does your code introduce? Keep the ones that apply:_
+
+- New feature (non-breaking change which adds functionality)
+- Bug fix (non-breaking change which fixes an issue)
+- Configuration change
+- Refactor/improvements
+- Documentation / non-code
+
+## Tasks
+_List of tasks you will do to complete the PR_
+  - [ ] Created Task 1
+  - [ ] Created Task 2
+  - [ ] To-do Task 3
+
+## Review
+_List of tasks the reviewer must do to review the PR_
+- [ ] Tests
+- [ ] Documentation
+- [ ] CHANGELOG
+
+## Deployment Notes
+These should highlight any db migrations, feature toggles, etc.

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at opensource@zalando.de. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,61 @@
+# Contributing to LAS.jl
+
+**Thank you for your interest in LAS.jl. Your contributions are highly welcome.**
+
+There are multiple ways of getting involved:
+
+- [Report a bug](#report-a-bug) 
+- [Suggest a feature](#suggest-a-feature) 
+- [Contribute code](#contribute-code) 
+
+Below are a few guidelines we would like you to follow.
+If you need help, please reach out to us by opening an issue.
+
+## Report a bug 
+Reporting bugs is one of the best ways to contribute. Before creating a bug report, please check that an [issue](/issues) reporting the same problem does not already exist. If there is such an issue, you may add your information as a comment.
+
+To report a new bug you should open an issue that summarizes the bug and set the label to "bug".
+
+If you want to provide a fix along with your bug report: That is great! In this case please send us a pull request as described in section [Contribute Code](#contribute-code).
+
+## Suggest a feature
+To request a new feature you should open an [issue](../../issues/new) and summarize the desired functionality and its use case. Set the issue label to "feature".  
+
+## Contribute code
+This is an outline of what the workflow for code contributions looks like
+
+- Check the list of open [issues](../../issues). Either assign an existing issue to yourself, or 
+create a new one that you would like work on and discuss your ideas and use cases. 
+
+It is always best to discuss your plans beforehand, to ensure that your contribution is in line with our goals.
+
+- Fork the repository on GitHub
+- Create a topic branch from where you want to base your work. This is usually master.
+- Open a new pull request, label it `work in progress` and outline what you will be contributing
+- Make commits of logical units.
+- Make sure you sign-off on your commits `git commit -s -m "adding X to change Y"` 
+- Write good commit messages (see below).
+- Push your changes to a topic branch in your fork of the repository.
+- As you push your changes, update the pull request with new infomation and tasks as you complete them
+- Project maintainers might comment on your work as you progress
+- When you are done, remove the `work in progess` label and ping the maintainers for a review
+- Your pull request must receive a :thumbsup: from two [maintainers](MAINTAINERS)
+
+Thanks for your contributions!
+
+### Commit messages
+Your commit messages ideally can answer two questions: what changed and why. The subject line should feature the “what” and the body of the commit should describe the “why”.  
+
+When creating a pull request, its description should reference the corresponding issue id.
+
+### Sign your work / Developer certificate of origin
+All contributions (including pull requests) must agree to the Developer Certificate of Origin (DCO) version 1.1. This is exactly the same one created and used by the Linux kernel developers and posted on http://developercertificate.org/. This is a developer's certification that he or she has the right to submit the patch for inclusion into the project. Simply submitting a contribution implies this agreement, however, please include a "Signed-off-by" tag in every patch (this tag is a conventional way to confirm that you agree to the DCO) - you can automate this with a [Git hook](https://stackoverflow.com/questions/15015894/git-add-signed-off-by-line-using-format-signoff-not-working)
+
+```
+git commit -s -m "adding X to change Y"
+```
+
+
+
+
+**Have fun, and happy hacking!**

CONTRIBUTORS.md

@@ -0,0 +1,8 @@
+# Project Contributors
+
+All external contributors to the project, we are grateful for all their help 
+
+## Contributors sorted alphabetically
+
+- **[Ben Curran](https://github.com/BenCurran98)**
+  - Repository Author

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Fugro NV
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

MAINTAINERS

@@ -0,0 +1,5 @@
+Ben Curran <b.curran@fugro.com>
+Isabella Kieu <i.kieu@fugro.com>
+Megan Dawson <m.dawson@fugro.com>
+Shane Cheng <sh.cheng@fugro.com>
+Zhihao Qiao <z.qiao@fugro.com>

README.md

@@ -1,6 +1,44 @@
-# LAS.jl
-A Julia package for reading and writing LAS data
+# LAS.jl 
 
 [![CI](https://github.com/fugro-oss/LAS.jl/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/fugro-oss/LAS.jl/actions/workflows/ci.yml)
-[![](https://img.shields.io/badge/docs-stable-blue.svg)](https://fugro-oss.github.io/LAS.jl/stable)
-[![](https://img.shields.io/badge/docs-latest-blue.svg)](https://fugro-oss.github.io/LAS.jl/dev)
+[![](https://img.shields.io/badge/docs-latest-blue.svg)](https://fugro-oss.github.io/LAS.jl/dev)
+
+A Julia package for reading and writing *LAS* data. *LAS* is a public file format for saving and loading 3D point cloud data, and its source repository can be found [here](https://github.com/ASPRSorg/LAS). This package currently supports *LAS* specifications 1.1-1.4 (see [here](https://www.asprs.org/wp-content/uploads/2019/03/LAS_1_4_r14.pdf) for the 1.4 spec.)
+
+Some key features included in this package are:
+* High-level functions for reading and writing *LAS* data in tabular formats using [TypedTables.jl](https://github.com/JuliaData/TypedTables.jl)
+* Automatic detection of *LAS* point formats from data
+* Reading and writing *Julia*-native structs as *Variable Length Records* (*VLRs*) and *Extended Variable Length Records* (*EVLRs*)
+* Easy manipulation of file header properties
+
+
+## Getting Started
+
+These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. Simply run:
+
+```
+using Pkg
+Pkg.add("git@github.com:fugro-oss/LAS.jl.git")
+using LAS
+```
+
+And you're ready to go!
+
+## Contributing
+
+Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our process for submitting pull requests to us, and please ensure
+you follow the [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).
+
+## Versioning
+
+We use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/fugro-oss/LAS.jl/tags). 
+
+## Authors
+
+* **Ben Curran** - *initial author of repo* - [@BenCurran98](https://github.com/BenCurran98)
+
+See also the list of [contributors](CONTRIBUTORS) who participated in this project.
+
+## License
+
+This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details