[Geotools-devel] A interesting contrast ... and a question?

[Jody G. <jga...@re...>]

We have tried to keep the API in GeoTools minimal, taking advantage of 
specifications etc...

The following article highlights another approach:
-<http://martinfowler.com/bliki/HumaneInterface.html>

That is kick out the stops and be a bit more human friendly, and well 
usable.
I would not mind going half way on this, using a more limited API for data
structures that communicate between subsystems (like Filter and Feature),
while making available implementations that are more human friendly.

Phrased another way, a lot of our utility methods should be looked at,
if they are being used to plug an API hole we should just apply the fix.
(A guide for this is if we need the utility method for internal use).

If they are being used to make a complex data structure approachable
perhaps we can add them to an abstract class for a more seamless
experience.

So here is the question - what is your favorite utility method?

I personally like:
- CRS.decode( code )

A close second is DataUtilities.createType( typeName, typeSpec )

Jody