<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I’ve a lot of user-defined attributes on the station with entrance flag, centreline and survey object. The values are visible as a further column in the html list-exports.<o:p></o:p></p><p class=MsoNormal>The data should be also available in the sql database export.<o:p></o:p></p><p class=MsoNormal>Is there a way to manage this?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Centreline, survey and station custom attributes should be enough. But map, scrap, point, line and surface custom attributes is not needed in the sql file.<o:p></o:p></p><p class=MsoNormal>Three normalized tables would be fine:<o:p></o:p></p><p class=MsoNormal>C_ATTR_STATION<o:p></o:p></p><p class=MsoNormal>C_ATTR_CENTRELINE<o:p></o:p></p><p class=MsoNormal>C_ATTR_SURVEY<o:p></o:p></p><p class=MsoNormal>Each with an ID field of the corresponding table object, attribute name and value. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>//dirk<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>