[JPP-Devel] [ jump-pilot-Feature Requests-3472020 ] Saving long attribute name into shapefile

2012-04-19 Thread SourceForge . net
Feature Requests item #3472020, was opened at 2012-01-10 14:06
Message generated for change (Comment added) made by michaudm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=679909aid=3472020group_id=118054

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: File/Data IO
Group: None
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: michael michaud (michaudm)
Assigned to: michael michaud (michaudm)
Summary: Saving long attribute name into shapefile

Initial Comment:
Mail from Jukka related to bug id 3472008 :
What might happen when user is saving into shapefile a dataset with attributes 
like long_attribute_name_01 and long_attribute_name_02?  Truncating names 
to suit the .dbf format would yield to identical names. This is how GDAL 
behaves:

Attribute names can only be up to 10 characters long. Longer names will be 
silently truncated. This may result in non-unique column names, which will 
definitely cause problems later.

Starting with version 1.7, the OGR Shapefile driver tries to generate unique 
field names. Successive duplicate field names, including those created by 
truncation to 10 characters, will be truncated to 8 characters and appended 
with a serial number from 1 to 99.

For example:
 a → a, a → a_1, A → A_2;
 abcdefghijk → abcdefghij, abcdefghijkl → abcdefgh_1

Taken from http://gdal.org/ogr/drv_shapefile.html


--

Comment By: michael michaud (michaudm)
Date: 2012-04-19 07:28

Message:
Feature added in r2777 (2012-03-24)

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=679909aid=3472020group_id=118054

--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel


[JPP-Devel] [ jump-pilot-Feature Requests-3472020 ] Saving long attribute name into shapefile

2012-01-10 Thread SourceForge . net
Feature Requests item #3472020, was opened at 2012-01-10 14:06
Message generated for change (Tracker Item Submitted) made by michaudm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=679909aid=3472020group_id=118054

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: File/Data IO
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: michael michaud (michaudm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Saving long attribute name into shapefile

Initial Comment:
Mail from Jukka related to bug id 3472008 :
What might happen when user is saving into shapefile a dataset with attributes 
like long_attribute_name_01 and long_attribute_name_02?  Truncating names 
to suit the .dbf format would yield to identical names. This is how GDAL 
behaves:

Attribute names can only be up to 10 characters long. Longer names will be 
silently truncated. This may result in non-unique column names, which will 
definitely cause problems later.

Starting with version 1.7, the OGR Shapefile driver tries to generate unique 
field names. Successive duplicate field names, including those created by 
truncation to 10 characters, will be truncated to 8 characters and appended 
with a serial number from 1 to 99.

For example:
 a → a, a → a_1, A → A_2;
 abcdefghijk → abcdefghij, abcdefghijkl → abcdefgh_1

Taken from http://gdal.org/ogr/drv_shapefile.html


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=679909aid=3472020group_id=118054

--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel