Re: [OSGeo-Discuss] TIN file formats

2020-02-12 Thread Pierre Abbat
On Wednesday, 12 February 2020 06.35.27 EST Martin Dobias wrote:
> Unfortunately there is no mailing list yet - but feel free to open new
> issue(s) at the github repo and we can discuss there:
> https://github.com/lutraconsulting/MDAL/issues

That isn't right either. I'm not reporting a bug or asking for a feature; I'm 
asking for help understanding the code so that I can add a feature.

Pierre

-- 
La sal en el mar es más que en la sangre.
Le sel dans la mer est plus que dans le sang.



___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] TIN file formats

2020-02-12 Thread Martin Dobias
Hi Pierre

On Wed, Feb 12, 2020 at 12:07 PM Pierre Abbat  wrote:
>
> On Monday, 10 February 2020 04.29.37 EST Martin Dobias wrote:
> > MDAL stores TIN as a vector of vertices (XYZ) and a vector of faces
> > (where each face is a vector of indices of vertices). There is no
> > topological representation like half-edge data structure as this has
> > not been needed so far (the library so far has been mostly used for
> > rendering, deriving datasets and conversion between formats). MDAL now
> > supports vertex and face iterators, so drivers can use whatever
> > representation they want (including not keeping the mesh in memory at
> > all) as long as they can provide those iterators.
>
> Looks like I need more help than belongs on the discuss list. Is there a
> mailing list for MDAL?

Unfortunately there is no mailing list yet - but feel free to open new
issue(s) at the github repo and we can discuss there:
https://github.com/lutraconsulting/MDAL/issues

Regards
Martin
___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] TIN file formats

2020-02-12 Thread Pierre Abbat
On Monday, 10 February 2020 04.29.37 EST Martin Dobias wrote:
> MDAL stores TIN as a vector of vertices (XYZ) and a vector of faces
> (where each face is a vector of indices of vertices). There is no
> topological representation like half-edge data structure as this has
> not been needed so far (the library so far has been mostly used for
> rendering, deriving datasets and conversion between formats). MDAL now
> supports vertex and face iterators, so drivers can use whatever
> representation they want (including not keeping the mesh in memory at
> all) as long as they can provide those iterators.

Looks like I need more help than belongs on the discuss list. Is there a 
mailing list for MDAL?

Bezitopo and PerfectTIN, from which I'll be porting the TIN read/write 
routines, use a sort of winged-edge data structure. But the points, edges, and 
triangles are held in STL maps, which have to be in memory.

Pierre

-- 
When a barnacle settles down, its brain disintegrates.
Já não percebe nada, já não percebe nada.



___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] TIN file formats

2020-02-10 Thread Martin Dobias
Hi Pierre

On Sun, Feb 9, 2020 at 8:17 PM Pierre Abbat  wrote:
>
> Again: how does MDAL represent TINs internally? I looked at the code and got
> lost.

MDAL stores TIN as a vector of vertices (XYZ) and a vector of faces
(where each face is a vector of indices of vertices). There is no
topological representation like half-edge data structure as this has
not been needed so far (the library so far has been mostly used for
rendering, deriving datasets and conversion between formats). MDAL now
supports vertex and face iterators, so drivers can use whatever
representation they want (including not keeping the mesh in memory at
all) as long as they can provide those iterators.

Regards
Martin
___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] TIN file formats

2020-02-09 Thread Pierre Abbat
On Saturday, 7 December 2019 03.21.17 EST Saber Razmjooei wrote:
> Hi Pierre,
> Very interesting! We are trying to create a generic TIN reader/writer for
> open source applications:
> https://github.com/lutraconsulting/MDAL/
> 
> MDAL already supports a number of TIN/mesh formats and it is integrated
> with QGIS.
> 
> It would be good to join efforts.

Again: how does MDAL represent TINs internally? I looked at the code and got 
lost.

Pierre

-- 
Don't buy a French car in Holland. It may be a citroen.



___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] TIN file formats

2019-12-12 Thread Pierre Abbat
On Thursday, 12 December 2019 09.45.46 EST Saber Razmjooei wrote:
> Hi Pierre,
> 
> Apologies for the late response.
> 
> The link was updated. If your TIN is small, you can use MDAL to read it. An
> example of such data (ESRI ADF TIN) can be found here:
> https://github.com/lutraconsulting/MDAL/blob/master/mdal/frmts/mdal_esri_tin
> .cpp
> 
> With MDAL/QGIS, you can also display vectoral data (e.g. slope direction in
> http://files.carlsonsw.com/mirror/manuals/Carlson_2014/source/Site_Road_Desi
> gn/Surface/Triangulate_amp_Contour/08tri_contour9.PNG ).

How does MDAL represent TINs internally?

