Development

To submit a bug report please check that it is not already in the bug list below. If not, useful information to include in your report is:

1. the most useful thing you can provide is a small, zipped sample of data that can be used to replicate the problem (if applicable)
2. the full text of any error messages that were generated
3. the text of the command that caused the error
4. comments on anything unusual about your circumstances (e.g. is the input data massive, or on a network drive, or you have restricted permissions to access it?)

I am also happy to hear your suggestions for improvements: either modifications to existing tools or new functionality. To submit a suggestion, please check that your suggestion is not already in the Improvements list below, and please be as specific as possible.

If you have more general opinions or comments you would like to share with everyone, please do email them to me and make it clear that your comments are intended to be public. All comments will be presented anonymously unless you specifically and unambiguously instruct me on how to cite you.

1. Copy from output window. The keyboard shortcut Control-C does not work when trying to copy text from the output window. Instead, you must right-click the selected text and select Copy from the context menu. I have so far been unable to find a solution to this problem. If you are a programmer and have ideas about how to fix it then I would be interested to hear from you (I have tried PreviewKeyDown and IMessageFilter approaches, but neither work. A stand-alone application works fine, but there is something about a class library and/or an ArcGIS extension that causes this to fail in the GME extension).

Fundamental changes to the design of GME:

1. Projection awareness. Include on-the-fly projection changes when working with data with different projections.
2. Python support. Make the GME command line callable from Python directly, without having to go through the Model Builder tool.
3. Improved Model Builder integration. Make these commands better integrated with Model Builder, especially so that the output of the GME commands can feed into other Model Builder tools.
4. Add stand-alone application. Make GME a stand-alone application so that you do not have to start ArcMap in order to run it (although it still requires an ArcMap license).
5. Switch to open source GIS engine. In the long term, switch to an open source GIS engine like SAGA, GRASS, or uDIG/Geotools, and make GME open source and cross-platform.

Changes to existing commands:

1. isectpolyrst. Allow the user to select a subset of statistical summary fields to add rather than all of these:MN, MIN, MAX, STD, CNT, MED.

New functionality (these are a few examples of forthcoming commands):

1. isopleths. A command to generate isopleths based on a continuous raster surface, and output them as either lines, polygons or donut polygons (similar to the Percent Contour tool in HawthsTools). Users will be able to specify a list of isopleth levels to generate.
2. for each. A 'for each' command, similar to the existing 'for loop' command, but that processes a collection of objects in a folder or geodatabase. For instance, the for each loop would allow the user to specify a series of commands that would be applied to each raster or vector dataset in a folder.
3. deletedatasource. A command to delete datasets.
4. genraster. A command to create new raster layers based on statistical distributions, or more complex algorithms. Useful for stochastic modelling.
5. convert.linestosegments. Splits polylines into their constituent segments.

So far no users have submitted public comments.