Closed GoogleCodeExporter closed 9 years ago
Maybe those keywords are GML 3+?
I've fixed the gml reader in r796 to handle the keywords, except for file 4
since I don't know how to handle that yet. Surface is not a class in NTS.
Original comment by felix.ob...@netcologne.de
on 2 Jan 2012 at 10:40
Many thank felix :)
Actually I haven't worked much on GML format and have no idea about the meaning
of <gml:exterior>, <gml:posList> and <gml:pos>. Regarding the file 4 issue,
maybe the Surface element in that GML file isn't in GML standard or maybe it
have been added to GML later on. I'm not sure which case is right
Original comment by duylamph...@gmail.com
on 2 Jan 2012 at 10:57
AFAIK in 'Simple Features Specification for SQL' a surface is an abstract
class, and the only concrete implementation is the Polygon class, so I think
that can be correct to try to manage a surface as a polygon and let the code
fail if some error happens
Original comment by diegogu...@gmail.com
on 2 Jan 2012 at 11:06
From looking at the sample file I assume it would be more like a multipolygon,
but may contain patches made of nonlinear components, like e.g. oracle sdo can
handle. I don't think we should bother as long jts does not.
Original comment by felix.ob...@netcologne.de
on 2 Jan 2012 at 1:46
>I don't think we should bother as long jts does not
I completely agree.
Original comment by diegogu...@gmail.com
on 2 Jan 2012 at 1:48
Thank you
Original comment by duylamph...@gmail.com
on 3 Jan 2012 at 3:06
Original issue reported on code.google.com by
duylamph...@gmail.com
on 1 Jan 2012 at 9:14Attachments: