arcgisscripting and arcpy object model diagrams

[NathanWarmerdam]

For python scripters, the most useful piece of documentation at 9.x was the Geoprocessing Programming Model (seen here: http://webhelp.esri.com/arcgisdesktop/9.3/pdf/Geoprocessor_93.pdf).  This is extraordinarily useful because it presents the whole of arcgisscripting concisely on a single page.

In the documentation for 10.0, this item cannot be found for arcgisscripting or arcpy.  Can you please add this?

[HeikeBöge]

I miss the geoprocessor model diagram for 10. It would be very helpful.

[BrookeMedley]

Live by it.  Please update!

[AlexCatchpaugh2]

I need this to hang on my wall. Please update for 10

[LotharUlferts]

The OMD is my scout in dark nights of program disorientation...

[mattwilkie]

I am very happy for the improved intellisense. It's a very useful addition to the help resources, or at least it should have been an addition. I find the OMDs very helpful in seeing what's avialable at a glance and their positions relative to each other. We are poorer for not having them available (or better said as not being up to date).

(((sorry for the all-italics. I can't get the editor to turn it off)))

[HeatherFollis]

Please update.

[RussellKallstrom]

I strongly disagree with ESRI's position on this, and think an OMD should still be constructed, at least for 10.0.  First off, the quantum leap that countless Joe/Jane GIS users are making now is from VBA to Python to solve basic workflows, not arcgisscripting to arcpy.  Good for you if you already know Python, but it is fairly obvious that a lot of people are learning Python because of ESRI's ArcGIS 10.

Second, even if were just about a move from arcgisscripting to arcpy, Fox himself notes that those changes are much more than cosmetic.  There are small changes like cases of functions used to big changes like multiple modules.  Using an OMD for this fundamental design (10.0) change helps give a starting point, particularly when Python is now pretty much the only show in town.  It is nice that current Python experts can jump on in with a site package method of documentation, but that leaves a lot of people behind.  This makes it doubly difficult:  not constructing one ignores that the object haven't disappeared, but still exist, e.g., row, field, etc.  I've found help info on functions and so on, but it is not organized in a way that addresses the objects they manipulate.  To me, it's a little like giving someone a key and saying it can lock and unlock doors, but not telling them 1) if it's for a door and 2) what door it opens.  If you didn't know, you really wouldn't know where to start.  The OMD is quite simply, a map for arcpy, and I'm hoping that ESRI can see it that way.

[RobbynAbbitt1]

I agree - as a college instructor, having this diagram was invaluable for myself and my students.  The intelisense, while incredibly useful, does not help with the full learning process of putting together what all you can do with the scripting environment.  Please reconsider.

[deleted-user-nnQhchh4f8oI]

For new people, this is a must becasue the geoprocessor model is used in the class.

[GraziaZulian]

Would be a great help