[OpenLayers-Dev] Review #2894 - GML.v3 <pos> read handling bug

[Christophe Noel]

Hello,

The v3 GML reader doesn't handle correctly a <pos> list. It currently assigns the obj.points with the current point coordinates, making any serie of <pos> be a single point.
It should rather push the new point to the array !

I created a patch for the easy fix :
Ticket : http://trac.osgeo.org/openlayers/ticket/2894
Patch : http://trac.osgeo.org/openlayers/attachment/ticket/2894/GML-v3.patch 

Regards,

Christophe NOEL,
SPACEBEL.

-------------------------

Other remarks :

I also don't understand why it is required to give the featureType and featureNamespace. In my opinion, the parser can work without knowing this information (or at least could detect it if needed).

That makes the OpenLayers.Format.GML class very useful to me : in my case, these information are not known.
Note that I also corrected a pos problem for this class :
Ticket #2885 : http://trac.osgeo.org/openlayers/ticket/2885 
Patch : http://trac.osgeo.org/openlayers/attachment/ticket/2885/GML.js.patch  



 



___________________________________________________________________________________
E-MAIL DISCLAIMER

The present message may contain confidential and/or legally privileged information.
If you are not the intended addressee and in case of a transmission error,
please notify the sender immediately and destroy this E-mail. 
Disclosure, reproduction or distribution of this document and its possible 
attachments is strictly forbidden.

SPACEBEL denies all liability for incomplete, improper, inaccurate, intercepted, 
(partly) destroyed, lost and/or belated transmission of the current information 
given that unencrypted electronic transmission cannot currently be guaranteed 
to be secure or error free. Upon request or in conformity with formal, contractual 
agreements, an originally signed hard copy will be sent to you to confirm 
the information contained in this E-mail.

SPACEBEL denies all liability where E-mail is used for private use.

SPACEBEL cannot be held responsible for possible viruses that might corrupt this 
message and/or your computer system.
____________________________________________________________________________________