[OSGeoLive] Adding PerfectTIN to OSGeoLive
Astrid Emde (OSGeo)
astrid_emde at osgeo.org
Tue Aug 25 02:12:59 PDT 2020
This mail went to Pierre and Alex...
Am 25.08.2020 11:00 schrieb Astrid Emde:
> Hello Pierre,
> Am 25.08.2020 04:52 schrieb Alex Mandel:
>> On 8/18/20 7:19 PM, Pierre Abbat wrote:
>>> On Tuesday, 18 August 2020 15:57:00 EDT Astrid Emde (OSGeo) wrote:
>>>> Hello Pierre,
>>>> thanks for your application.
>>>> Could you please also provide an installer for your software in a
>>>> and make a pull request so we can test it.
>>>> * see also
>>> I'm in the midst of implementing STL export after adding color to the
>>> of exported PLY files, so I can't work on a package until that's
>>> ready to
>>> release, which will be version 0.5.1. On top of that, I had two
>>> computers fail
>>> in quick succession. One of them is my main development box, and it
>>> came back
>>> from repair not booting.
>>> Do you mean a .deb package or instructions in shell that fetch the
>>> and build and install them?
>>>> Looks like we do not have point clouds on OSGeoLive yet. Do you have
>>>> suggestion for good example data?
>>> Darkblue_b sent me a link to a point cloud in Raleigh, which I may or
>>> may not
>>> be able to access (it's on the failed computer's M.2 drive). It is
>>> not clean
>>> (it's full of trees). IIRR he processed it at 1 dm tolerance, which
>>> that point
>>> cloud does not deserve, as its density is only about 1/m².
>>> Pat, who asked me to write the program in the first place, is going,
>>> in the next few weeks, to fly a drone above a church in Shelby to get
>>> data for a continuing education seminar to be held there in December.
>>> data will be distributed, or at least demonstrated, to some 40-80
>>> which should be public enough for a data set to be distributed with
>>> The other point clouds I have are jobs eGPS (where Pat works) or
>>> 3DSurvey has
>>> done, except for one square of West Virginia terrain, which is
>>> covered with
>>>> After we had a look at the installer and decide whether PerfectTIN
>>>> you could write the documentation files.
>>>> For the documentation youu find information at
>>> Is what you mean by "documentation" just one line in the CSV file, or
>>> is it
>>> something that would explain to a user how to use the program?
>> We could also consider using a small sample from the USGS 3DEP public
>> data set. https://usgs.entwine.io/
> Sample Data
> I think for the sample data it is important, that the data is not too
> It would be great if it would fit to the data we already have
> About the documentation.
> Each project has to provide an overview document and a quickstart.
> see https://live.osgeo.org/en/overview/overview.html
> On Github at: https://github.com/OSGeo/OSGeoLive-doc/tree/master/doc
> the line in the csv file gathers some overview information that is
> used to setup the documentation pages
More information about the osgeolive