Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v2.0.0 #14

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/remark.yaml
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
plugins:
# Support Github-flavored Markdown
- remark-gfm
# Check links
- validate-links
# Apply some recommended defaults for consistency
Expand Down Expand Up @@ -37,7 +39,7 @@ plugins:
- - remark-lint-unordered-list-marker-style
- '-'
- - remark-lint-list-item-indent
- space
- one
# Tables
- remark-lint-table-pipes
- remark-lint-no-literal-urls
14 changes: 9 additions & 5 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,21 +1,24 @@
# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

### Added
## [v2.0.0] - 2024-08-21

### Changed

- Required properties of type `string` require a minimum length of `1`.

### Deprecated
- Updated to "Pilot" maturity
- Required properties of type `string` require a minimum length of `1`
- `pc:schemas` is no longer required

### Removed

- `pc:encoding` because there is an encoding key in the asset

### Fixed

- Fixed JSON Schema, which allowed pointcloud fields in the top-level of Collections
Expand All @@ -24,5 +27,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

Initial independent release, see [previous history](https://github.com/radiantearth/stac-spec/commits/v1.0.0-rc.1/extensions/pointcloud)

[Unreleased]: <https://github.com/stac-extensions/pointcloud/compare/v1.0.0...HEAD>
[Unreleased]: <https://github.com/stac-extensions/pointcloud/compare/v2.0.0...HEAD>
[v2.0.0]: <https://github.com/stac-extensions/pointcloud/compare/v1.0.0...v2.0.0>
[v1.0.0]: <https://github.com/stac-extensions/pointcloud/tree/v1.0.0>
7 changes: 5 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,9 +26,9 @@ LiDAR or coincidence-matched imagery.
| ------------- | --------------------------------- | ----------- |
| pc:count | integer | **REQUIRED.** The number of points in the Item. |
| pc:type | string | **REQUIRED.** Phenomenology type for the point cloud. Possible valid values might include `lidar`, `eopc`, `radar`, `sonar`, or `other` |
| pc:schemas | [[Schema Object](#schema-object)] | A sequential array of Items that define the dimensions and their types. |
| pc:schemas | \[[Schema Object](#schema-object)\] | A sequential array of Items that define the dimensions and their types. |
| pc:density | number | Number of points per square unit area. |
| pc:statistics | [[Stats Object](#stats-object)] | A sequential array of Items mapping to `pc:schemas` defines per-channel statistics. |
| pc:statistics | \[[Stats Object](#stats-object)\] | A sequential array of Items mapping to `pc:schemas` defines per-channel statistics. |

### Schema Object

Expand Down Expand Up @@ -71,18 +71,21 @@ To run tests locally, you'll need `npm`, which is a standard part of any [node.j

First you'll need to install everything with npm once. Just navigate to the root of this repository and on
your command line run:

```bash
npm install
```

Then to check markdown formatting and test the examples against the JSON schema, you can run:

```bash
npm test
```

This will spit out the same texts that you see online, and you can then go and fix your markdown or examples.

If the tests reveal formatting problems with the examples, you can fix them with:

```bash
npm run format-examples
```
Loading
Loading