Re: [gdal-dev] S-57 Driver WRONG Geometry

If we assume that each S57 object corresponds to a real world entity - in my opinion the best encoding would be a separate line object. I.e. the main road is a point to point entity (as LineString supports) and the spur from the east (such as the one from Ljubicevac) is a separate line. That would

Re: [gdal-dev] S-57 Driver WRONG Geometry

I guess is a commodity. The authority has sevencs production software. So, if it “looks ok” in that software “never mind the others”. Until Frank implemented the modification I’ve recomposed myself the geometry. But there is no way other than visual to decide if I should draw edge by edge or a

Re: [gdal-dev] S-57 Driver WRONG Geometry

Sevencs succeed in many other aspects where others fail. For example, they will actually parse and show older Netherlands chart data (I still have a few cells from a year ago), which encoded polygon edges using multiple SG2D fields, rather than a single SG2D field with multiple values. Not only th

Re: [gdal-dev] S-57 Driver WRONG Geometry

Dear Mike, I could not agree more. But, if u parse the sample ENC, you will see that for the ROADWY layer: >NAME_RCNM = (10:130,130,130,130,130,130,130,130,130,130) >NAME_RCID = (10:114,103,89,97,99,112,111,108,110,124) >ORNT = (10:1,1,1,1,1,1,1,1,1,1) >USAG = (10:

Re: [gdal-dev] S-57 Driver WRONG Geometry

Correct me if I am wrong (I might be) but my reading of S-57 standard (section 4.7 and thereabouts) is such that it does not provide for multi-line geometries. Instead, it is suggested that if certain edges of a line have to be "invisible" they should be masked by using appropriate attribute. I hav

Re: [gdal-dev] S-57 Driver WRONG Geometry

// Thank You all for your great effort!!! Bogdan On 5/27/2010 6:19 PM, Frank Warmerdam wrote: > Bogdan Grama wrote: >> Dear Frank >> >> Please find in the archive (http://www.wgs.ro/gdal/0_w.zip

Re: [gdal-dev] S-57 Driver WRONG Geometry

Bogdan Grama wrote: Dear Frank Please find in the archive (http://www.wgs.ro/gdal/0_w.zip): -the ENC -GDAL Interpretation -correct Interpretation The assembled geometry is not according with specifications. Each referenced edge starts and ends with a ConnectedNode. Not all the Connected nodes

Re: [gdal-dev] S-57 Driver WRONG Geometry

Dear Frank Please find in the archive (http://www.wgs.ro/gdal/0_w.zip): -the ENC -GDAL Interpretation -correct Interpretation The assembled geometry is not according with specifications. Each referenced edge starts and ends with a ConnectedNode. Not all the Connected nodes are present in the fe

Re: [gdal-dev] S-57 Driver WRONG Geometry

Dear Frank Please find in the archive (http://www.wgs.ro/gdal/0_w.zip): -the ENC -GDAL Interpretation -correct Interpretation The assembled geometry is not according with specifications. Each referenced edge starts and ends with a ConnectedNode. Not all the Connected nodes are present in the fe

Re: [gdal-dev] S-57 Driver WRONG Geometry

Bogdan Grama wrote: Dear all, I'm using GDAL/OGR for reading and rendering ENC files in c#. Recently i've discovered that for some ENC a feature geometry was badly decoded. >LAYER NAME = ROADWY >NAME_RCNM = (10:130,130,130,130,130,130,130,130,130,130) >NAME_RCID = (10:11

[gdal-dev] S-57 Driver WRONG Geometry

Dear all, I'm using GDAL/OGR for reading and rendering ENC files in c#. Recently i've discovered that for some ENC a feature geometry was badly decoded. >LAYER NAME = ROADWY >NAME_RCNM = (10:130,130,130,130,130,130,130,130,130,130) >NAME_RCID = (10:114,103,89,97,99,112,111