Le jeudi 28 janvier 2016 10:33:49, Jukka Rahkonen a écrit : > Even Rouault <even.rouault <at> spatialys.com> writes: > > Hi Jukka, > > > > could you provide the file or the source file used to generate it ? In > > theory, > > > the driver should be able to process any valid file. The checks are meant > > to detect things like > > <veeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeery_loooooooong_tag_name> > > > that could result in denial of service, but there must be something > > wrong. > > And > > > you don't get that with GML where there are similar checks ? > > > > Even > > Hi, > > I had a new look on the data and prepared a dataset for testing > http://latuviitta.org/downloads/big_polygon_jml.zip
I downloaded it and don't see any issue. But it looks like it is the one written by GDAL > > The issue happens when GDAL reads JML file that is written by OpenJUMP. > There is no errors if I convert the data into JML format with ogr2ogr. Main > difference between those files is that GDAL writes the polygon geometry as > one line but OpenJUMP is writing it formatted with line breaks and lots of > white space > > <geometry> > <gml:MultiPolygon> > <gml:polygonMember> > <gml:Polygon> > <gml:outerBoundaryIs> > <gml:LinearRing> > > <gml:coordinates>193588.34496920794,7005684.6655854415 > 193632.06812505925,7005834.808810625 > 193608.4497544446,7005874.299165146 > .... > > > -Jukka Rahkonen- > > > > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
