On Thu, Dec 8, 2016 at 7:52 PM, Martin Davis wrote:
> It looks like GeoServer is deleting parameter elements with "default"
> values (although I'm not aware that there is any such thing as default
> values for SLD entries).
>
See the "raw" parameter description in the REST API reference here:
h
On 7-11-2016 9:28, jvandewege wrote:
>
>
> Improvement GEOS-7838REST call to about/version doesn't work on
> Wildfly/Jboss : https://osgeo-org.atlassian.net/browse/GEOS-7838
>
As per subject this is issued is solved and backported to geoserver-2.9.3.
Thanks to all who made this possible,
Joop
--
Kevin,
I think this is a feature chaining problem. The first thing I noticed is
that in discretecoverage.xml you have
discretecoverage_domain but I think this
should match the targetElement of the nested type (wxxm:DomainObject). I
also saw inputAttribute which might work but I think is meant
Thanks Ben,
I'll have to check out HALE. Automatic mapping files sounds nice!
Unfortunately, I haven't had a chance to step through the debugger yet as I've
been away from the office and don't have direct access to my dev system. That
is my next step though.
I've attached both my mapping fil
On 09/12/16 10:24, kweis...@harris.com wrote:
> I figured the debugger was the way to go, but hoped there was an easier way.
> :P
Kevin, I feel your pain. The debugger is an end-user-interface antipattern.
One interesting user interface option is HALE, which I have heard of but
not used. HALE h
I figured the debugger was the way to go, but hoped there was an easier way. :P
I'll take a look at the recommended breakpoints and see if I can figure out
what's happening. The element I'm trying to encode is a wxxm:DiscreteCoverage
which should have a wxxm:domainSet element with 0-N wxxm:Doma
I noticed some odd behaviour in GS 2.9.1. I load a style via the REST API
which has the following in a PolygonSymbolizer:
#00
1
1.0
When I view the style in the Style Editor panel the following is displayed:
This is also what is stored in the data di
Yes, the debugger is my tool of choice as well. Another important
breakpoint is gt-app-schema
DataAccessMappingFeatureIterator.computeNext, where you can see features
being built and check their content:
https://github.com/geotools/geotools/blob/master/modules/extension/app-schema/app-schema/src
Hello,
I have the same issue and unfortunately I didn't find any nice way to
troubleshot this kind of problems too.
So if someone knows a better way to do this kind of trouble shooting I
would love to hear it too.
So far I rely on debugging to understand what I "did wrong" with my
mappings.
I
Hello again everyone,
I'm working on creating some app-schema mapping files for some complex schemas
and have been having a few issues. Specifically, I've got some elements that
for some reason refuse to populate. I don't get any errors during boot up nor
when a request is processed, the eleme
Hi Andrea,
As usual thanks for sharing your expertise in this matter. We were really
confused here about what we were dealing with so thanks again.
With the information and link provided we will allocate and solve the
problem.
You are right, REST API is a great tool for automation but very prone
On Wed, Dec 7, 2016 at 11:10 AM, Alberto CD <
alberto.calle...@deimos-space.com> wrote:
> Another question is: Why is just failing WFS getCapabilities request?? WMS
> and WCS are working fine (even though we have this warnigns in the log for
> those too...)
>
Going by memory, because in WFS the w
On Wed, Dec 7, 2016 at 5:12 PM,
wrote:
> Hi Nils,
>
>
>
> Thank you for your quick reply. Your commands helped a lot and the import
> finally works!
>
> Is there any chance that something like this finds its way to the
> documentation?
>
The chance is proportional to how much you're willing to p
13 matches
Mail list logo
