[Geotools-devel] CRS's in the new SimpleFeatureTypeBuilder

[Adrian C. <ac...@gm...>]

Hey Justin,

Your builders look really nice; seems like they will be fun to use. 


Martin and I discussed a bit the role of the CRS in the feature type.
This issue will only last until geotools moves to using DirectPositions
rather than JTS directly, however the issue is with us today.

We suggest that adding a jts geometry to any featureType whose crs has
not been explicitly set through some call to .setCRS(..) or to .crs(..)
should generate a WARNING. 

We suggest therefore that a user be allowed to set a CRS to null, e.g.
via a call .setCRS(null). That would allow the user to use geometries
for which they do not know the CRS but force them to set that
explicitly. Once the CRS is set to null (or to any other value), no
WARNING would be emitted.

Does that work for you? Perhaps this is already the case.


Note also I changed the Simple example your page:
  http://docs.codehaus.org/display/GEOTDOC/Feature+Model+Guide
to set the CRS before adding the geometry because I figured we wanted to
encourage 'good practice' in the doc. We should add, in one of the
alternative sections, .setCRS(null) if and when such functionality
exists.

--adrian