feature request: net or pin name attribute read/write support for GDS2

[GoogleCodeExporter]

 background:
By generating ready-to-use GDS2 files one expects a LVS clean layout. For this 
certain attributes per geometry-shape are needed. I'm not sure if this is 
defined in any standard but some of the EDA companies are using this to retain 
the pin name when doing successively streaming-out and/or streaming-in GDS-data.

Original issue reported on code.google.com by analogc...@gmx.net on 29 Mar 2013 at 10:23

[GoogleCodeExporter]

I will need a bit more info here. Some thoughts...
- GDS is owned theese days by Cadence if I'm not wrong and compliance is a bit 
of a dream. I'm not aware of a formal test file approved by the 
owner/maintainer.
- Not sure I can get the latest "official" format description from them unless 
I buy some of their products. It's not like a standard, to buy it legaly for 
~100 bucks from IEEE. A plenty of references on the web of course - so anybody 
can pick and choose...
- The original Calma GDS format contains a plenty of fields which were either 
hardly used ever or not used anymore. All the format versions after that in the 
majority of the cases reduce the record types.

I can continue of course, but let's get to the point:- I'll appreciate either a 
formal description of the requested attributes/properties in terms of GDS 
records or (even better and I believe easier) a very short example file.
The second point will be - some help when it comes to the validation of the 
feature.

Original comment by krustev....@gmail.com on 4 Apr 2013 at 10:35

[GoogleCodeExporter]

From my experience GDS does not store any data on shapes (like pin names, 
directions, etc.). LVS is supported by saving TEXT records (not in BOUNDARY or 
PATH) on some designated layers which then are recognized by verification tool. 

Also, GDSII not being "standardized" is a commonly accepted truth.

Original comment by edo...@gmail.com on 9 May 2013 at 5:24