INSPIRE download services, WFS and spatial dataset identifier

[geowolf]

Hi all,

I'm trying to get the INSPIRE module in shape before I propose its graduation to official extension (many people use it, it's a shame to have it as an unsupported module).

The recent WFS additions did not have tests, and that made it impossible to graduate the module (not enough test coverage) so I added some tests.

Looking into it I tried to make a simple schema validation of the output, and to my surprise, it failed due to a mandatory element being absent (!!)

The element is the spatial dataset identifier, which is actually a list of code/namespace pairs:

<inspire_dls:SpatialDataSetIdentifier>

<inspire_common:Code>mycode</inspire_common:Code>

<inspire_common:Namespace>http://myuri.org</inspire_common:Namespace>

</inspire_dls:SpatialDataSetIdentifier>

<inspire_dls:SpatialDataSetIdentifier>

<inspire_common:Code>mycode2</inspire_common:Code>

<inspire_common:Namespace>http://myuri.org</inspire_common:Namespace>

</inspire_dls:SpatialDataSetIdentifier>

The docs I've found around are not telling me much about what this is though.

What I'm wondering most is, is it something that should be configured at a global level (WFS admin panel), or is it more something that it makes sense to configure on a layer by layer basis (layer config panel)?

All I could find in the download services spec is:

The Spatial Data Set Identifier parameter is defined in the Network Service regulation [INS NS] as “The Spatial Data Set Identifier parameter shall contain the Unique Resource Identifier of the Data Set”

The following table demonstrates how the Spatial Data Set Identifier is mapped between the Atom and WFS based Technical Guidance and the corresponding ISO metadata of the spatial data set. The Spatial Data Set Identifier parameter maps to either the RS_Identifier or the MD_Identifier depending on what type of Spatial Data Set Identifier is used in the corresponding ISO metadata.

However the above leaves me none the wiser....

Anybody knows more?

Cheers

Andrea

--

==

GeoServer training in Milan, 6th & 7th June 2013!  Visit http://geoserver.geo-solutions.it for more information.
==

Ing. Andrea Aime 

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054  Massarosa (LU)

Italy

phone: [phone]

fax: [phone]

mob: [phone]

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

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

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[nmtoken]

> What I'm wondering most is, is it something that should be configured at a
global level (WFS admin panel), or is it more something that it makes sense
to configure on a layer by layer basis (layer config panel)?

As this is really metadata about the service, I would expect that that you would configure it at the global layer and not on a layer by layer basis.  The identifiers in the SpatialDataSetIdentifier section relate to dataset metadata identifiers (for each dataset operated on by the service).

> The Spatial Data Set Identifier parameter maps to either the RS_Identifier or the MD_Identifier
depending on what type of Spatial Data Set Identifier is used in the corresponding ISO metadata.

An RS_Identifier section of a dataset metadata record might look like:

<gmd:identifier>
  <gmd:RS_Identifier>
    <gmd:code>
      <gco:CharacterString>13480203</gco:CharacterString>
    </gmd:code>
    <gmd:codeSpace>
      <gco:CharacterString>http://data.bgs.ac.uk/id/dataHolding</gco:CharacterString>
    </gmd:codeSpace>
  </gmd:RS_Identifier>
</gmd:identifier>

So I assume that would correspond to something like:

<inspire_dls:SpatialDataSetIdentifier>
  <inspire_common:Code>13480203</inspire_common:Code>
  <inspire_common:Namespace>http://data.bgs.ac.uk/id/dataHolding</inspire_common:Namespace>
</inspire_dls:SpatialDataSetIdentifier>


An MD_Identifier section of a dataset metadata record might look like:

<gmd:identifier>
  <gmd:MD_Identifier>
    <gmd:code>
      <gco:CharacterString>9df8df51-6342-37a8-e044-0003ba9b0d98</gco:CharacterString>
    </gmd:code>
  </gmd:MD_Identifier>
</gmd:identifier>

