<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Mid-pipe Attribute Changes in Gas and Pipeline Questions</title>
    <link>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458072#M354</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi All.&amp;nbsp; I'm not sure if this is the best forum for this question, as I am dealing with sanitary sewers, but here goes:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Our sewer pipes are represented as polylines and manholes are points.&amp;nbsp; The datasets are simple featureclasses in a geodatabase - they are not part of a linear network or have any other SDE-side relationships.&amp;nbsp; Pipes are segmented as different features between manholes, if attributes change between manholes.&amp;nbsp; We have new Asset Management software which treats the pipes as running contiguously between manholes; changes in attributes are represented as events, occurring a measured distance from a known point.&amp;nbsp; I need to make our data work in and with our new Asset Management software. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In a nutshell, I need a solution which uses unsplit pipe geometry between manholes, while retaining the information where attributes change mid-line.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have considered a linear network, however I have (at least) two requirements: &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1 - that the attributes of each dataset are linked, so that changes to one are automatically represented in the other, and &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2 - that thematic maps can be made showing different segments of each pipe differently - i.e. changes along the line are represented not as points, but as segments between pioints.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Will a Linear Network / Dynamic Segmentation accommodate this situation?&amp;nbsp; Or can anyone suggest a solution otherwise??&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sean&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Background (lengthy but may be helpful):&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Our sanitary sewers have a number of pipes that are well over 100 years old and in many places manholes are few and far between.&amp;nbsp; Because of this, there are numerous places where the pipes have been spot-repaired and so critical attributes of the feature change between manholes.&amp;nbsp; Also, our old brick sewers were built with vertical curves, so slope also regularly changes in between manholes.&amp;nbsp; We need to know where such changes occur.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To represent changes in between manholes, we have split the pipe geometry where attributes change.&amp;nbsp; To stick with our naming converntion (pipe are named for its upstream manhole), we have appended the unique ID of these segmented pipes with a ".1", ".2", etc.&amp;nbsp; So this way each segment still has a unique ID while retainnig a sequential relationship with the pipes and manholes around it.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Recently our Sewer department has gone to the NASSCO PACP/MACP assessment and management standards, and is in the midst of integrating our GIS information into an Asset Management software which also works with these standards.&amp;nbsp; These standards, and particularly this AM software, requires that a pipe segment is defined between manholes and is not split.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We are still using 9.31 but are right on the cusp of migrating to 10.1.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Dec 2012 14:19:52 GMT</pubDate>
    <dc:creator>SeanGambrel</dc:creator>
    <dc:date>2012-12-13T14:19:52Z</dc:date>
    <item>
      <title>Mid-pipe Attribute Changes</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458072#M354</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi All.&amp;nbsp; I'm not sure if this is the best forum for this question, as I am dealing with sanitary sewers, but here goes:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Our sewer pipes are represented as polylines and manholes are points.&amp;nbsp; The datasets are simple featureclasses in a geodatabase - they are not part of a linear network or have any other SDE-side relationships.&amp;nbsp; Pipes are segmented as different features between manholes, if attributes change between manholes.&amp;nbsp; We have new Asset Management software which treats the pipes as running contiguously between manholes; changes in attributes are represented as events, occurring a measured distance from a known point.&amp;nbsp; I need to make our data work in and with our new Asset Management software. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In a nutshell, I need a solution which uses unsplit pipe geometry between manholes, while retaining the information where attributes change mid-line.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have considered a linear network, however I have (at least) two requirements: &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1 - that the attributes of each dataset are linked, so that changes to one are automatically represented in the other, and &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2 - that thematic maps can be made showing different segments of each pipe differently - i.e. changes along the line are represented not as points, but as segments between pioints.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Will a Linear Network / Dynamic Segmentation accommodate this situation?&amp;nbsp; Or can anyone suggest a solution otherwise??&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sean&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Background (lengthy but may be helpful):&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Our sanitary sewers have a number of pipes that are well over 100 years old and in many places manholes are few and far between.&amp;nbsp; Because of this, there are numerous places where the pipes have been spot-repaired and so critical attributes of the feature change between manholes.&amp;nbsp; Also, our old brick sewers were built with vertical curves, so slope also regularly changes in between manholes.&amp;nbsp; We need to know where such changes occur.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To represent changes in between manholes, we have split the pipe geometry where attributes change.&amp;nbsp; To stick with our naming converntion (pipe are named for its upstream manhole), we have appended the unique ID of these segmented pipes with a ".1", ".2", etc.&amp;nbsp; So this way each segment still has a unique ID while retainnig a sequential relationship with the pipes and manholes around it.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Recently our Sewer department has gone to the NASSCO PACP/MACP assessment and management standards, and is in the midst of integrating our GIS information into an Asset Management software which also works with these standards.&amp;nbsp; These standards, and particularly this AM software, requires that a pipe segment is defined between manholes and is not split.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We are still using 9.31 but are right on the cusp of migrating to 10.1.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2012 14:19:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458072#M354</guid>
      <dc:creator>SeanGambrel</dc:creator>
      <dc:date>2012-12-13T14:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: Mid-pipe Attribute Changes</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458073#M355</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Just a quick additional thought / question:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If we were to use Dynamic Segmentation (DynSeg) to address this problem, it is likely that we would move all of our attribute info into our DynSeg FC.&amp;nbsp; Otherwise we'd have some attributes in the base geometry and some in the DynSeg FC.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does anyone else use this setup?&amp;nbsp; Is this a great or terrible idea?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sean&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2012 17:29:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458073#M355</guid>
      <dc:creator>SeanGambrel</dc:creator>
      <dc:date>2012-12-13T17:29:23Z</dc:date>
    </item>
    <item>
      <title>Re: Mid-pipe Attribute Changes</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458074#M356</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'd like to know the same thing, we are in the same boat with attributes changing mid-pipe and wanting to integrate with asset management software.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2013 15:28:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458074#M356</guid>
      <dc:creator>TrishRice</dc:creator>
      <dc:date>2013-02-06T15:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: Mid-pipe Attribute Changes</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458075#M357</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;these are by the definition seperate assets... so they should be treated like this accordingly..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;so the creation of dummy assets is required. We use a flange fitting to split in this case or a "miscellaneous fitting". We have comonality using non key fields such as linecode and a common name for major assets such as outfalls and tunnels.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Feb 2013 01:59:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/mid-pipe-attribute-changes/m-p/458075#M357</guid>
      <dc:creator>GrahamW</dc:creator>
      <dc:date>2013-02-07T01:59:37Z</dc:date>
    </item>
  </channel>
</rss>

