The Command Line Revisited
I’ve talked repeatedly about GIS command line tools being powerful. During the launch last week of Cityzenith, I was describing our Asq query tool to the audience and described it as the command line of Cityzenith.
Asq is simple, a query tool to search through our indexed data stores in Elastic. But is also much more, a way to manipulate what you see in your view. Using the GUI to add and work with files and layers is of course how must people will work with the product but being able to stack together commands to perform the same action is where the power is. Much like Automator on Mac OS X or similar scripting tools, the idea is to batch functions together in building blocks.
I don’t want users of Cityzenith to feel constrained by buttons, dialogs and options. Start typing and autocomplete takes care of your next decision. In showing our development team how you perform a Definition Query on ArcGIS Desktop, they were speachless at how many right clicks, OKs and other UI madness one must complete before getting something as simple as [PARK_NAME] = “Grant”. I want to type:
SHOW -> FILE -> PARK -> WHERE -> PARK_NAME -> IS -> “Grant”
That’s not even including all the spatial query functions we can do.
We just launched so this is the beginning of command line City Information Modeling (CIM). Cityzenith can help manage the built environment but taking control of all the aggregated data is critical. Hence Asq being the command line of Cityzenith.
If you’re interested in signing up, we’ve got a page to do that.