So I assume that would correspond to something like:

<inspire_dls:SpatialDataSetIdentifier>
  <inspire_common:Code>9df8df51-6342-37a8-e044-0003ba9b0d98</inspire_common:Code>
  <inspire_common:Namespace></inspire_common:Namespace>
</inspire_dls:SpatialDataSetIdentifier>


Hope this helps

                           ,,,
James                     (o o)
======================oOO==(_)==OOo===
James Passmore
GIS and WWW Specialist
Geoscience Products and Services,
British Geological Survey,
http://www.bgs.ac.uk/

[phone]
@nmtoken



This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[geowolf]

On Mon, Apr 22, 2013 at 1:55 PM, Passmore, James H. <[hidden email]> wrote:

Hope this helps

It surely does, thank you :-)

Cheers

Andrea

--

==

GeoServer training in Milan, 6th & 7th June 2013!  Visit http://geoserver.geo-solutions.it for more information.
==

Ing. Andrea Aime 

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054  Massarosa (LU)

Italy

phone: [phone]

fax: [phone]

mob: [phone]

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

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

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[theodoros.vakkas]

The spatial dataset identifier is a mandatory element (Unique Resource Identifier) required in the INSPIRE/ISO metadata file created for the dataset. 

So, when creating the metadata file for each dataset a Unique Resource Identifier is provided in the form of either RS_Identifier or MD_Identifier. If a value for a codeSpace is provided, then the data type for the identifier should be RS_Identifer, which is substitutable for the usual MD_Identifier

