Convert mentioned point cloud formats to web-friendly Orbit Point Cloud.

realityconversion

# Reality Conversion API

The *Reality Conversion API* provides the ability to convert reality files such as point clouds from [supported source format](#supportedconversiontypes) to [supported target format](#supportedconversiontypes). Point cloud produced by scanning devices are often stored in very large files, in a format that reflects to the way data is captured but that is not ready to be directly consumed interactively in a web viewer. One of the main purposes of such a conversion is to make reality data, when stored in a non-web-friendly format, ready for web consumption.

##Input
A reality data container with correct classification and type hosting one or multiple Input files. 

##Output
A reality data container with correct classification and type hosting one or multiple output files (one per input file).  The output data is expressed in the same coordinate system as the input one. 

##Supported conversion types

|  Source Format | Source Extension  |  Source Type |  Target Format |  Target Extension | Target Type |
| :------------: | :---------------: | :----------: | :------------: | :---------------: | :---------: |
|  ASTM E57  | .e57 | E57 | Orbit Point Cloud  | .opc | OPC |
| Laser Exchange Format | .las | LAS | Orbit Point Cloud | .opc | OPC |
| LASzip Exchange Format | .laz  | LAZ | Orbit Point Cloud |.opc | OPC |
| Polygon File Format | .ply | PLY | Orbit Point Cloud | .opc | OPC |


---

Create a new job to convert point cloud formats to web-friendly Orbit Point Cloud. The POST request body MUST include type, name, inputs and outputs.
Accepted input formats for conversion are LAS, LAZ, PLY, E57 and ouput format is OPC.

### Authentication

Requires `Authorization` header with valid Bearer token for scope `realityconversion:modify`.

For more documentation on authorization and how to get access token visit [OAUTH2 Authorization](https://developer.bentley.com/apis/overview/authorization/) page.

---


jobs-create

OAuth access token with scope `realityconversion:modify`

Authorization

Setting to `application/vnd.bentley.itwin-platform.v1+json` is recommended.

Accept

My first RCS job

This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.

application/json;InvalidAuthorizationScheme

The 422 (Unprocessable Entity) status code indicates that the request cannot be processed by the server due to a client error (e.g. malformed request syntax).

application/json;InvalidRealityConversionRequest

This response indicates that the user has sent too many requests in a given amount of time.

The number of requests exceeds the rate-limit for the client subscription.

retry-after

---

Delete an unsubmitted job. Job will not be deleted once it is in active state.

### Authentication

Requires `Authorization` header with valid Bearer token for scope `realityconversion:modify`.

For more documentation on authorization and how to get access token visit [OAUTH2 Authorization](https://developer.bentley.com/apis/overview/authorization/) page.

---

jobs-delete

Job cannot be deleted once it has been submitted.

---

Retrieve job details.

### Authentication

Requires `Authorization` header with valid Bearer token for scope `realityconversion:read`.

For more documentation on authorization and how to get access token visit [OAUTH2 Authorization](https://developer.bentley.com/apis/overview/authorization/) page.

---


jobs-get

OAuth access token with scope `realityconversion:read`

---

Retrieve job progress.

### Authentication

Requires `Authorization` header with valid Bearer token for scope `realityconversion:read`.

For more documentation on authorization and how to get access token visit [OAUTH2 Authorization](https://developer.bentley.com/apis/overview/authorization/) page.

---

jobs-progress

---

Patch can be used for changing the job state (to active or cancelled), updating job type, inputs , outputs, options or changing cost estimation parameters.

### Authentication

Requires `Authorization` header with valid Bearer token for scope `realityconversion:modify`.

For more documentation on authorization and how to get access token visit [OAUTH2 Authorization](https://developer.bentley.com/apis/overview/authorization/) page.

---
