I need to create a list of parcels that are intersected by a pipeline. That list has to be ordered from the beginning of the line to the end. I have hundreds of lines so automating this would be fantastic. I can create the list of parcel owners with a select by location but putting them in order is where im stumped.
Is there a way to number polygons along a line from beginning to end?
I need to create a list of parcels that are intersected by a pipeline. That list has to be ordered from the beginning of the line to the end. I have hundreds of lines so automating this would be fantastic. I can create the list of parcel owners with a select by location but putting them in order is where im stumped.
Is there a way to number polygons along a line from beginning to end?
Use the Create Routes tool in the Linear Referencing tool set to convert your pipelines to Routes. I assume each pipeline has a unique ID that can function as the Route ID field. Assign measure in a way that makes sense, probably that respects the direction of the line. You can create 2 fields. One will be 0 for the From Measure, the other will hold your To Measure and can be calculated to equal your line length. Use Locate Features along Route. This will create a duplicate of your APN with three added fields, the pipe Route ID (your pipeline ID) and the From and To measure where the feature intersected the line. Sort by Route ID and From measure (Ascending or Descending as you like) to list the APNs in the order that they fall along the road. You also will have an event table that can map the linear overlap of the parcels on the line.
This seems to be working other than that the table that created has all zeros for the FMEAS and TMEAS and cant be sorted. It is however selecting the right parcels based on the Route Identifier, it is just not populating the measurement fields.
This seems to be working other than that the table that created has all zeros for the FMEAS and TMEAS and cant be sorted. It is however selecting the right parcels based on the Route Identifier, it is just not populating the measurement fields.
Make sure to go to the Environmental Settings for Create Route and set the M Extent, Resolution and Tolerance to handle fractions. Without Environmental overrides it tends to create measures in whole numbers, which means that fractions of a mile turn into 0. Calculate M values for the Route To value into a field to verify they are not 0 with a Python Calculation:
!Shape.Lastpoint.M!
If the fractional value is not a problem, then run Intersect and use the formula to extract M values from the intersected lines (they will transfer).