(source: http://inspire.jrc.ec.europa.eu/documents/Metadata/INSPIRE_MD_IR_and_ISO_v1_2_20100616.pdf, page 18)

In RS_identifier form which is preferable(?): 

<gmd:RS_Identifier>

<gmd:code>

<gco:CharacterString>daf473d4-275d-48b4-a40b-5101684ff7f7</gco:CharacterString>

</gmd:code>

<gmd:codeSpace>

<gco:CharacterString>http://www.rae.gr</gco:CharacterString>

</gmd:codeSpace>

</gmd:RS_Identifier>

or 

<gmd:identifier>

<gmd:RS_Identifier>

<gmd:code>

<gco:CharacterString>http://www.rae.gr#daf473d4-275d-48b4-a40b-5101684ff7f7</gco:CharacterString>

</gmd:code>

</gmd:RS_Identifier>

</gmd:identifier>

<gmd:identifier>

The gmd:code should then map to inspire_common:Code and the the gmd:codeSpace maps to  inspire_common:Namespace

At the end, the Download Service metadata should include a list in of the datasets against it operates on. Not sure, but maybe it should be configured at the service level, allowing adjustments similar to WMS (authority, add layer identifiers)

Here is the dls_schema http://inspire.ec.europa.eu/schemas/inspire_dls/

Hope it helps

 

On Mon, Apr 22, 2013 at 6:55 AM, <[hidden email]> wrote:

Send Geoserver-devel mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/geoserver-devel
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Geoserver-devel digest..."


Today's Topics:

   1. INSPIRE download services,        WFS and spatial dataset identifier
      (Andrea Aime)
   2. [Hudson] Build failed in Hudson:  geoserver-2.3.x-nightly #84
      (Hudson)


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

Message: 1
Date: Sun, 21 Apr 2013 17:17:17 +0200
From: Andrea Aime <[hidden email]>
Subject: [Geoserver-devel] INSPIRE download services,   WFS and spatial
        dataset identifier
To: Geoserver-devel <[hidden email]>,    Jesse
        Eichar <[hidden email]>
Message-ID:
        <CA+nxMTvBCiUyMtS35nDUT=[hidden email]>
Content-Type: text/plain; charset="windows-1252"

Hi all,
I'm trying to get the INSPIRE module in shape before I propose its
graduation to official extension (many people use it, it's a shame to have
it as an unsupported module).

The recent WFS additions did not have tests, and that made it impossible to
graduate the module (not enough test coverage) so I added some tests.

Looking into it I tried to make a simple schema validation of the output,
and to my surprise, it failed due to a mandatory element being absent (!!)

The element is the spatial dataset identifier, which is actually a list of
code/namespace pairs:

<inspire_dls:SpatialDataSetIdentifier>
<inspire_common:Code>mycode</inspire_common:Code>
<inspire_common:Namespace>http://myuri.org</inspire_common:Namespace>
</inspire_dls:SpatialDataSetIdentifier>
<inspire_dls:SpatialDataSetIdentifier>
<inspire_common:Code>mycode2</inspire_common:Code>
<inspire_common:Namespace>http://myuri.org</inspire_common:Namespace>
</inspire_dls:SpatialDataSetIdentifier>

The docs I've found around are not telling me much about what this is
though.
What I'm wondering most is, is it something that should be configured at a
global level (WFS admin panel), or is it more something that it makes sense
to configure on a layer by layer basis (layer config panel)?

All I could find in the download services spec is:

The Spatial Data Set Identifier parameter is defined in the Network Service
regulation [INS NS] as ?The Spatial Data Set Identifier parameter shall
contain the Unique Resource Identifier of the Data Set?
The following table demonstrates how the Spatial Data Set Identifier is
mapped between the Atom and WFS based Technical Guidance and the
corresponding ISO metadata of the spatial data set. The Spatial Data Set
Identifier parameter maps to either the RS_Identifier or the MD_Identifier
depending on what type of Spatial Data Set Identifier is used in the
corresponding ISO metadata.

However the above leaves me none the wiser....
Anybody knows more?

Cheers
Andrea

--
==
GeoServer training in Milan, 6th & 7th June 2013!  Visit
http://geoserver.geo-solutions.it for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: <a href="tel:%2B39%200584%20962313" value="[phone]">[phone]
fax: <a href="tel:%2B39%200584%201660272" value="[phone]">[phone]
mob: <a href="tel:%2B39%20%20339%208844549" value="[phone]">[phone]

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 2
Date: Mon, 22 Apr 2013 03:54:54 +0000 (UTC)
From: Hudson <[hidden email]>
Subject: [Geoserver-devel] [Hudson] Build failed in Hudson:
        geoserver-2.3.x-nightly #84
To: [hidden email]
Message-ID: <244163008.331366602895078.JavaMail.jetty@gridlock>
Content-Type: text/plain; charset=UTF-8

See <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/84/>

------------------------------------------
[...truncated 8265 lines...]
[INFO] Copying gt-xsd-gml3-9-SNAPSHOT.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/gt-xsd-gml3-9-SNAPSHOT.jar>
[INFO] Copying gt-xsd-ows-9-SNAPSHOT.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/gt-xsd-ows-9-SNAPSHOT.jar>
[INFO] Copying gt-xsd-sld-9-SNAPSHOT.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/gt-xsd-sld-9-SNAPSHOT.jar>
[INFO] Copying gt-xsd-wcs-9-SNAPSHOT.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/gt-xsd-wcs-9-SNAPSHOT.jar>
[INFO] Copying gt-xsd-wfs-9-SNAPSHOT.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/gt-xsd-wfs-9-SNAPSHOT.jar>
[INFO] Copying gt-xsd-wps-9-SNAPSHOT.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/gt-xsd-wps-9-SNAPSHOT.jar>
[INFO] Copying hamcrest-core-1.1.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/hamcrest-core-1.1.jar>
[INFO] Copying ejb3-persistence-1.0.1.GA.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/ejb3-persistence-1.0.1.GA.jar>
[INFO] Copying hibernate-3.2.6.ga.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/hibernate-3.2.6.ga.jar>
[INFO] Copying hibernate-annotations-3.3.1.GA.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/hibernate-annotations-3.3.1.GA.jar>
[INFO] Copying hibernate-commons-annotations-3.0.0.ga.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/hibernate-commons-annotations-3.0.0.ga.jar>
[INFO] Copying hibernate-entitymanager-3.3.2.GA.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/hibernate-entitymanager-3.3.2.GA.jar>
[INFO] Copying jt-attributeop-1.3.0.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jt-attributeop-1.3.0.jar>
[INFO] Copying jt-contour-1.3.0.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jt-contour-1.3.0.jar>
[INFO] Copying jt-rangelookup-1.3.0.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jt-rangelookup-1.3.0.jar>
[INFO] Copying jt-utils-1.3.0.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jt-utils-1.3.0.jar>
[INFO] Copying jt-vectorbinarize-1.3.0.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jt-vectorbinarize-1.3.0.jar>
[INFO] Copying jt-vectorize-1.3.0.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jt-vectorize-1.3.0.jar>
[INFO] Copying jt-zonalstats-1.3.0.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jt-zonalstats-1.3.0.jar>
[INFO] Copying cas-client-core-3.1.12.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/cas-client-core-3.1.12.jar>
[INFO] Copying jasypt-1.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jasypt-1.8.jar>
[INFO] Copying jetty-6.1.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jetty-6.1.8.jar>
[INFO] Copying jetty-util-6.1.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jetty-util-6.1.8.jar>
[INFO] Copying servlet-api-2.5-6.1.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/servlet-api-2.5-6.1.8.jar>
[INFO] Copying geodb-0.7-RC2.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/geodb-0.7-RC2.jar>
[INFO] Copying encoder-1.1.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/encoder-1.1.jar>
[INFO] Copying org.restlet-1.0.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/org.restlet-1.0.8.jar>
[INFO] Copying org.restlet.ext.freemarker-1.0.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/org.restlet.ext.freemarker-1.0.8.jar>
[INFO] Copying org.restlet.ext.spring-1.0.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/org.restlet.ext.spring-1.0.8.jar>
[INFO] Copying slf4j-api-1.5.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/slf4j-api-1.5.8.jar>
[INFO] Copying slf4j-log4j12-1.4.2.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/slf4j-log4j12-1.4.2.jar>
[INFO] Copying slf4j-simple-1.0.1.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/slf4j-simple-1.0.1.jar>
[INFO] Copying spring-aop-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-aop-3.1.1.RELEASE.jar>
[INFO] Copying spring-asm-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-asm-3.1.1.RELEASE.jar>
[INFO] Copying spring-beans-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-beans-3.1.1.RELEASE.jar>
[INFO] Copying spring-context-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-context-3.1.1.RELEASE.jar>
[INFO] Copying spring-context-support-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-context-support-3.1.1.RELEASE.jar>
[INFO] Copying spring-core-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-core-3.1.1.RELEASE.jar>
[INFO] Copying spring-expression-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-expression-3.1.1.RELEASE.jar>
[INFO] Copying spring-jdbc-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-jdbc-3.1.1.RELEASE.jar>
[INFO] Copying spring-orm-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-orm-3.1.1.RELEASE.jar>
[INFO] Copying spring-tx-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-tx-3.1.1.RELEASE.jar>
[INFO] Copying spring-web-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-web-3.1.1.RELEASE.jar>
[INFO] Copying spring-webmvc-3.1.1.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-webmvc-3.1.1.RELEASE.jar>
[INFO] Copying spring-security-cas-3.1.0.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-security-cas-3.1.0.RELEASE.jar>
[INFO] Copying spring-security-config-3.1.0.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-security-config-3.1.0.RELEASE.jar>
[INFO] Copying spring-security-core-3.1.0.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-security-core-3.1.0.RELEASE.jar>
[INFO] Copying spring-security-crypto-3.1.0.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-security-crypto-3.1.0.RELEASE.jar>
[INFO] Copying spring-security-web-3.1.0.RELEASE.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/spring-security-web-3.1.0.RELEASE.jar>
[INFO] Copying htmlvalidator-1.2.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/htmlvalidator-1.2.jar>
[INFO] Copying oro-2.0.8.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/oro-2.0.8.jar>
[INFO] Copying picocontainer-1.2.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/picocontainer-1.2.jar>
[INFO] Copying postgresql-8.4-701.jdbc3.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/postgresql-8.4-701.jdbc3.jar>
[INFO] Copying stax-api-1.0.1.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/stax-api-1.0.1.jar>
[INFO] Copying jasper-compiler-5.5.15.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jasper-compiler-5.5.15.jar>
[INFO] Copying jasper-compiler-jdt-5.5.15.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jasper-compiler-jdt-5.5.15.jar>
[INFO] Copying jasper-runtime-5.5.15.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/jasper-runtime-5.5.15.jar>
[INFO] Copying serializer-2.7.1.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/serializer-2.7.1.jar>
[INFO] Copying xercesImpl-2.7.1.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/xercesImpl-2.7.1.jar>
[INFO] Copying xmlParserAPIs-2.6.2.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/xmlParserAPIs-2.6.2.jar>
[INFO] Copying xml-apis-1.3.04.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/xml-apis-1.3.04.jar>
[INFO] Copying xml-apis-ext-1.3.04.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/xml-apis-ext-1.3.04.jar>
[INFO] Copying xml-apis-xerces-2.7.1.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/xml-apis-xerces-2.7.1.jar>
[INFO] Copying xmlpull-1.1.3.1.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/xmlpull-1.1.3.1.jar>
[INFO] Copying xpp3-1.1.3.4.O.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/xpp3-1.1.3.4.O.jar>
[INFO] Copying xpp3_min-1.1.4c.jar to <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/target/dependency/xpp3_min-1.1.4c.jar>
[INFO] gt-api-9-SNAPSHOT.jar already exists in destination.
[INFO] gwc-core-1.4-SNAPSHOT.jar already exists in destination.
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO] Executed tasks
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] GeoServer ............................................. SUCCESS [17.781s]
[INFO] Core Platform Module .................................. SUCCESS [7.806s]
[INFO] Open Web Service Module ............................... SUCCESS [16.608s]
[INFO] Main Module ........................................... SUCCESS [53.176s]
[INFO] Web Feature Service Module ............................ SUCCESS [19.493s]
[INFO] Web Coverage Service Module ........................... SUCCESS [2.813s]
[INFO] Web Map Service Module ................................ SUCCESS [25.140s]
[INFO] GeoServer Web Modules ................................. SUCCESS [0.180s]
[INFO] Core UI Module ........................................ SUCCESS [18.978s]
[INFO] Security UI Module .................................... SUCCESS [10.059s]
[INFO] GeoServer Security Modules ............................ SUCCESS [0.369s]
[INFO] GeoServer JDBC Security Module ........................ SUCCESS [6.875s]
[INFO] GeoServer LDAP Security Module ........................ SUCCESS [2.606s]
[INFO] Web Coverage Service 1.0 Module ....................... SUCCESS [7.321s]
[INFO] Web Coverage Service 1.1 Module ....................... SUCCESS [5.994s]
[INFO] GeoWebCache (GWC) Module .............................. SUCCESS [17.699s]
[INFO] REST Support Module ................................... SUCCESS [4.424s]
[INFO] REST Configuration Service Module ..................... SUCCESS [7.235s]
[INFO] WMS UI Module ......................................... SUCCESS [5.903s]
[INFO] GWC UI Module ......................................... SUCCESS [6.410s]
[INFO] WFS UI Module ......................................... SUCCESS [3.524s]
[INFO] Demoes Module ......................................... SUCCESS [10.779s]
[INFO] WCS UI Module ......................................... SUCCESS [4.847s]
[INFO] GeoServer Web Application ............................. SUCCESS [28.670s]
[INFO] Community Space ....................................... SUCCESS [0.157s]
[INFO] Authentication by unique url key ...................... SUCCESS [4.352s]
[INFO] GeoServer CSS Styling ................................. SUCCESS [14.681s]
[INFO] WorldWind Format Module ............................... SUCCESS [4.779s]
[INFO] Printing Module ....................................... SUCCESS [11.743s]
[INFO] GeoServer Embedded FTP server ......................... SUCCESS [2.273s]
[INFO] GeoServer Scripting Extensions ........................ SUCCESS [0.364s]
[INFO] Core Scripting Extension .............................. SUCCESS [6.107s]
[INFO] GeoServer Extensions .................................. SUCCESS [0.171s]
[INFO] H2 DataStore Extension ................................ SUCCESS [2.599s]
[INFO] Python Scripting Extension ............................ SUCCESS [11.694s]
[INFO] JavaScript Scripting Extension ........................ SUCCESS [9.044s]
[INFO] Groovy Scripting Extension ............................ SUCCESS [21.149s]
[INFO] GeoServer JDBC KV Catalog ............................. SUCCESS [5.976s]
[INFO] GeoServer INSPIRE Extensions .......................... SUCCESS [4.117s]
[INFO] Simple Feature Service ................................ SUCCESS [9.191s]
[INFO] Aggregating Data Store ................................ SUCCESS [4.854s]
[INFO] Web Coverage Service 2.0 Module ....................... SUCCESS [8.318s]
[INFO] GeoServer libjpeg-turbo Module ........................ SUCCESS [3.954s]
[INFO] GeoServer Community Release Module .................... SUCCESS [28.673s]
[INFO] SpatiaLite Extension .................................. SUCCESS [4.832s]
[INFO] BeanShell Scripting Extension ......................... SUCCESS [3.391s]
[INFO] Ruby Scripting Extension .............................. SUCCESS [3.377s]
[INFO] Application Schema Support ............................ SUCCESS [0.223s]
[INFO] Application Schema Integration Test ................... SUCCESS [11.759s]
[INFO] Sample DataAccess Integration Test .................... SUCCESS [2.256s]
[INFO] ArcSDE DataStore Extension ............................ SUCCESS [12.114s]
[INFO] GeoSearch Index Module ................................ SUCCESS [5.003s]
[INFO] SQL Server DataStore Extension ........................ SUCCESS [0.993s]
[INFO] Oracle DataStore Extension ............................ SUCCESS [0.319s]
[INFO] MySQL DataStore Extension ............................. SUCCESS [0.197s]
[INFO] DB2 DataStore Extension ............................... SUCCESS [0.725s]
[INFO] ImageMap Output Format ................................ SUCCESS [5.607s]
[INFO] ImageI/O-Ext GDAL Coverage Extension .................. SUCCESS [0.424s]
[INFO] JP2K Coverage Extension ............................... SUCCESS [0.441s]
[INFO] ogr2ogr Output Format ................................. SUCCESS [4.367s]
[INFO] Excel Output Format ................................... SUCCESS [4.112s]
[INFO] Validation Module ..................................... SUCCESS [1.773s]
[INFO] Chart external graphics support ....................... SUCCESS [0.261s]
[INFO] Feature Generalization Extension ...................... SUCCESS [2.631s]
[INFO] Image Mosaic JDBC Extension ........................... SUCCESS [0.573s]
[INFO] OWS request flow controller ........................... SUCCESS [5.753s]
[INFO] Web Processing Service parent ......................... SUCCESS [0.319s]
[INFO] Web Processing Service Module ......................... SUCCESS [16.608s]
[INFO] Web Processing Service GUI ............................ SUCCESS [6.096s]
[INFO] GeoServer Layer Querying filter functions ............. SUCCESS [3.484s]
[INFO] Teradata DataStore Extension .......................... SUCCESS [2.044s]
[INFO] GeoServer Monitor Extensions .......................... SUCCESS [0.370s]
[INFO] Core Monitor Extension ................................ SUCCESS [7.854s]
[INFO] Monitor Hibernate Extension ........................... SUCCESS [11.975s]
[INFO] GeoServer CAS Security Module ......................... SUCCESS [5.323s]
[INFO] GeoServer Security Extension Modules .................. SUCCESS [0.381s]
[INFO] XLST based WFS output format .......................... SUCCESS [4.780s]
[INFO] GeoServer Release Module .............................. SUCCESS [16.923s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9 minutes 59 seconds
[INFO] Finished at: Mon Apr 22 03:54:25 UTC 2013
[INFO] Final Memory: 141M/491M
[INFO] ------------------------------------------------------------------------
+ /opt/apache-maven-2.2.1/bin/mvn assembly:attached
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   GeoServer
[INFO]   Core Platform Module
[INFO]   Open Web Service Module
[INFO]   Main Module
[INFO]   Web Feature Service Module
[INFO]   Web Coverage Service Module
[INFO]   Web Map Service Module
[INFO]   GeoServer Web Modules
[INFO]   Core UI Module
[INFO]   Security UI Module
[INFO]   GeoServer Security Modules
[INFO]   GeoServer JDBC Security Module
[INFO]   GeoServer LDAP Security Module
[INFO]   Web Coverage Service 1.0 Module
[INFO]   Web Coverage Service 1.1 Module
[INFO]   GeoWebCache (GWC) Module
[INFO]   REST Support Module
[INFO]   REST Configuration Service Module
[INFO]   WMS UI Module
[INFO]   GWC UI Module
[INFO]   WFS UI Module
[INFO]   Demoes Module
[INFO]   WCS UI Module
[INFO]   GeoServer Web Application
[INFO]   Community Space
[INFO]   GeoServer Extensions
[INFO] ------------------------------------------------------------------------
[INFO] Building GeoServer
[INFO]    task-segment: [assembly:attached] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] snapshot org.geoserver:platform:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:platform:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:ows:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:ows:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:main:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:main:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:wfs:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:wfs:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:wcs:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:wcs:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:wms:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.web:web-core:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.web:web-core:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:wms:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.web:web-security:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.web:web-security:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:rest:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:rest:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:wcs1_0:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:wcs1_0:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:wcs1_1:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:wcs1_1:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver:gwc:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:gwc:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.web:web-demo:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.web:web-demo:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.web:web-wms:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:restconfig:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.security:sec-jdbc:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver:restconfig:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.web:web-wms:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.security:sec-jdbc:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.web:web-gwc:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.web:web-gwc:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.security:sec-ldap:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.web:web-wfs:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.web:web-wfs:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.security:sec-ldap:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] snapshot org.geoserver.web:web-wcs:2.3-SNAPSHOT: checking for updates from opengeo
[INFO] snapshot org.geoserver.web:web-wcs:2.3-SNAPSHOT: checking for updates from osgeo
[INFO] [assembly:attached {execution: default-cli}]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to find descriptor: <http://hudson.opengeo.org/hudson/job/geoserver-2.3.x-nightly/ws/src/release/ext-xslt.xml> (No such file or directory)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18 seconds
[INFO] Finished at: Mon Apr 22 03:54:53 UTC 2013
[INFO] Final Memory: 40M/367M
[INFO] ------------------------------------------------------------------------
+ cp target/release/geoserver*-bin.zip /var/www/html/geoserver/2.3.x/geoserver-2.3.x-2013-04-22-bin.zip
cp: cannot stat `target/release/geoserver*-bin.zip': No such file or directory

--
This message is automatically generated by Hudson.
For more information on Hudson, see: http://hudson-ci.org/



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

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter

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

_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


End of Geoserver-devel Digest, Vol 83, Issue 48
***********************************************

--

Theodoros Vakkas

Head of Geoinformatics Dpt

e-mail: [hidden email]

Mobile: [phone]

 

Geospatial Enabling Technologies

42 Posidonos Av., 17675, Kallithea, Attica, Greece

Tel:  [phone]

Fax:  [phone]

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel