topic Attached Lisp: Will select Object Data but won't turn on grips in AutoCAD Map 3D Forum

Attached Lisp: Will select Object Data but won't turn on grips

TheCanadianPrimate — Wed, 10 May 2023 18:24:23 GMT

I've been fooling around a bit with bringing into Map 3D some of our GIS info for ESRI's ArcGIS Pro. One of the things I wanted to do was create a selection set based on object data. Now the attached lisp file Sel_by_OD__US.lsp will do just that but it won't turn on the grips so I can what it is I selected. If you look at the bottom of the code there is (sssetfirst nil js_sel) which I though might be the code to do so. However it's not turning on the grips for me.

I'm using Map 3d 2023.

Any ideas?

Re: Attached Lisp: Will select Object Data but won't turn on grips

CADaSchtroumpf — Wed, 10 May 2023 22:16:21 GMT

(sssetfirst) may not work well on first use.
Activate the grips by selecting only one object, if the grips appear, press "ESC" to cancel the selection and restart the lisp command.
If the grips still do not appear, the number of objects may be too large, but the selection is effective. See in the properties palette if "all"(nbr objects) is present. If yes then you can act in the properties or launch an editing command.

Re: Attached Lisp: Will select Object Data but won't turn on grips

ChicagoLooper — Sun, 14 May 2023 00:36:54 GMT

@TheCanadianPrimate

If you simply want isolate objects based on object data (OD) then you don’t need lisp because you can do that using a query. AutoCAD Map3D can run an object data query based on the rule(s) you stipulate.

What does your object data contain?
What condition(s) do you want to use to isolate or group objects?

If you don’t have a plan to isolate or identify objects and just want to group objects on-the-fly as you go, then a lisp is not what you should use. Don’t use a lisp just because you don’t know how to do it any other way—the forum is here to explain alternative and more appropriate ways to efficiently achieve your goal.

If you’re willing to share your OD and can thoroughly explain what you’d like to accomplish a solution can be provided.

Re: Attached Lisp: Will select Object Data but won't turn on grips

fieldguy — Sun, 14 May 2023 10:21:17 GMT

One of the main advantages to using programming techniques to work with object data is the operations occur in the current file - opened in the editor. IMO this is far less cumbersome than working on a document that is "Map->Attached".

Re: Attached Lisp: Will select Object Data but won't turn on grips

ChicagoLooper — Sun, 14 May 2023 15:50:01 GMT

@CADaSchtroumpf

You don’t have to use ‘Map=>Attach’ command.

The ‘query current drawing’ feature uses Object Data which is already part of the OP’s drawing. There’s no requirement to be ‘Map=>connected. None.

However, if using a shapefile data (an FDO connection) then a query will not only isolate entities, it can go further.

On a parcel shapefile, you can identify AND isolate because you’ve got more horsepower. Waaayy more. And that engine is already built into Map3D, not added on.

For example,

All properties above 10,000 SF
All properties valued >$200,000
All properties on Street, City.

A query if flexible and can be based on one criteria, 2 criteria or all three. The same query can even color code the results, vary the line weights, use a different linetypes and even add a label from the shapefile’s database.

If you’ve never run a powerful query you’d never think it was possible and only other methods, such as lisps, are the only ones capable. Data analysis is where FDO’s stand out and a simple isolate operation will invariably lead to greater, more efficient possibilities allowing the drawing (and user) to shine.

Re: Attached Lisp: Will select Object Data but won't turn on grips

fieldguy — Mon, 15 May 2023 10:22:58 GMT

>>The ‘query current drawing’ feature uses Object Data which is already part of the OP’s drawing. There’s no requirement to be ‘Map=>connected. None.<<

Where is this 'query current drawing' command?

I totally agree with your last statement. Why is there no FDO connection for DWG files?

Re: Attached Lisp: Will select Object Data but won't turn on grips

ChicagoLooper — Mon, 15 May 2023 12:24:11 GMT

@CADaSchtroumpf wrote

<<…Where is this 'query current drawing' command?>>

You can query Object Data through the Map Task Pane. You don’t need an FDO connection.

Re: Attached Lisp: Will select Object Data but won't turn on grips

fieldguy — Mon, 15 May 2023 12:46:36 GMT

That command is under "Add Drawing Data". I do not want to add anything - I am only interested in existing entities.

The examples you posted previously (For example, All properties above 10,000 SF, All properties valued >$200,000, All properties on Street, City) cannot be pertormed in that query dialog.

Re: Attached Lisp: Will select Object Data but won't turn on grips

