Skip to content

Commit 4e065bf

Browse files
gadomskim-mohr
andauthored
Release v2.0.0 (#14)
* deps: update dependencies * release: v2.0.0 * fix: update schema to The New Way, add more tests * Add media type --------- Co-authored-by: Matthias Mohr <[email protected]>
1 parent d014eb3 commit 4e065bf

File tree

8 files changed

+701
-95
lines changed

8 files changed

+701
-95
lines changed

.github/remark.yaml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
11
plugins:
2+
# Support Github-flavored Markdown
3+
- remark-gfm
24
# Check links
35
- validate-links
46
# Apply some recommended defaults for consistency
@@ -37,7 +39,7 @@ plugins:
3739
- - remark-lint-unordered-list-marker-style
3840
- '-'
3941
- - remark-lint-list-item-indent
40-
- space
42+
- one
4143
# Tables
4244
- remark-lint-table-pipes
4345
- remark-lint-no-literal-urls

CHANGELOG.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,24 @@
11
# Changelog
2+
23
All notable changes to this project will be documented in this file.
34

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

78
## [Unreleased]
89

9-
### Added
10+
## [v2.0.0] - 2024-08-21
1011

1112
### Changed
1213

13-
- Required properties of type `string` require a minimum length of `1`.
14-
15-
### Deprecated
14+
- Updated to "Pilot" maturity
15+
- Required properties of type `string` require a minimum length of `1`
16+
- `pc:schemas` is no longer required
1617

1718
### Removed
1819

20+
- `pc:encoding` because there is an encoding key in the asset
21+
1922
### Fixed
2023

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

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

27-
[Unreleased]: <https://github.com/stac-extensions/pointcloud/compare/v1.0.0...HEAD>
30+
[Unreleased]: <https://github.com/stac-extensions/pointcloud/compare/v2.0.0...HEAD>
31+
[v2.0.0]: <https://github.com/stac-extensions/pointcloud/compare/v1.0.0...v2.0.0>
2832
[v1.0.0]: <https://github.com/stac-extensions/pointcloud/tree/v1.0.0>

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,9 @@ LiDAR or coincidence-matched imagery.
2626
| ------------- | --------------------------------- | ----------- |
2727
| pc:count | integer | **REQUIRED.** The number of points in the Item. |
2828
| pc:type | string | **REQUIRED.** Phenomenology type for the point cloud. Possible valid values might include `lidar`, `eopc`, `radar`, `sonar`, or `other` |
29-
| pc:schemas | [[Schema Object](#schema-object)] | A sequential array of Items that define the dimensions and their types. |
29+
| pc:schemas | \[[Schema Object](#schema-object)\] | A sequential array of Items that define the dimensions and their types. |
3030
| pc:density | number | Number of points per square unit area. |
31-
| pc:statistics | [[Stats Object](#stats-object)] | A sequential array of Items mapping to `pc:schemas` defines per-channel statistics. |
31+
| pc:statistics | \[[Stats Object](#stats-object)\] | A sequential array of Items mapping to `pc:schemas` defines per-channel statistics. |
3232

3333
### Schema Object
3434

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

7272
First you'll need to install everything with npm once. Just navigate to the root of this repository and on
7373
your command line run:
74+
7475
```bash
7576
npm install
7677
```
7778

7879
Then to check markdown formatting and test the examples against the JSON schema, you can run:
80+
7981
```bash
8082
npm test
8183
```
8284

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

8587
If the tests reveal formatting problems with the examples, you can fix them with:
88+
8689
```bash
8790
npm run format-examples
8891
```

0 commit comments

Comments
 (0)