epicureanism/inspire-foss

Automatically exported from code.google.com/p/inspire-foss

inspire-foss's Issues

thedeegree3 JSF console interface needs to be secured

What steps will reproduce the problem?
1. deploy the deegree3 INSPIRE WFS/WMS
2. go to console
3. one can manipulate all resources 

What is the expected output? What do you see instead?
Expected some form of login-security. 

Please use labels and text to provide additional information.

A temp solution could be to put all console-related pages under a single 
directory root that is secured using (e.g. Apache) basic HTTP authentication.

Original issue reported on code.google.com by [email protected] on 14 Sep 2010 at 10:42

DescribeFeatureType request fails with NPE when invoked with no feature type names

What steps will reproduce the problem?
1. run the deegree3 wfs (see /webapps/deegree3)
2. start OGC web client
3. invoke DescribeFeatureType (with no feature type names)

What is the expected output? What do you see instead?
Valid response describing all feature types. 
Instead an exception (NPE) is thrown.

This is due to a NULL value passed to the constructor of DescribeFeatureType 
within DescribeFeatureTypeXMLAdapter.parse110()
followed by accessing this NULL value in 
DescribeFeatureTypeHandler.doDescribeFeatureType() when no feature types given 
with request


Please use labels and text to provide additional information.

This is the request:

<?xml version="1.0" encoding="UTF-8"?>
<wfs:DescribeFeatureType version="1.1.0" service="WFS" 
xmlns:wfs="http://www.opengis.net/wfs" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd" outputFormat="text/xml; 
subtype=gml/3.2.1">
</wfs:DescribeFeatureType>


This is the empty owsException:

<?xml version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.opengis.net/ows 
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd" version="1.0.0">
  <ows:Exception exceptionCode="NoApplicableCode">
    <ows:ExceptionText></ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

This is the exception raised:

java.lang.NullPointerException
    at org.deegree.services.wfs.DescribeFeatureTypeHandler.doDescribeFeatureType(DescribeFeatureTypeHandler.java:181)
    at org.deegree.services.wfs.WFSController.doXML(WFSController.java:433)
    at org.deegree.services.controller.OGCFrontController.dispatchXMLRequest(OGCFrontController.java:700)
    at org.deegree.services.controller.OGCFrontController.doPost(OGCFrontController.java:475)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

Original issue reported on code.google.com by [email protected] on 20 Sep 2010 at 10:21

PostgreSQL/PostGIS driver conflict during webapp init

What steps will reproduce the problem?
1. having multiple (deegree) instances using PostgreSQL/GIS drivers 
2. when starting the container the deegree3 (most recent) webapps gives JDBC 
loading exception ("No suitable driver found" see exception below)
3. happens with cold startup restart or redeploy

Running on Ubuntu, Java6, PostgreSQL 8.3, PostGIS 1.4, Tomcat 6.0.20

What is the expected output? What do you see instead?
Normal init. The strange thing is that all JDBC actions go ok after, so the 
driver is initialized.

This is the observed output.

[10:46:52] ERROR: [FeatureStoreManager] Error creating feature store: No 
suitable driver found for jdbc:postgresql://localhost:5432/inspire_blob
org.deegree.feature.persistence.FeatureStoreException: No suitable driver found 
for jdbc:postgresql://localhost:5432/inspire_blob
    at org.deegree.feature.persistence.postgis.PostGISFeatureStore.init(PostGISFeatureStore.java:518)
    at org.deegree.feature.persistence.FeatureStoreManager.registerAndInit(FeatureStoreManager.java:209)
    at org.deegree.feature.persistence.FeatureStoreManager.init(FeatureStoreManager.java:131)
    at org.deegree.commons.config.DeegreeWorkspace.initAll(DeegreeWorkspace.java:216)
    at org.deegree.services.controller.OGCFrontController.initWorkspace(OGCFrontController.java:888)
    at org.deegree.services.controller.OGCFrontController.init(OGCFrontController.java:868)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
