Model Builder: Difference between revisions
Brian Wilson (talk | contribs) m Model builder moved to Model Builder |
Brian Wilson (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
ArcGIS 9.x has this | ArcGIS 9.x has this thing called "Model Builder" that lets you build flow charts* and then execute them. | ||
This gives you a starting point for writing your own Python [[Geoprocessing | Once you have a flow chart built and working, then you can export the code (Model->Export->To Script->Python). This gives you a starting point for writing your own Python [[Geoprocessing]] for use as components in Model Builder. | ||
* I think they call them "UML diagrams" now or something esoteric like that. | * I think they call them "UML diagrams" now or something esoteric like that. | ||
Revision as of 16:27, 26 April 2006
ArcGIS 9.x has this thing called "Model Builder" that lets you build flow charts* and then execute them.
Once you have a flow chart built and working, then you can export the code (Model->Export->To Script->Python). This gives you a starting point for writing your own Python Geoprocessing for use as components in Model Builder.
- I think they call them "UML diagrams" now or something esoteric like that.
In the beginning in programming classes, they made us draw flow charts. We all wrote the code first, then did the flow charts so that we'd get credit for doing our homework. Then they invented "top-down" programming, and we'd write our program then we'd to do pseudo-code to get all the points. Now we have to design flow charts first, then generate the code so that we can fix it up and make it run. Once you export the flow chart into the code, you can't go backwards so it's safe to throw the flow chart away.