TheCanadianPrimate — Mon, 15 May 2023 13:09:37 GMT

The simplest answer here for me is to run the lisp and after it's done "Select" and "p". That will highlight with grips all my selected items ( ex. all fire hydrants in the city that are private).

Thanks to all that replied I'm going to take a good look at your answers see what I can learn when I have a bit of slack time.

Re: Attached Lisp: Will select Object Data but won't turn on grips

ChicagoLooper — Mon, 15 May 2023 13:16:06 GMT

@fieldguy

What?!

Read the opening post. There's object data and it already exists, it's not being added.

Object data exists when it's attached to vectors, as in existing vectors. Are you saying object data isn't attached to vectors, isn't attached to anything......so OD are orphans and are unattached, just floating in thin air, with no geospatial presence?

You don't have to 'add' anything because the entities AND the associated OD is already there. Did you forget to read the opening post?

Re: Attached Lisp: Will select Object Data but won't turn on grips

fieldguy — Mon, 15 May 2023 14:01:48 GMT

>>You don't have to 'add' anything <<. Why is the initial command "Add Additional data" then? It does add data - it creates a "view" (I assume that's what it is) of the entities that match the criteria. I confess - I have never used it before, but it looks like that could be used to answer the OP. You can use your query examples in that dialog.

Re: Attached Lisp: Will select Object Data but won't turn on grips

CADaSchtroumpf — Mon, 15 May 2023 14:50:02 GMT

Actually, I didn't know about this procedure.
I had a little trouble experimenting with it because I couldn't see the result at all (you have to remember to uncheck the base of the drawing to see it)
Thanks for the tip

Re: Attached Lisp: Will select Object Data but won't turn on grips

ChicagoLooper — Mon, 15 May 2023 15:10:36 GMT

@TheCanadianPrimate

Did you use MAPIMPORT get the object data (OD) from the fire hydrant shapefile? Or was the OD already attached to the hydrants? Either way, if you have data indicating which blocks are private and which aren't, then that OD can be leveraged to identify your 'p' hydrants.

Here's an example using MapImport when importing a fire hydrant shapefile. (Your mileage may vary.)

MapImport command is used on the shapefile. Since I already have a block defined in the drawing (I pasted a circle block in modepsace then deleted it so the block would be defined) the imported hydrants could use that circle block. In addition to bringing the hydrants, OD was also attached during the mapimport command. The end result are 'smart' blocks representing the fire hydrants.

Since the source data is a shapefile, I can harvest the shapefile's database. Here's a small portion of the shapefile's dbf that's arranged in 1,321 rows and 41 columns. Each row represents an individual hydrant and each column represents a hydrant attribute. (See image-1)

Image-1

I want my map to display the hydrant's manufacturer so I used the MFG column containing the Mfg. attribute values Kennegy, M&M, Mueller and Null. The MapImport command segregated the hydrants according to Mfg. name and put each manufacturer on it's own layer. As you already know, you can easily control, color, linetype, line weight, freeze and thaw on a ByLayer basis. (See image-2)

Image-2

Notes:

Object data came from the shapefile's database file (dbf) during MapImport procedure. No lisp used.
Although a query could've been used, no query was used because the Mapimport command itself is powerful enough to group the hydrants based on data, in this specific case MFG data.
If a location query was used (and it wasn't) I could've just queried a 9-square block area defined by a polygon, such as rectangle I drew ahead of time.
A more enhanced query could've also included a combination of date installed, test date, repair date, main size, etc., etc. to isolate or group the hydrants.
The hydrants could've also been labeled with a hydrant number harvested from the OD.
Image-2 only displays AutoCAD blocks and Bing Map.
The layers displayed in the Layer Prop Manager are not user-generated per se, they were created by settings in the MapImport command.

Re: Attached Lisp: Will select Object Data but won't turn on grips

O_Eckmann — Mon, 15 May 2023 19:33:40 GMT

Hi @TheCanadianPrimate ,

If you prefer using my plug-in to query and show OD, you find 2 commands:

- 1st is to show OD in grid mode like FDO, you can sort by column and select rows => select corresponding objects

- or you can build a query according table, field and operator (specific operator according type of OD), and you can also obtain all existing value in drawing (interesting for textual value).

This free plug-in is available in general discussion on OD, but it should be available on autodesk store this week.

The plug-in was initially developped in french langage, but I've included a US button to "translate" some dialogs.

Below a video to show possible 2 way to select buildings with height between 30 and 38m.

(view in My Videos)

Olivier