Sequential Order

[Land337]

Is is possible to number tracts along a line in sequential order without having to manually input a value into the attribute table? I have attached a dwg as an example. Any help is much appreciated!

[ChicagoLooper]

@Land337 

<<...in sequential order without having to manually input a value....>>

Why? What purpose would that serve.

If there's another way to get what you want without putting it in sequential order then go that route instead.  Sequential order might just be a round-a-bout way of doing something when a better way (a more appropriate way) already exists.

You are have parcel data. Explain the desired result you want then let the forum determine the method to achieve it. 

St Mary's parish, right? Someone has overwritten some of your Parcel ID's .

[Land337]

@ChicagoLooper 

Sorry for not explaining further. Say I have a route the goes 100 miles through multiple parishes/counties and crosses thousands of parcels. I am interested in numbering these parcels (in flow order) to import the dbf in excel to obtain a tract list. Does this make sense? Thanks!

[ChicagoLooper]

Sorry, but that STILL doesn't clarify the  issue. I get that you want to put the parcels in a particular order......but why! Certainly you're not just putting them in order just for the fun it. There's a reason. Correct?

For whatever reason you wish to sort, I and many others, wouldn't do it that way. Why? Because it's meaningless. The key is why do you need to sort like that when you can easily isolate parcels? For example, you want to isolate parcels in a defined area. Or isolate parcels will PINs beginning with 987. Or isolate parcels bigger than 2 acres. Or isolate parcels so you can send property owners junk mail. Etc. Etc. Etc.

Yes, I know I can do it in excel, but what good does that do me. So I organize my 'list' of parcels in a specific order, big deal. I'm putting them in order for a reason. What I do with that ordered list I can most likely can do even when it's not in order.....or even do it without putting it in a list to begin with.

Do you know why some PIN numbers have been overwritten? Can you possibly shed some light on that?

If it were me, my workflow would be to MapExport the parcels to shapefile then do the sorting in shapefile's dbf because keeping them as AutoCAD polygons is too weak--there's a lot of horsepower when you leverage the dbf. Yes, I know, I know, putting it in sequential order is 'a' solution but it's NOT the solution. 

[parkr4st]

MAPEXPORT to 2 fdo files.  parcels and line  with what OD you desire

put the two files in a map and MAPGISOVERLAY INTERSECT to a SDF file

The line segments are in sequential order in the data table

use the .layer file in a map, the lables are there.

BTW a fake parcel at the beginning of the line will make 25 be #1 to be correct.

I have to go now.  the next step is to tranfer the label data to the polygons.

What to do when you divide a parcel is another question.

[O_Eckmann]

Hi @parkr4st, @Land337 

Are you sure that line segments are in sequential order?

I've tried this solution (Map 2023), and they are in sequential order from part 2 to part 24, but the 1st segment has id = 25 (last record).

I haven't tried it on another dataset to confirm this behavior, but your SDF have same problem.

For next question to transfer this info to parcels, you can MAPIMPORT these segments, and use this code to draw a text in the middle of the segment containing it's curvilinear abscissa along road.

(vl-load-com)
(defun C:Inc2Poly ( / oPart oPartDxf oRoad oRoadDxf I ssPart PTC dPK lsPK oPK)
  (if (and (setq oPart (car (entsel "\nSelect a cutted part : ")))
	   (setq oPartDxf (entget oPart))
	   (or (= "LINE" (cdr (assoc 0 oPartDxf))) (= "LWPOLYLINE" (cdr (assoc 0 oPartDxf))))
	   (setq oRoad (car (entsel "\nSelect the road : ")))
	   (setq oRoadDxf (entget oRoad))
	   (= "LWPOLYLINE" (cdr (assoc 0 oRoadDxf)))
      )
    (progn
      (setq ssPart (ssget "x" (list (cons 8 (cdr (assoc 8 oPartDxf))) (cons 0 "*LINE"))))
      (setq I 0)
      (repeat (sslength ssPart)
	(setq oPart (ssname ssPart I))
	(setq I (1+ I))
	(setq PTC (vlax-curve-GetPointAtDist oPart (* 0.5 (vlax-curve-GetDistAtParam oPart (vlax-curve-GetEndParam oPart)))))
	(setq dPK (vlax-curve-GetDistAtPoint oRoad PTC))
	(setq lsPK (append lsPK (list (list dPK PTC))))
      )
      (setq lsPK (vl-sort lsPK (function (lambda (e1 e2) (< (car e1) (car e2))))))
      (setq I 0)
      (repeat (length lsPK)
	(setq oPK (nth I lsPK))
	(setq I (1+ I))
	(entmake (list (cons 0  "TEXT")
		       (cons 8 (getvar "CLAYER"))
		       (cons 40 6.0)
		       (cons 10 (cadr oPK))
		       (cons 1 (rtos (car oPK) 2 2))
		       (cons 7 "STANDARD")
		 )
	)
      )
    )
  )
)

Then with ADEGENLINKS with option Enclosed text, you can transfer this info into parcels.

Problem can appear if road divides a parcel into more than 2 parts.