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.

Back in the 90s I used AutoCAD for much of my data creation because it made it simple to model the built environment. Before the madness of AutoCAD 13, the DOS based approach of having a command line at the bottom of the window made its use so much better than having to navigate toolbars and menus. Windows 95 and Mac OS destroyed the command line tools to the point we have things like Ribbon Interfaces and stackable toolbars. Its so much at this point that I try and do most of my GIS processes in the command line using Python or Javascript.

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.