Latest Contributions by AyanPalit

@AvaFarouche Looks like you are directly using the Excel Table. Does your other processes work fine with data in Excel - there are specific instructions to Work with Microsoft Excel files in ArcGIS Pro If the required drivers are installed, try using Excel to Table  and use the GDB table as input to XY Table to Point tool. ... View more

Updating this old thread for tracking and community documentation. Related post: https://community.esri.com/t5/arcgis-pro-questions/arcgis-pro-calculate-geometry/m-p/1667532  I added links to the Calculate Geometry Attributes as well as requirements of the field/data type for the geometry attributes. Check if you are using 'double' type for XY coordinates. ... View more

Updating this old thread for tracking and community documentation.  Use Calculate Geometry Attributes to add information to a feature's attribute fields representing the spatial or geometric characteristics and location of each feature, such as length or area and x-, y-, z-coordinates, and m-values. Access the Calculate Geometry tool by opening the attribute table and right-clicking the field to bring up the context menu. There is an option to 'Calculate Geometry'. This tool can also be accessed directly from the geoprocessing pane from within the Data Management toolbox > Calculate Geometry Attributes. You can select an existing field or provide a new field name. If a new field name is provided, the field type is determined by the type of values that are written to the field. Count attributes are written to long integer fields; area, length, and x-, y-, z-coordinate, and m-value attributes are written to double fields; and coordinate notations such as Degrees Minutes Seconds or MGRS are written to text fields. Reference KB article: Calculate geometry in ArcGIS Pro ... View more

@VenkataKondepati You can find the schema at Introduction to Communications Utility Network Foundation ... View more

@TrinityShuler02  The stack exchange provides a basic way of getting the distances. However, you have to repeat the entire process for new sets of points -  black polygon and pink diamond. The same link also mentions linear referencing.  The workflow is better handled through Linear Referencing ; it does need learning some new concepts and tools.  You can get started with the following references: Linear referencing datasets NHD flowlines may be modelled as Routes with the Start/End locations as Calibration Points or simply update measures on the vertices based on geometry length. You can then Locate Features Along Routes using NHD flowline as input route and the points as input features. You can provide search radius of 300 feet for the points that do not intersect the NHD routes. The tool will generate a event table with the located measure of each point along the NHD route. You can then do a simple calculation to find the distance between specified points. This method can be used to persist the measures on the NHD flowline routes. You can generate the event table by running Locate Features Along Routes for newer sets of points. ... View more

@CoronaGis Thanks for posting your use case with details and drawing. I encourage organizations to conceive the best way to model the network, rather than duplicate what a legacy system used to do. Utility Network has much broader modelling capabilities with greater possibilities.   Here are my comments: Start at identifying the subnetworks for your gas distribution system. A great resource for this is: Managing Gas and Pipeline Networks: Creating Subnetworks Is District similar to a pressure zone? If so, Compressor or Regulator are the prime candidates to act as the subnetwork controller for Pressure tier.  Controllable valves are the prime candidates to act as the subnetwork controller for isolation tier.  Measurement points do not impact network behavior and therefore not good choice for 'device' and hence 'subnetwork controller' (only devices can act as controllers).  Assuming use of the  Gas and Pipeline Referencing Utility Network Foundation  , PipelineDevice has a yes/no flag field, that can be used to indicate Measurement or SCADA indicator. Note this is simply an attribute, and doesn't impact network behavior. Utility companies often have unique business requirements that drive the modelling decisions. Hoping others in the community will share their implementation advice.    ... View more