.jar

Please use labels and text to provide additional information.
Within the Tomcat container I have the following webapps. These start in this 
order and have the following driver versions:

1. deegree-wfs v2.4 OK
postgresql-8.3-603.jdbc3.jar
postgis-1.3.3.jar

2. deegree(3) inspire demo OK (uses memory store only)
postgresql-8.4-701.jdbc4.jar
postgis-jdbc-1.3.3.jar

3. deegree3 FAILS ("No suitable driver found")
postgresql-8.4-701.jdbc4.jar
postgis-jdbc-1.3.3.jar

4. GeoServer 2.0+ OK
postgresql-8.4-701.jdbc3.jar
gt-jdbc-postgis-2.6.4

1. and 3. use the same username but different DBs (inspire and inspire_blob)...

If I make 3. the only webapp in the Tomcat container then init is OK.

Original issue reported on code.google.com by [email protected] on 20 Sep 2010 at 12:49

deegree FSLoader error (deegree-tools-base 3.1pre11)

I am trying to get the FSLoader working again but it fails (see below). I 
remember from Bolsena that there were some changes from deegree 3.0 to 3.1 and 
that we changed stuff in the workspace. I have checked-in everything. Also 
going back to 3.0.4 does not work for me, so I am stuck. Hopefully it is a 
simple issue like changing stuff in the workspace....

Steps

1. install deegree-tools (cd tools/loader/deegree-tools: .get-deegree-tools.sh; 
install-deegree-tools.sh) 
2. try to load data in the DB e.g. using 
/etl/NL.Kadaster/AdministrativeUnits/test/load.sh (uses config 
/webapps/deegree3/src/main/webapp/WEB-INF/workspace/jdbc/inspire_blob.xml)
3. observe errors

What is the expected output? What do you see instead?
/Users/just/project/customers/kadaster/svn/project/inspire-foss/trunk/tools/load
er/../../webapps/deegree3/src/main/webapp/WEB-INF/workspace/datasources/feature/
inspire-postgis.xml 
/Users/just/project/customers/kadaster/svn/project/inspire-foss/trunk/tools/load
er/../../webapps/deegree3/src/main/webapp/WEB-INF/workspace/jdbc/inspire_blob.xm
l GML_32 USE_EXISTING gemeente-au.xml

Exception in thread "main" java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.deegree.commons.tools.ToolBox$ToolInfo.invoke(ToolBox.java:412)
    at org.deegree.commons.tools.ToolBox.main(ToolBox.java:201)
Caused by: java.lang.NullPointerException: Name is null
    at java.lang.Enum.valueOf(Enum.java:195)
    at org.deegree.tools.feature.persistence.FeatureStoreLoader$Action.valueOf(FeatureStoreLoader.java:94)
    at org.deegree.tools.feature.persistence.FeatureStoreLoader.main(FeatureStoreLoader.java:180)
    ... 6 more

Original issue reported on code.google.com by [email protected] on 18 Aug 2011 at 1:21

GetCapabilities gives error on PostGIS Extent query

What steps will reproduce the problem?
1. insert some features such that gml_objects is populated
2. GetFeature requests are all OK.
3. perform a GetCapabilities

What is the expected output? What do you see instead?
Expect to see Capabilties listed, instead getting OWS Exception:
"org.postgresql.util.PGobject cannot be cast to org.postgis.PGboxbase"

This is the stack trace. This happens when the result of the Extent query is 
non-empty. GetCapabilities is OK with an empty gml_objects table.

