Uploading a pointset to Evo

Introduction

This guide will walk you through the process of uploading a pointset to Evo.

About the pointset object

The pointset object we will be uploading conforms to the Pointset (v 1.0.1) pointset schema and has the following required parameters:

• An instance of Base Spatial Data Properties (v 1.0.1), which includes:

  • bounding_box: Bounding box of the spatial data.
  • coordinate_reference_system: Coordinate system of the spatial data.
  • An instance of Base Object Properties (v 1.0.1), which includes the required parameters:
    • name: The name of the object that will appear in Leapfrog and other client applications.
    • uuid: Identifier of the object. Can be left as None if this is a new object.

• locations: The locations of the points.

The metadata for the example pointset object we will upload has the following structure:

{
    "schema": "/objects/pointset/1.0.1/pointset.schema.json",
    "uuid": null,
    "name": "Example pointset.",
    "description": "This is an example of a pointset Geoscience object.",
    "locations": {
        "coordinates": {
            "width": 3,
            "data_type": "float64",
            "length": 50,
            "data": "35b8b8ba5479a34e905a1b9e212e1cb4a52ec484b969359f2c28f5a00311dbca"
        }
    },
    "bounding_box": {
        "min_y": -5550857.067070156,
        "max_y": -5309927.430829638,
        "min_x": 19108070.856018253,
        "max_x": 19338143.530560993,
        "min_z": 0,
        "max_z": 0
    },
    "coordinate_reference_system": {
        "epsg_code": 3857
    },
    "tags": {
        "location": "location"
    }
}

Before we can upload the pointset object metadata, we need to upload the data file(s) associated with the pointset object. In this example, we will upload a single data file being referenced by the pointset object 'locations' field and identified by the data hash: 35b8b8ba5479a34e905a1b9e212e1cb4a52ec484b969359f2c28f5a00311dbca.