[Geoserver-users] DescribeFeatureType problem

GeoServer GeoServer User
1

Hi Andrea,

the table is still empty, we are trying to use WFS-T to fill it but without
success right now. So I can't do a GetFeature as yet :slight_smile:

For reference:

http://support.esri.com/index.cfm?fa=knowledgebase.techArticles.articleShow&d=21938

Best regards,
Bart

--
Bart van den Eijnden
OSGIS, Open Source GIS
http://www.osgis.nl

--------- Oorspronkelijk bericht --------
Van: Andrea Aime <aaime@anonymised.com>
Naar: Bart van den Eijnden OSGIS <bartvde@anonymised.com>
Cc: geoserver-users@lists.sourceforge.net
Onderwerp: Re: [Geoserver-users] DescribeFeatureType problem
Datum: 23/01/08 06:09

Bart van den Eijnden (OSGIS) ha scritto:
&gt; Hi Andrea,
&gt;
&gt; this is the 1.1 response:
&gt;
....
&gt; &lt;xsd:element maxOccurs=&quot;1&quot;

minOccurs=&quot;0&quot; name=&quot;SE_ANNO_CAD_DATA&quot;

&gt; nillable=&quot;true&quot; type=&quot;xsd:hexBinary&quot;/&gt;

Ouch, what's this, a blob (binary large object)? I've never tried that
out, so this may well be what's causing WFS 1.0 to choke.
Curious, is WFS 1.1 able to encode the GetFeature response properly as
well? (if so, kudos to Justin for covering even this data type).

A workaround would be to setup a view so that the field above is not
going to be seen by GeoServer.

Cheers
Andrea

2

Bart van den Eijnden (OSGIS) ha scritto:

Hi Andrea,

the table is still empty, we are trying to use WFS-T to fill it but without
success right now. So I can't do a GetFeature as yet :slight_smile:

For reference:

http://support.esri.com/index.cfm?fa=knowledgebase.techArticles.articleShow&d=21938

Hum, not sure we could do anything good with this kind of
column... maybe it would be wiser to hide it at the datastore
level? Doing WFS-T on it may be problematic thought, is ArcSDE
able to fill in a default value if we don't provide one?

ArcSDE gurus needed here.
Cheers
Andrea

3

Hi Bart, sorry for the late response

the best I can think of to enable you using the table is to try a workaround
like ignoring this kind of columns in the geotools arcsde plugin as long as
they're nillable.
I could try that and send you a jar to try out. You don't need to set a value
for that column through WFS-T, right? if so would ignoring that column would
be enough for your needs?
Otherwise we should need to actually support blobs at arcsde (which is there
but never actually tried it), and which could be more complicated, on the WFS
side of the fence. That won't happen in the very near future though except
through some funded work or code donation, due to other higher priority
concerns.

Would you be willing to try out an arcsde jar with that workaround so?

Cheers,

Gabriel
On Wednesday 23 January 2008 10:19:51 am Andrea Aime wrote:

Bart van den Eijnden (OSGIS) ha scritto:
> Hi Andrea,
>
> the table is still empty, we are trying to use WFS-T to fill it but
> without success right now. So I can't do a GetFeature as yet :slight_smile:
>
> For reference:
>
> http://support.esri.com/index.cfm?fa=knowledgebase.techArticles.articleSh
>ow&d=21938

Hum, not sure we could do anything good with this kind of
column... maybe it would be wiser to hide it at the datastore
level? Doing WFS-T on it may be problematic thought, is ArcSDE
able to fill in a default value if we don't provide one?

ArcSDE gurus needed here.
Cheers
Andrea

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4045,479706d0282871804284693!