java.lang.ClassCastException: org.postgresql.util.PGobject cannot be cast to 
org.postgis.PGboxbase
    at org.deegree.feature.persistence.postgis.PostGISFeatureStore.getEnvelope(PostGISFeatureStore.java:325)
    at org.deegree.feature.persistence.postgis.PostGISFeatureStore.getEnvelope(PostGISFeatureStore.java:195)
    at org.deegree.services.wfs.GetCapabilitiesHandler.export110(GetCapabilitiesHandler.java:577)
    at org.deegree.services.wfs.GetCapabilitiesHandler.export(GetCapabilitiesHandler.java:174)
    at org.deegree.services.wfs.WFSController.doGetCapabilities(WFSController.java:690)
    at org.deegree.services.wfs.WFSController.doXML(WFSController.java:439)
    at org.deegree.services.controller.OGCFrontController.dispatchXMLRequest(OGCFrontController.java:700)
    at org.deegree.services.controller.OGCFrontController.doPost(OGCFrontController.java:475)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

This also happens when running standalone (one webapp in a container).

Additional version info:
platforms: Mac OSX and Ubuntu
Java: Java6
DB: Postgresql 8.3
PostGIS: 1.4.0
drivers: postgis-jdbc-1.3.3.jar postgresql-8.4-701.jdbc4.jar

I think there is somewhere a Driver mismatch.
I tried changing Drivers: using e.g. postgis-jdbc-1.4.0.jar or postgresql 
8.3/jdbc3 but all with the same result. It is strange since all other PostGIS 
actions (insert, query) don't give errors.
I can't figure this out further. Could be that the combination PG 8.3 + PostGIS 
1.4.0 is uncommon.

Original issue reported on code.google.com by [email protected] on 16 Sep 2010 at 1:54

Provide a Feature loader script for inserting GML features from a GML file

deegree3 supports loading features either through WFS-T or through its custom 
FeatureStore API taking a GML file as input.

There are already tools (main()) programs in deeegree-tools. This task is to 
figure out the most optimal way for creating a loader script that calls the 
deegree loader main(). A starting point may be the (shell) scripts used in the 
FOSS4G2010 complex feature store tutorial, or from deegree-demos.

The ultimate solution would be to use a generic WFS-T loader, but if FSLoader 
is a quicker solution for now that is ok.

Original issue reported on code.google.com by [email protected] on 16 Sep 2010 at 2:09

Insert of inlined Address feature fails

What steps will reproduce the problem?

1. build deegree latest from SVN (I used rev 26769 on 15.sep.2010)
2. start the deegree3 client and go to OGC web client 
3. execute Addresses choose Transaction | Insert_One_Address_Inlined request

What is the expected output? What do you see instead?
Expected is a successful insert of 4 features (1 Address + 3 components)

Inserting the inlined feature above worked for me on 14.sep.2010 with an 
earlier SVN rev. XLinked feature insert works ok.

Observed is an ows:ExceptionReport with exceptionCode="InvalidParameterValue" 
The stack trace gives

class org.deegree.commons.xml.XMLParsingException: Error in XML document (line: 
64, column: 51, character offset: 3413): Expected feature of type 
"{urn:x-inspire:specification:gmlas:Addresses:3.0}AddressComponent" in property 
"{urn:x-inspire:specification:gmlas:Addresses:3.0}component", but found element 
with name "{urn:x-inspire:specification:gmlas:Addresses:3.0}AddressAreaName".
<< is empty >>
    at org.deegree.gml.feature.GMLFeatureReader.parseFeatureProperty(GMLFeatureReader.java:514)
    at org.deegree.gml.feature.GMLFeatureReader.parseProperty(GMLFeatureReader.java:447)
    at org.deegree.gml.feature.GMLFeatureReader.parseFeature(GMLFeatureReader.java:319)
    at org.deegree.gml.GMLStreamReader.readFeature(GMLStreamReader.java:218)
    at org.deegree.services.wfs.TransactionHandler.parseWFSFeatureCollection(TransactionHandler.java:437)
    at org.deegree.services.wfs.TransactionHandler.parseFeaturesOrCollection(TransactionHandler.java:386)
    at org.deegree.services.wfs.TransactionHandler.doInsert(TransactionHandler.java:340)
    at org.deegree.services.wfs.TransactionHandler.doTransaction(TransactionHandler.java:199)
Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 15 Sep 2010 at 11:35

Solve issues that arose from Kadaster ESDIN ExM WFS testing

During ESDIN service testing the following issues arose with Kadaster ExM WFS 
testing. This is to keep track of these issues.


* srsName is EPSG:4326 instead of  urn:ogc:def:crs:EPSG::4258 or 
http://www.opengis.net/def/crs/EPSG/0/4258

* codeSpace/codeList attribute is not present in property 
xlau:AdministrativeUnit/au:nationalLevel, gn:GeographicalName/gn:nativeness and 
others

* no gml:identifier property

* nilReason values not 'unknown' or 'other:unpopulated', if provided. Value 
'UNPOPULATED' found.

* locale is not dereferencable, values are 'nl-NL' and not a URI to a 
gmd:PT_Locale

* nilReason is missing, but must be 'other:unpopulated' in property 
xlau:AdministrativeUnit/au:condominium

* Geometries not in Europe or the European overseas territories: 6.80333796, 
53.31592001 - Axis order must be lat/lon not lon/lat

Original issue reported on code.google.com by [email protected] on 14 Feb 2011 at 1:54

Calling DescribeFeatureType causes 100% CPU-bound in deegree3 webapp

What steps will reproduce the problem?
1. run the webapps/deegree3 webapp (no data in DB needed)
2. go to OGC client console in browser
3. select "General" | "DescribeFeatureType"

What is the expected output? What do you see instead?
XML output from DescribeFeatureType. Instead the process hangs with CPU to 
100%. This was reproducable on both Linux+Mac, with and without data in PostGIS 
(inspire_blob db). 

Please use labels and text to provide additional information.
This did not happen before, but today (28 sep 2010 10:45) when using the latest 
deegree3 snapshots. I am attaching the entire Maven build/run output here. The 
webapp config files used can be found in SVN (webapps/deegree3).

This issue prevents me to put the services in production for ESDIN testing 
since I have to restart the server.

Original issue reported on code.google.com by [email protected] on 28 Sep 2010 at 9:05

Attachments:

• deegree3-output.txt

gml_bounded_by column is NULL when inserting INSPIRE features with geometry

What steps will reproduce the problem?
1.run webapps/deegree3 webapp and go to OGC client console 
(console/client/client.html)
2. insert INSPIRE features using Transaction INSERT requests 
3. inserts are OK but gml_bounded_by column in gml_objects table is not 
populated
4. GetCapabilities also gives error when there are  features are in the 
gml_objects table


ava.lang.ClassCastException: org.postgresql.util.PGobject cannot be cast to 
org.postgis.PGboxbase
    at org.deegree.feature.persistence.postgis.PostGISFeatureStore.getEnvelope(PostGISFeatureStore.java:325)
    at org.deegree.feature.persistence.postgis.PostGISFeatureStore.getEnvelope(PostGISFeatureStore.java:195)
    at org.deegree.services.wfs.GetCapabilitiesHandler.export110(GetCapabilitiesHandler.java:577)
    at org.deegree.services.wfs.GetCapabilitiesHandler.export(GetCapabilitiesHandler.java:174)
    at org.deegree.services.wfs.WFSController.doGetCapabilities(WFSController.java:690)
    at org.deegree.services.wfs.WFSController.doXML(WFSController.java:439)
    at org.deegree.services.controller.OGCFrontController.dispatchXMLRequest(OGCFrontController.java:700)
    at org.deegree.services.controller.OGCFrontController.doPost(OGCFrontController.java:475)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)


What is the expected output? What do you see instead?
I expect gml_bounded_by to have geometries and GetCapabilites with possibly 
bboxes


Please use labels and text to provide additional information.
It could be that the INSERT XML is not properly populated :

- does it require gml:boundedBy elements ?
- is the fact that the feature GML is in GML 3.2.1 but the NS is 3.1.1 an issue 
?

Original issue reported on code.google.com by [email protected] on 14 Sep 2010 at 10:19