More info about the proxy behaviour: WFS plugin does use proxy for http GET
requests like GetCapabilities but not for http POST requests which are used for
the final WFS GetFeature. This is probably something that should be fixed in
core OpenJUMP and not in WFS plugin. I know that such fix is do
Hi,
I could really read some data from http://demo.opengeo.org/geoserver/wfs.
There is something wrong with building spatial filters. I could not make a
single one to work, perhaps not even built with the WFS plugin. At least some
attribute filters do work but then the WFS plugin had problems
On 22.12.2014 00:11, Rahkonen Jukka (Tike) wrote:
> I would like to test this new WFS reader (which I would pack to OJ PLUS) and
> I have some servers to test with.
actually there is nothing new under the sun.. it's just the old version 1.1
revived.
try OJ PLUS snapshot r4216.. button is still
Some quick comments, may be inaccurate:
deegree2 is not really maintained. Deegree3 is much more complicated because it
aims to support all INSPIRE specialities and applications schemas (and WFS
v.2.0.0 and 2.0.2) which go beyound the simple feature model. It may be that
doing the simple things