I have not heard any more about the Carlson TIN header. The other surveyor 
said he would contact the programmer at Carlson, but I don't know if he has.

Pierre
-- 
li ze te'a ci vu'u ci bi'e te'a mu du
li ci su'i ze te'a mu bi'e vu'u ci



___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] TIN file formats

2019-12-12 Thread Saber Razmjooei
Hi Pierre,

Apologies for the late response.

The link was updated. If your TIN is small, you can use MDAL to read it. An
example of such data (ESRI ADF TIN) can be found here:
https://github.com/lutraconsulting/MDAL/blob/master/mdal/frmts/mdal_esri_tin.cpp

With MDAL/QGIS, you can also display vectoral data (e.g. slope direction in
http://files.carlsonsw.com/mirror/manuals/Carlson_2014/source/Site_Road_Design/Surface/Triangulate_amp_Contour/08tri_contour9.PNG
).

Hope this helps.

Kind regards
Saber


For

On Sun, 8 Dec 2019 at 03:50, Pierre Abbat  wrote:

> On Saturday, 7 December 2019 03.21.17 EST Saber Razmjooei wrote:
> > Hi Pierre,
> > Very interesting! We are trying to create a generic TIN reader/writer for
> > open source applications:
> > https://github.com/lutraconsulting/MDAL/
> >
> > MDAL already supports a number of TIN/mesh formats and it is integrated
> > with QGIS.
> >
> > It would be good to join efforts.
>
> How does MDAL represent TINs internally?
>
> Where is the QGIS coding style? The link on that page goes to a 404 page.
>
> I may try to find out what the Carlson TIN header means. I'm talking to
> another surveyor tomorrow, who has tried to get the spec, but since I last
> talked with him about it, I met some people (not programmers) from
> Carlson,
> generated a TIN from a point cloud as they watched, exported it as
> Carlson,
> and handed it to them on a flash drive.
>
> Pierre
>
> --
> li ze te'a ci vu'u ci bi'e te'a mu du
> li ci su'i ze te'a mu bi'e vu'u ci
>
>
>
> ___
> Discuss mailing list
> Discuss@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/discuss



-- 
Saber Razmjooei
www.lutraconsulting.co.uk
+44 (0)7568 129733
___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] TIN file formats

2019-12-07 Thread Pierre Abbat
On Saturday, 7 December 2019 03.21.17 EST Saber Razmjooei wrote:
> Hi Pierre,
> Very interesting! We are trying to create a generic TIN reader/writer for
> open source applications:
> https://github.com/lutraconsulting/MDAL/
> 
> MDAL already supports a number of TIN/mesh formats and it is integrated
> with QGIS.
> 
> It would be good to join efforts.

How does MDAL represent TINs internally?

Where is the QGIS coding style? The link on that page goes to a 404 page.

I may try to find out what the Carlson TIN header means. I'm talking to 
another surveyor tomorrow, who has tried to get the spec, but since I last 
talked with him about it, I met some people (not programmers) from Carlson, 
generated a TIN from a point cloud as they watched, exported it as Carlson, 
and handed it to them on a flash drive.

Pierre

-- 
li ze te'a ci vu'u ci bi'e te'a mu du
li ci su'i ze te'a mu bi'e vu'u ci



___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] TIN file formats

2019-12-07 Thread Saber Razmjooei
Hi Pierre,
Very interesting! We are trying to create a generic TIN reader/writer for
open source applications:
https://github.com/lutraconsulting/MDAL/

MDAL already supports a number of TIN/mesh formats and it is integrated
with QGIS.

It would be good to join efforts.

Kind regards,
Saber



On Fri, 6 Dec 2019, 21:11 Pierre Abbat,  wrote:

> PerfectTIN can export a TIN in several formats: DXF (text or binary),
> Carlson
> TIN (reverse engineered, the spec is not public and I don't understand the
> header), LandXML, and a plain-text format which I found at https://
> www.xmswiki.com/wiki/TIN_Files . This last one is used by a program
> called
> AquaVeo. Does any other program use it? What's it called? Are there any
> other
> formats that I should write code to read or write?
>
> Pierre
> --
> li fi'u vu'u fi'u fi'u du li pa
>
>
>
> ___
> Discuss mailing list
> Discuss@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/discuss
___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

[OSGeo-Discuss] TIN file formats

2019-12-06 Thread Pierre Abbat
PerfectTIN can export a TIN in several formats: DXF (text or binary), Carlson 
TIN (reverse engineered, the spec is not public and I don't understand the 
header), LandXML, and a plain-text format which I found at https://
www.xmswiki.com/wiki/TIN_Files . This last one is used by a program called 
AquaVeo. Does any other program use it? What's it called? Are there any other 
formats that I should write code to read or write?

Pierre
-- 
li fi'u vu'u fi'u fi'u du li pa



___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss