[Geoserver-users] [Geotools-gt2-users] GS 1.5 RC2: Can I read wfs features without default geometry ?

GeoServer GeoServer User
1

Hi Justin,

Thanks for your response.

Datastore is oracle spatial 10g, but I'm surprised if it is really depend of the Datastore.
If a feature has geometry column works fine, but I din't get never a result if feture hasn't geometry, like this one.

Tanks & regards

Balazs

Request: http://localhost:8080/geoserver/wfs?Service=WFS&Version=1.0.0&Request=GetFeature&Typename=V_S_PLR

Answer:

<?xml version="1.0" ?>
- <ServiceExceptionReport version="1.2.0" xmlns="http://www.opengis.net/ogc&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation="http://www.opengis.net/ogc http://tsvie01chatt:9090/geoserver/schemas//wfs/1.0.0/OGC-exception.xsd&quot;&gt;
  <ServiceException>java.io.IOException: Feature type: wisa:V_S_PLR does not have a default geometry at org.vfny.geoserver.global.FeatureTypeInfo.getNativeCRS(FeatureTypeInfo.java:539) at org.vfny.geoserver.wfs.responses.GetFeatureResults.addFeatures(GetFeatureResults.java:177) at org.vfny.geoserver.wfs.responses.FeatureResponse.execute(FeatureResponse.java:324) at org.vfny.geoserver.wfs.responses.FeatureResponse.execute(FeatureResponse.java:139) at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService.java:516) at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.java:315) at org.geoserver.request.Dispatcher.dispatch(Dispatcher.java:192) at org.geoserver.request.Dispatcher.handleRequestInternal(Dispatcher.java:52) at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139) at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:684) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:625) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:392) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:347) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1050) at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:103) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:354) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141) at org.mortbay.jetty.Server.handle(Server.java:269) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:687) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:492) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339) at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)</ServiceException>
  </ServiceExceptionReport>

Schema:

<?xml version="1.0" encoding="ISO-8859-1" ?>
- <xs:schema targetNamespace="http://www.lfrz.at" xmlns:wisa="http://www.lfrz.at" xmlns:gml="http://www.opengis.net/gml&quot; xmlns:xs="http://www.w3.org/2001/XMLSchema&quot; xmlns:citef="http://www.opengis.net/cite/functions&quot; elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
  <xs:import namespace="http://www.opengis.net/gml&quot; schemaLocation="http://tsvie01chatt:9090/geoserver/schemas/gml/2.1.2/feature.xsd&quot; />
- <xs:complexType name="V_S_PLR_Type">
- <xs:complexContent>
- <xs:extension base="gml:AbstractFeatureType">
- <xs:sequence>
  <xs:element type="xs:decimal" minOccurs="1" name="PLR_ID" nillable="false" maxOccurs="1" />
  <xs:element type="xs:string" minOccurs="1" name="PLR_DESCRIPTION" nillable="false" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="V_S_PLR" type="wisa:V_S_PLR_Type" substitutionGroup="gml:_Feature" />

-----Ursprüngliche Nachricht-----
Von: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Gesendet: Montag, 26. März 2007 20:14
An: Szakacs, Balazs
Cc: geotools-gt2-users@lists.sourceforge.net
Betreff: Re: [Geotools-gt2-users] GS 1.5 RC2: Can I read wfs features
without default geometry ?

Hi Balazs,

It could very well depend on type of datastore you are using. If you
could include that information it would be helpful. It would also help
to know which request you are making and the entire stack trace which
results.

Also, this discussion will be more appropriate if moved to
geoserver-users@anonymised.com

Thanks,

-Justin

Szakacs, Balazs wrote:
> Hi Group
>
>
>
> Can I read wfs features with GS 1.5 RC2 if it does not have geometry
> parameter?
>
>
>
> With GS 1.5 I can set up a feature without geometry, like GS 1.3.3, but
> if I try to read it I get a exception: "geoserver java.io.IOException:
> Feature type: <Feature name> does not have a default geometry "
>
> The same was no problem with GS 1.3.3
>
>
>
> Please let me know, how I can read it.
>
>
>
> Thanks for support
>
>
>
> Balazs
>
>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
-
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
your
> opinions on IT & business topics through brief surveys-and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geotools-gt2-users mailing list
> Geotools-gt2-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

2

Hi Balazs,

So yes it appears that the exception is explicitly thrown when a feature does not have a geometric attribute. Wether this can be considered a bug or not I am not 100% sure.

Developers: have we ever supported the encoding of features without geometry? Does anyone know of other WFS's that support it?

