Hello
@Jukka Rahkonen: The OSSIM project (the link you provided) is more of image
orthorectification. Although
they are doing image co-registration but its as one of the steps of
orthorectification(I could only understand this from the manual).
Also I am not sure of the techniques they are using f
Jürgen, Even,
please find below a snip of my NAS-data. As there are legal restrictions
I ed the coordinate information and some other stuff.
codeSpace="http://www.adv-online.de/";>urn:adv:oid:DERPLP17rFWQ
Even Rouault wrote
> Hermann,
>
> It is (was) a limitation of the GML driver. The issue is that from its
> point
> of view there's only one feature AQD_ReportingHeader, but you are
> interested
> into its sub-elements AQD_Zone, and the GML parser isn't smart enough to
> guess
> your intention.
Le mercredi 29 janvier 2014 12:51:25, peifer a écrit :
> Hi,
>
> I have a GML file [1], which according to my understanding has 7 polygon
> features [2]. ogrinfo only sees 1 feature [3], which is the last one in
> document order (gml:id="ZON_NO0005_Polygon").
>
> Can someone please tell me if the
Hi Even,
On Wed, 29. Jan 2014 at 14:12:06 +0100, Even Rouault wrote:
> > In the NAS data there is a srsName attribute for every geometry object.
> > This srsName can differ from the srsName for the whole layer. As far as I
> > see in the code, this is actually not implemented and this leads to wr
Le mercredi 29 janvier 2014 13:06:42, Stefan Bernsdorf a écrit :
> Hi,
> I have question concerning the NAS data importer.
> In the NAS data there is a srsName attribute for every geometry object.
> This srsName can differ from the srsName for the whole layer.
> As far as I see in the code, this is
Hi,
I have question concerning the NAS data importer.
In the NAS data there is a srsName attribute for every geometry object.
This srsName can differ from the srsName for the whole layer.
As far as I see in the code, this is actually not implemented and this
leads to wrong data is the value for
Hi,
I have a GML file [1], which according to my understanding has 7 polygon
features [2]. ogrinfo only sees 1 feature [3], which is the last one in
document order (gml:id="ZON_NO0005_Polygon").
Can someone please tell me if the observed ogrinfo behaviour is a known
limitation of the GML driver,
