Opened 16 years ago

Last modified 15 years ago

#168 closed defect

Can't unparse (to wkt or wkb) polygon with missing end point — at Version 2

Reported by: pramsey Owned by: pramsey
Priority: medium Milestone: PostGIS 1.4.0
Component: postgis Version: 1.4
Keywords: Cc:

Description (last modified by pramsey)

I managed to load this into 1.4 using the 1.3 shp2pgsql utility (so the parser accepted it). And now I can't dump the table because this geometry won't unparse. Fortunately, the GML output is more forgiving: 

<gml:MultiPolygon srsName="EPSG:2270">
 <gml:polygonMember>
  <gml:Polygon>
   <gml:outerBoundaryIs>
    <gml:LinearRing>
     <gml:coordinates>
      4280509.572796883992851,250062.898095423181076,1384.223139199977595 
      4280509.572796883992851,250062.898095423181076,1384.223139199977595  
      4280509.572796883992851,250062.898095423181076,1384.223139199977595
     </gml:coordinates>
    </gml:LinearRing>
   </gml:outerBoundaryIs>
  </gml:Polygon>
 </gml:polygonMember>
</gml:MultiPolygon>

It's a three-point polygon where startpoint = midpoint = endpoint.

Change History (2)

comment:1 by pramsey, 16 years ago

Description: modified (diff)

comment:2 by pramsey, 16 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.