Hi all,
at a deeper inspection on geoserver master (2.3-SNAPSHOT) it looks like the
stuff works as espected.
In that case the WMS GetCapabilities 1.1.1 does not contain the element
VendorSpecificCapabilities unless we enable GWC direct integration and
specify tiled=true on the request.
Moreover
See http://hudson.opengeo.org/hudson/job/geoserver-master/5385/changes
Changes:
[Andrea Aime] [GEOS-2801] WCS Reprojection using an XML GetCoverage request
seems to be somewhat broken (WCS 1.1.1)
--
[...truncated 44081 lines...]
22 Aug 11:50:42 INFO
Hi all,
as you should know the PSC is looking for user representatives
in the PSC, we have already two good candidates but I'd like to add yet
another
one, Rahkonen Jukka.
Jukka is a long time GeoServer user, and one of the most active on the
users mailing list, providing hints and solutions
to
See http://hudson.opengeo.org/hudson/job/geoserver-2.2.x/53/changes
Changes:
[Andrea Aime] [GEOS-2801] WCS Reprojection using an XML GetCoverage request
seems to be somewhat broken (WCS 1.1.1)
--
[...truncated 39425 lines...]
Aug 22, 2012 12:08:47 PM
On Wed, Aug 22, 2012 at 2:09 PM, Hudson moni...@openplans.org wrote:
See http://hudson.opengeo.org/hudson/job/geoserver-2.2.x/53/changes
Changes:
[Andrea Aime] [GEOS-2801] WCS Reprojection using an XML GetCoverage
request seems to be somewhat broken (WCS 1.1.1)
My bad, fixing it
Cheers
Dragan
Hi all,
as you probably know our current GML2 output (GetFeature and GetFeatureInfo)
omits fully the elements whose value is null.
This causes issues in some dumb clients, such as javascript ones, as they
may
show up a reduced set of attributes hiding the fact there are more.
Now, one could run a
+1. Jukka has been a very active member of the community for quite some
time and I would very much welcome him on the PSC.
On Wed, Aug 22, 2012 at 5:01 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
Hi all,
as you should know the PSC is looking for user representatives
in the PSC, we have
Well this discussion came up actually before during the development of the
wfs 1.1 spec and there were three options.
1. omit the element
2. create an empty element
3. use the xs:nil construct
In the end (1) was decided upon. (2) I believe creates invalid xml
documents and (3) I can't remember.
+1
Regards,
Simone Giannecchini
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
+1
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 331 6233686
On Wed, Aug 22, 2012 at 5:18 PM, Justin Deoliveira jdeol...@opengeo.orgwrote:
Well this discussion came up actually before during the development of the
wfs 1.1 spec and there were three options.
1. omit the element
2. create an empty element
3. use the xs:nil construct
In the end (1) was
On Wed, Aug 22, 2012 at 6:07 PM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
That's odd? I've just tried to replace elements in a GeoServer WFS
response with empty ones, as follows:
wfs:FeatureCollection xmlns=http://www.opengis.net/wfs;
xmlns:wfs=http://www.opengis.net/wfs; xmlns:gml=
I think it depends on the type, indeed some types will allow for empty
content (like strings) but others i believe do not. Or maybe i am just
wrong about that
On Wed, Aug 22, 2012 at 9:07 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Wed, Aug 22, 2012 at 5:18 PM, Justin Deoliveira
On Wed, Aug 22, 2012 at 6:09 PM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
Bah, it just took forever to validate, but indeed the result is invalid,
have to look into why
This variant seems to work fine though:
wfs:FeatureCollection xmlns=http://www.opengis.net/wfs;
See http://hudson.opengeo.org/hudson/job/geoserver-master/5386/
--
[...truncated 89782 lines...]
- GEOSERVER_DATA_DIR:
http://hudson.opengeo.org/hudson/job/geoserver-master/ws/src/extension/wps/wps-core/./target/mock2833863917248619049data
+1 - would love to see Jukka on the PSC, he's definitely been one of the
most helpful users on the list for many years.
/me hopes he accepts.
On Wed, Aug 22, 2012 at 11:43 AM, Alessio Fabiani
alessio.fabi...@geo-solutions.it wrote:
+1
==
Our support, Your Success! Visit
To reiterate a bit - in GeoServer we aren't trying to replace GeoNetwork,
to be a full catalog 'solution'. We just want to expose GeoServer holdings
as CSW. So one would use something like GeoNetwork in a full SDI that
requires full metadata and complex editing of that and aggregating many
David
I have created a ticket at: http://jira.codehaus.org/browse/GEOS-5280
The branch I made is based on master but I think that we could backport it
to 2.1.x pretty easily.
--
David Winslow
OpenGeo - http://opengeo.org/
On Fri, Aug 17, 2012 at 5:17 PM, David Winslow dwins...@opengeo.org wrote:
I
Hi all,
To compliment the recent geotools process reorg (see geotools-devel) i have
created a corresponding pull request for geoserver:
https://github.com/geoserver/geoserver/pull/18
Included is a single DeprecatedProcessFactory that handles the old
process names in order to maintain backward
On 23/08/2012 6:31 a.m., Chris Holmes wrote:
But CSW in GeoServer should make it easier for GeoNetwork to harvest
information from GeoServers, and to just follow a philosophy of
keeping the metadata close to the data.
Yes, this is precisely my interest. There is this complicated problem
See http://hudson.opengeo.org/hudson/job/geoserver-master/5387/
--
[...truncated 44077 lines...]
23 Aug 00:35:32 INFO [tester.BaseWicketTester] - path
category:2:category.links:0 org.apache.wicket.markup.html.list.ListItem
23 matches
Mail list logo
