[postgis-users] shp2pgsql bug?

[Eric Lam]

Thanks, it is now working as expected for my data.

regards
Eric Lam

strk at refractions.net wrote:

>Never mind, I could reproduce the problem with current head
>and have fixed it. Can give CVS a try  ?
>I added support for loader/dumper test, automatically run
>by 'make test'. Currently tests for MULTILINE in all dimensions
>are provided.
>
>--strk;
>
>On Fri, Jun 16, 2006 at 11:51:03AM +0200, strk at refractions.net wrote:
>  
>
>>Which versions are you using of both  pgsql2shp and shp2pgsql ?
>>
>>--strk;
>>
>>On Fri, Jun 16, 2006 at 03:23:18PM +0930, Eric Lam wrote:
>>    
>>
>>>Hello list,
>>>
>>>I am back porting geometries I have loaded in postgresql8.x with postgis 
>>>1.x to a postgresql 7.4.x with postgis 0.8.x
>>>
>>>I am doing a:
>>>pgsql2shp -f tmp.shp -g the_geom data MLSTable
>>>shp2pgsql -s 4283 -c -g the_geom -w tmp.shp MLSTable > table.sql
>>>
>>>All geometries are multilinestrings. However up until recently, I have 
>>>only ever had 1 linestring in the multilinestring.
>>>For geometries with more than 1 linestring in the multilinestring there 
>>>is a comma at the start of every extra linestring except the first.
>>>eg MULTILINESTRING( (12 34, 23 34, 14 51),(,25 43,34 23,34 54),(,76 
>>>45,34 23))
>>>
>>>Is this a known problem? Is there something I am missing?
>>>
>>>At the moment I have piped the file through sed to remove the extra 
>>>comma before loading into the older database.
>>>This is loading fine, however ....
>>>      
>>>
>>_______________________________________________
>>postgis-users mailing list
>>postgis-users at postgis.refractions.net
>>http://postgis.refractions.net/mailman/listinfo/postgis-users
>>    
>>
>
>  
>