GML3 handles decoding and encoding, so for community-schema-ds we need
the encoder bindings to be sensible, right?
so does this mean that GML3 can only read simple features, and encode
simple features? Is this an arbitrary limitation (for some reason a
deliberate choice of bindings based on famili
Hello list, we are near to finish our TXT proposal called "Extension of CQL to
match abilities of Filter"
http://docs.codehaus.org/display/GEOTOOLS/Extention+of+CQL+to+match+abilities+of+Filter
In the inception phase we picked up the suggestions of a lot of people. Then
we were working to prov
Hello list, we are near to finish our TXT proposal called "Extension of CQL to
match abilities of Filter"
http://docs.codehaus.org/display/GEOTOOLS/Extention+of+CQL+to+match+abilities+of+Filter
In the inception phase we picked up the suggestions of a lot of people. Then
we were working to prov
Rob Atkinson ha scritto:
> GML3 handles decoding and encoding, so for community-schema-ds we need
> the encoder bindings to be sensible, right?
>
> so does this mean that GML3 can only read simple features, and encode
> simple features? Is this an arbitrary limitation (for some reason a
> delibera
Ben Caradoc-Davies ha scritto:
> As you are no doubt aware, I have been attempting to port GeoTools 2.4.x
> community-schemas-ds to trunk. The purpose of this port is to make use
> of GeoAPI 2.2 and its implementations in gt-main, so as to better
> support complex features. The intent is to get
Use SDO_FILTER instead of SDO_RELATE for BBOX queries
-
Key: GEOT-2062
URL: http://jira.codehaus.org/browse/GEOT-2062
Project: GeoTools
Issue Type: Bug
Components: data oraclespat
SimpleFeatureImpl.getProperty(name) NPE if the property is uknown, it should
return null instead
Key: GEOT-2061
URL: http://jira.codehaus.org/browse/GEOT-2061
CRS decode error
Key: GEOT-2063
URL: http://jira.codehaus.org/browse/GEOT-2063
Project: GeoTools
Issue Type: Bug
Components: data postgis
Affects Versions: 2.6-M0
Environment: any with postgis
Ben Caradoc-Davies wrote:
> Is there any documentation to ease GML3 transition from 2.4.x to trunk?
> I am attempting to port community-schemas from 2.4.x to trunk. I have
> fixed (I hope) many of the GeoAPI changes, but am running into problems
> with GML3 binding changes.
>
> There is nothing
Hi Ben,
So yes, at the moment there is no handling of any complex features so
the bindings all assume the flat feature model.
That being said, the parser itself is very flexible and allows you to
plug and override bindings as necessary. A possible path forward would
be this:
Create new bindin
Jody Garnett wrote:
> Justin Deoliveira wrote:
>> Hi Jody,
>>
>> First thing i want to make clear is that this is not the proposal to
>> make these things supported, just to restructure and continue to work
>> on getting them to supported. Having them in a single "h2" module is
>> not scaling an
SchemaIndex in xml parser / encoder leaks memory
Key: GEOT-2064
URL: http://jira.codehaus.org/browse/GEOT-2064
Project: GeoTools
Issue Type: Bug
Affects Versions: 2.5.0
Reporte
This all looks good; the only matter we are really voting on here is the
addition of a new class:
> class TXT {
> String toTXT( Expression );
> String toTXT( Filter );
> Expression toExpression( String );
> Expression toExpression( String, FilterFactory );
> Filter toFilter( St
Ben Caradoc-Davies wrote:
> features. The intent is to get rid of the nasty adapters used in
> community-schemas-ds to smuggle ISO features in the old gt2 feature
> model, and use the clean opengis Feature API (GeoAPI). This requires
> consistent use of the opengis API throughout.
Sounds great :
Justin Deoliveira wrote:
>> As such; if the modules are still unsupported; the only person you
>> need to answer to is yourself. Proposal would be over kill.
> Ok... I will happy keep working until we are ready to move to
> supported and will pipe up again when that happens.
Sounds good; note tha
The GeoTools 2.5 release is available for download:
* http://geotools.codehaus.org/2.5.0
The 2.5.0 release marks the first stable release of a number of exciting
developments and features of the 2.5.x series including:
* New feature model based on GeoAPI
* Java 5
* Support for units
16 matches
Mail list logo