-Justin

Szakacs, Balazs wrote:

Hi Justin,

Thanks for your response.

Datastore is oracle spatial 10g, but I'm surprised if it is really depend of the Datastore.
If a feature has geometry column works fine, but I din't get never a result if feture hasn't geometry, like this one.

Tanks & regards

Balazs

Request: http://localhost:8080/geoserver/wfs?Service=WFS&Version=1.0.0&Request=GetFeature&Typename=V_S_PLR

Answer:

<?xml version="1.0" ?> - <ServiceExceptionReport version="1.2.0" xmlns="http://www.opengis.net/ogc&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation="http://www.opengis.net/ogc http://tsvie01chatt:9090/geoserver/schemas//wfs/1.0.0/OGC-exception.xsd&quot;&gt;
  <ServiceException>java.io.IOException: Feature type: wisa:V_S_PLR does not have a default geometry at org.vfny.geoserver.global.FeatureTypeInfo.getNativeCRS(FeatureTypeInfo.java:539) at org.vfny.geoserver.wfs.responses.GetFeatureResults.addFeatures(GetFeatureResults.java:177) at org.vfny.geoserver.wfs.responses.FeatureResponse.execute(FeatureResponse.java:324) at org.vfny.geoserver.wfs.responses.FeatureResponse.execute(FeatureResponse.java:139) at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService.java:516) at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.java:315) at org.geoserver.request.Dispatcher.dispatch(Dispatcher.java:192) at org.geoserver.request.Dispatcher.handleRequestInternal(Dispatcher.java:52) at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139) at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44) at org.spring

framework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:684) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:625) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:392) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:347) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1050) at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:103) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:354) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226) at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141) at org.mortbay.jetty.Server.handle(Server.java:269) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:687) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:492) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339) at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)</ServiceException>

  </ServiceExceptionReport>

Schema:

<?xml version="1.0" encoding="ISO-8859-1" ?> - <xs:schema targetNamespace="http://www.lfrz.at" xmlns:wisa="http://www.lfrz.at" xmlns:gml="http://www.opengis.net/gml&quot; xmlns:xs="http://www.w3.org/2001/XMLSchema&quot; xmlns:citef="http://www.opengis.net/cite/functions&quot; elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
  <xs:import namespace="http://www.opengis.net/gml&quot; schemaLocation="http://tsvie01chatt:9090/geoserver/schemas/gml/2.1.2/feature.xsd&quot; /> - <xs:complexType name="V_S_PLR_Type">
- <xs:complexContent>
- <xs:extension base="gml:AbstractFeatureType">
- <xs:sequence>
  <xs:element type="xs:decimal" minOccurs="1" name="PLR_ID" nillable="false" maxOccurs="1" /> <xs:element type="xs:string" minOccurs="1" name="PLR_DESCRIPTION" nillable="false" maxOccurs="1" /> </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="V_S_PLR" type="wisa:V_S_PLR_Type" substitutionGroup="gml:_Feature" />

-----Ursprüngliche Nachricht-----
Von: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Gesendet: Montag, 26. März 2007 20:14
An: Szakacs, Balazs
Cc: geotools-gt2-users@lists.sourceforge.net
Betreff: Re: [Geotools-gt2-users] GS 1.5 RC2: Can I read wfs features
without default geometry ?

Hi Balazs,

It could very well depend on type of datastore you are using. If you
could include that information it would be helpful. It would also help
to know which request you are making and the entire stack trace which
results.

Also, this discussion will be more appropriate if moved to
geoserver-users@anonymised.com

Thanks,

-Justin

Szakacs, Balazs wrote:

Hi Group

Can I read wfs features with GS 1.5 RC2 if it does not have geometry
parameter?

With GS 1.5 I can set up a feature without geometry, like GS 1.3.3, but
if I try to read it I get a exception: "geoserver java.io.IOException:
Feature type: <Feature name> does not have a default geometry "

The same was no problem with GS 1.3.3

Please let me know, how I can read it.

Thanks for support

Balazs

------------------------------------------------------------------------

------------------------------------------------------------------------

-

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share

your

opinions on IT & business topics through brief surveys-and earn cash

http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

------------------------------------------------------------------------

_______________________________________________
Geotools-gt2-users mailing list
Geotools-gt2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

3

Hi,

Whether this feature exists or not at the moment I know a real world example where it would be useful. For example we have administrational registers where new features are created first directly into the database (creation of a new customer etc.) but they have to be digitised on a map afterwards. Now it is possible to request a corresponding feature type without any information about this new item by WFS, add new feature on a map, add the corresponding attribute data and then insert the new geometry with attributes into the database with WFS-T. However, attribute data must be queried separately and transfer to the new feature as a separate process.
Workflow would be much easier if the item could first be queried without geometry but with attributes through WFS, geometry could be added by GIS-client and then sent back to database as update through WFS-T. And all this could be performed with standard WFS tools without a need to have customised software components in the middle.

I guess there might be problems in counting bounding boxes etc. especially if WFS request returns no features with geometry. Perhaps then some defaults could be used, in first hand the extents of the returned features which have geometry, and secondly the extents of the whole feature type?

Just thinking,

-Jukka Rahkonen-

________________________________

Lähettäjä: geoserver-users-bounces@lists.sourceforge.net puolesta: Justin Deoliveira
Lähetetty: ke 28.3.2007 8:05
Vastaanottaja: Szakacs, Balazs
Kopio: geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] [Geotools-gt2-users] GS 1.5 RC2: Can I read wfs features without default geometry ?

Hi Balazs,

So yes it appears that the exception is explicitly thrown when a feature
  does not have a geometric attribute. Wether this can be considered a
bug or not I am not 100% sure.

Developers: have we ever supported the encoding of features without
geometry? Does anyone know of other WFS's that support it?

-Justin

Szakacs, Balazs wrote:

Hi Justin,

Thanks for your response.

Datastore is oracle spatial 10g, but I'm surprised if it is really depend of the Datastore.
If a feature has geometry column works fine, but I din't get never a result if feture hasn't geometry, like this one.

Tanks & regards

Balazs

Request: http://localhost:8080/geoserver/wfs?Service=WFS&Version=1.0.0&Request=GetFeature&Typename=V_S_PLR

Answer:

<?xml version="1.0" ?>
- <ServiceExceptionReport version="1.2.0" xmlns="http://www.opengis.net/ogc&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation="http://www.opengis.net/ogc http://tsvie01chatt:9090/geoserver/schemas//wfs/1.0.0/OGC-exception.xsd&quot;&gt;
  <ServiceException>java.io.IOException: Feature type: wisa:V_S_PLR does not have a default geometry at org.vfny.geoserver.global.FeatureTypeInfo.getNativeCRS(FeatureTypeInfo.java:539) at org.vfny.geoserver.wfs.responses.GetFeatureResults.addFeatures(GetFeatureResults.java:177) at org.vfny.geoserver.wfs.responses.FeatureResponse.execute(FeatureResponse.java:324) at org.vfny.geoserver.wfs.responses.FeatureResponse.execute(FeatureResponse.java:139) at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService.java:516) at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.java:315) at org.geoserver.request.Dispatcher.dispatch(Dispatcher.java:192) at org.geoserver.request.Dispatcher.handleRequestInternal(Dispatcher.java:52) at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139) at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44) at org.spring

framework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:684) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:625) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:392) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:347) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1050) at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:103) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:354) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226) at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141) at org.mortbay.jetty.Server.handle(Server.java:269) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:687) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:492) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339) at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)</ServiceException>

  </ServiceExceptionReport>

Schema:

<?xml version="1.0" encoding="ISO-8859-1" ?>
- <xs:schema targetNamespace="http://www.lfrz.at" xmlns:wisa="http://www.lfrz.at" xmlns:gml="http://www.opengis.net/gml&quot; xmlns:xs="http://www.w3.org/2001/XMLSchema&quot; xmlns:citef="http://www.opengis.net/cite/functions&quot; elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
  <xs:import namespace="http://www.opengis.net/gml&quot; schemaLocation="http://tsvie01chatt:9090/geoserver/schemas/gml/2.1.2/feature.xsd&quot; />
- <xs:complexType name="V_S_PLR_Type">
- <xs:complexContent>
- <xs:extension base="gml:AbstractFeatureType">
- <xs:sequence>
  <xs:element type="xs:decimal" minOccurs="1" name="PLR_ID" nillable="false" maxOccurs="1" />
  <xs:element type="xs:string" minOccurs="1" name="PLR_DESCRIPTION" nillable="false" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="V_S_PLR" type="wisa:V_S_PLR_Type" substitutionGroup="gml:_Feature" />

-----Ursprüngliche Nachricht-----
Von: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Gesendet: Montag, 26. März 2007 20:14
An: Szakacs, Balazs
Cc: geotools-gt2-users@lists.sourceforge.net
Betreff: Re: [Geotools-gt2-users] GS 1.5 RC2: Can I read wfs features
without default geometry ?

Hi Balazs,

It could very well depend on type of datastore you are using. If you
could include that information it would be helpful. It would also help
to know which request you are making and the entire stack trace which
results.

Also, this discussion will be more appropriate if moved to
geoserver-users@anonymised.com

Thanks,

-Justin

Szakacs, Balazs wrote:

Hi Group

Can I read wfs features with GS 1.5 RC2 if it does not have geometry
parameter?

With GS 1.5 I can set up a feature without geometry, like GS 1.3.3, but
if I try to read it I get a exception: "geoserver java.io.IOException:
Feature type: <Feature name> does not have a default geometry "

The same was no problem with GS 1.3.3

Please let me know, how I can read it.

Thanks for support

Balazs

------------------------------------------------------------------------

------------------------------------------------------------------------

-

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share

your

opinions on IT & business topics through brief surveys-and earn cash

http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

------------------------------------------------------------------------

_______________________________________________
Geotools-gt2-users mailing list
Geotools-gt2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

4

Justin Deoliveira ha scritto:

Hi Balazs,

So yes it appears that the exception is explicitly thrown when a feature does not have a geometric attribute. Wether this can be considered a bug or not I am not 100% sure.

Developers: have we ever supported the encoding of features without geometry? Does anyone know of other WFS's that support it?

I guess the real question is, does GML support the concept of a feature without geometry attributes? The answer is yes afaik.

The real issue is that most modules in geotools are designed assuming
a geometry will be there, as everything is Geoserver is (the exception
is really thrown by FeatureTypeInfo.getNativeCRS(), that is, Geoserver code).

So, imho this is a direction where we should go, but it's not at all
trivial, since default geometry is widely used. To give you an idea,
FeatureType.getDefaultGeometry() is used in 87 places in the geoserver
code + geotools code that geoserver uses, and Feature.getDefaultGeometry() in 119 places (it's quite likely we would
not have to check usage in 200 places, but a quick guesstimate is that 50 fixes here and there are probably needed).

Cheers
Andrea

5

Hey guys,

it's worth noting that if I understand right, the ArcSDE plugin does this right now. I.e., the default geometry is allowed to be null and then be updated later. SDE allows null geometries, and I have created an application based on a spatial table with a whole bunch of rows, each of which has a null geometry. The point of the application is to go through each row and 'digitize' in a feature that describes that particular row.

Well, at least the ArcSDE plugin is supposed to do this. I added a unit test that's passing now, but for a while I would fix it and then each version change (2.2-2.3-2.4) would break it again.

--saul

-----Original Message-----
From: geoserver-users-bounces@lists.sourceforge.net on behalf of Andrea Aime
Sent: Wed 3/28/2007 4:27 AM
To: Justin Deoliveira
Cc: Szakacs, Balazs; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] [Geotools-gt2-users] GS 1.5 RC2: Can I read wfs features without default geometry ?

Justin Deoliveira ha scritto:

Hi Balazs,

So yes it appears that the exception is explicitly thrown when a feature
  does not have a geometric attribute. Wether this can be considered a
bug or not I am not 100% sure.

Developers: have we ever supported the encoding of features without
geometry? Does anyone know of other WFS's that support it?

I guess the real question is, does GML support the concept of a feature
without geometry attributes? The answer is yes afaik.

The real issue is that most modules in geotools are designed assuming
a geometry will be there, as everything is Geoserver is (the exception
is really thrown by FeatureTypeInfo.getNativeCRS(), that is, Geoserver
code).

So, imho this is a direction where we should go, but it's not at all
trivial, since default geometry is widely used. To give you an idea,
FeatureType.getDefaultGeometry() is used in 87 places in the geoserver
code + geotools code that geoserver uses, and
Feature.getDefaultGeometry() in 119 places (it's quite likely we would
not have to check usage in 200 places, but a quick guesstimate is that
50 fixes here and there are probably needed).

Cheers
Andrea

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

6

Rahkonen Jukka ha scritto:

Hi,

Whether this feature exists or not at the moment I know a real world
example where it would be useful. For example we have
administrational registers where new features are created first
directly into the database (creation of a new customer etc.) but they
have to be digitised on a map afterwards. Now it is possible to
request a corresponding feature type without any information about
this new item by WFS, add new feature on a map, add the corresponding
attribute data and then insert the new geometry with attributes into
the database with WFS-T. However, attribute data must be queried
separately and transfer to the new feature as a separate process. Workflow would be much easier if the item could first be queried
without geometry but with attributes through WFS, geometry could be
added by GIS-client and then sent back to database as update through
WFS-T. And all this could be performed with standard WFS tools
without a need to have customised software components in the middle.

