Latest Contributions by AyanPalit

@rohanrajan_hms  The Assembly feature class in an Utility Network domain, is a conceptual representation that would contain other physical features.  Assembly—Represents point features that contain other features. As with device features, assembly features are compact features, but they differ in that assemblies contain other significant devices. Assemblies are useful to show a single symbol on the map yet model the internal features and their connections. You can view the internal features of an assembly on the map or in the diagram view. Examples of assembly features are switchgear, transformer banks, and pump assemblies. Physical Assets in a domain network are typically stored in device, line and junction feature classes. There are instances where an organization may not have the assembly details or the desire to model all the components. In that case the entire 'enclosure' (which is physical) is modelled as the assembly (leaving out the internal physical details).  Other supporting physical assets are modelled as part of the structure network. Structural attachments are typically stored in boundary, line and junction feature classes. ... View more

@Acharya Great question and there are several blogs and help documentation that will provide detailed explanation. Here's my take on this: Utility Network = ArcGIS Utility Network product   Utility Network is the ArcGIS product focused on network solutions for electric, gas, and water utilities, architecture, engineering, construction (AEC), and telecommunications industries. Utility and Pipeline Data Model = UPDM is a template data model for gas and hazardous liquid pipelines. UPDM is included with the Gas and Pipeline Referencing Utility Network Foundation solution.  The model has multiple implementation patterns based on business requirements: Utility Network (Gas Asset Package) ArcGIS Pipeline Referencing (information model) Utility Network and ArcGIS Pipeline Referencing ... View more

@MarkDoehnert If this is satisfactory response, mark the solution for others in the community. ... View more

@MarkDoehnert Since you have the streets based  Linear Referencing System (LRS), this geo-reporting can be done simply by Locate Features Along Routes Locating polygon features along routes computes the route and measure information at the geometric intersection of polygon data and route data. Once polygon data has been located along routes, the resulting event table can be used, for example, to calculate the length of route that traveled through each polygon. AyanPalit_0-1708186813435.gif Tool parameters in this user scenario: Input feature: layer with areas Route features: LRS streets Output Event: as line with From-Measure Field and To-Measure Field. The difference will give you the curb miles of streets within specific areas. Depending on the segmentation of your streets, you may have to perform a dissolve/merge and play with the tool parameters. Hope this Helps! ... View more

@gpgisandsky There are well documented limitations to 'user-schema geodatabases'.  User-schema geodatabases are those stored in the schema of a user other than the sde user in Oracle. They are not entirely self-contained; there is some functionality, such as user-defined types, that is only in the sde geodatabase. For that reason, you cannot treat geodatabases in users' schemas as their own entity, and you cannot upgrade the sde geodatabase until you move content out of a user-schema geodatabase and delete the user-schema geodatabase from the Oracle database. This is a legacy pattern and it is recommended to  Move user-schema geodatabases to stand-alone geodatabases in Oracle Please review the general considerations for Branch version scenarios. ... View more