Hey Eladd,
thanks for the example.
Too bad my browser screws up some of the characters ( : I think those are supposed to be tabs?) :(
Also in the last line of your post, it should say
[b][i][...] will [...] create a .ply file in the same directory and in the same name, i.e. polyg3.ply[/i][/b]
Just a typo :)
As a side note: If your PATH variable contains the path to FeFlow, you command can be truncated to:
[b][i]shptoasc d:\feflow\north\gisdata\polyg3.shp id[/i][/b]
So I checked out shptoasc, and option -d caught my attention. I compared the ply file generated with and without that option. The difference is a section at the end of the file, that defines the linkage to the data in the dbf file (see attachement). It gives you a template and instructions how to modify it. I followed those, but when I tried to join the ply file, it still would recognize the linkage. It popped up the "Item-Parameter Assaciation" dialog. Once you specify the links, it will join the data and save a ffi file. The ffi file looks pretty much the same as the "link section" in the ply file:
[i][b][Join]
DATABASE kZones.dbf
TYPE DBASE
ITEM ID ID
ITEM KX CONDX[/b][/i]
Bottom line is: I don't know why the modified ply file doesn't work, but I figure one could generate ffi files easily since they follow a simple scheme - Faby was asking about that in a different posting ("Polygon file").
Any other ideas on this?
Chris