I guess there might be problems in counting bounding boxes etc.
especially if WFS request returns no features with geometry. Perhaps
then some defaults could be used, in first hand the extents of the
returned features which have geometry, and secondly the extents of
the whole feature type?

Rahkonen, did you try and failed with a specific datastore?
Cheers
Andrea

7

Farber, Saul (ENV) ha scritto:

Hey guys,

it's worth noting that if I understand right, the ArcSDE plugin does
this right now. I.e., the default geometry is allowed to be null and
then be updated later.

Saul,
Balazs case is a little different. The exception seems to suggest he
does not have a geometry column in his schema at all. That's the only
way to get the exception he got. He's really trying to serve non geographic objects thru WFS.

Cheers
Andrea

8

Does anybody know if it is possible to have bitwise operator in SLD files ?

I hve the following data

Geom, attributes

Where attributes is an integer containing bit values as follows -

0x01 - motorway
0x02 - a road
0x04 - b road
0x08 - single carriageway
0x10 - dual carriageway

I want to draw dual carriageway A roads in dark green and single carriageway A roads in light green -

((attributes & 0x0a) == 0x0a) use dark green
((attributes & 0x12) == 0x12) use light green

Richard Shaw

¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤

Richard Shaw
Technical Design Authority - Information Solutions Consultancy
Intelligent Transport Systems

Atkins Highways and Transportation
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW

Tel: +44 (0) 1372 756407
Fax: +44 (0) 1372 740055
Mob: 07740 817586
E-mail: richard.shaw@anonymised.com

www.atkinsglobal.com/its

This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.

The ultimate parent company of the Atkins Group is WS Atkins plc. Registered in England No. 1885586. Registered Office Woodcote Grove, Ashley Road, Epsom, Surrey KT18 5BW.

Consider the environment. Please don't print this e-mail unless you really need to.

9

Hi Richard,

I do not believe there is anything in the Filter spec directly which
will support this. However with a little bit of coding you should be
able to achieve this with filter functions. For instance.

<Filter>
  <PropertyIsEqualTo>
    <Function name="bitwiseAnd">
       <PropertyName>attributes</PropertyName>
       <Literal>0a</Literal>
    <Function>
    <Literal>0a</Literal>
  </PropertyIsEqualTo>
</Filter>

To pull this off you would have to implement the "bitewiseAnd" function
at the geotools level. An implementation might look something like:

class BitwiseAndFunction extends
org.geotools.filter.FunctionExpressionImpl {

  public BitwiseAndFunction() {
    super("bitwiseAnd");
  }

  public int getArgCount() {
     return 2;
  }

  public Object evaluate( Object feature ) {
     //get the value of attribute as an integer
     Integer value = getExpression(0).evaluate(feature, Integer.class);

     //get the string value of the mask
     String mask = getExpression(1).evaluate(null);

     //convert the mask to int
     int intMask = Integer.parseInt( mask, 16 ):

     return Integer.toHexString( value.intValue() & intMask );
  }
}

This is just a crack off the top of my head so I am sure it will not
work as written :), but the general strategy holds.

Hopefully this makes sense. If you have any more questions or anything
is unclear please don't hesitate to ask.

-Justin

Shaw, Richard A wrote:

Does anybody know if it is possible to have bitwise operator in SLD files ?

I hve the following data

Geom, attributes

Where attributes is an integer containing bit values as follows -

0x01 - motorway
0x02 - a road
0x04 - b road
0x08 - single carriageway
0x10 - dual carriageway

I want to draw dual carriageway A roads in dark green and single carriageway A roads in light green -

((attributes & 0x0a) == 0x0a) use dark green
((attributes & 0x12) == 0x12) use light green

Richard Shaw

¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤

Richard Shaw
Technical Design Authority - Information Solutions Consultancy
Intelligent Transport Systems

Atkins Highways and Transportation
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW

Tel: +44 (0) 1372 756407
Fax: +44 (0) 1372 740055
Mob: 07740 817586
E-mail: richard.shaw@anonymised.com

www.atkinsglobal.com/its

This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.

The ultimate parent company of the Atkins Group is WS Atkins plc. Registered in England No. 1885586. Registered Office Woodcote Grove, Ashley Road, Epsom, Surrey KT18 5BW.

Consider the environment. Please don't print this e-mail unless you really need to.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,466f328550591637810514!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com