In Section 9.2.4 of the MapServer v6.0 Manual, under OGC Support and
Configuration / WMS Server / WMS 1.3.0 Support / Some Missing features it
lists WMS 1.3.0 Post request should be an XML document containing the
different operations and parameters. (Also appears in the current version
Hi all,
Are HTTP POST requests supported for WMS GetMap requests? I realise that
requests including an SLD are supported... but what about for requests not
using an SLD?
I'm using MapServer v6.0.3. I've tried to code up the layer name, format,
bounds etc as a POSTED request and can't get it to
Thanks Jukka - I'll try your suggestion for OGR connection-type first, since
that's easy for me to test on our existing platform. I have tried the
PropertyIsLike and that definitely works. It'll take me a little bit
longer to spin up a more recent version of the software packages...
Regards,
Hi Jukka - I've tried testing your other suggestion:
OK - I've tried using the OGR CONNECTIONTYPE - it no longer generates an
error message, but comes back with a null result set.
Checking the logs reveals that the error is now apparently being pushed
further back up the stack - eg the Postgres
I can't shine any light on the problem but I have encountered the same
problem. Using MapServer v6.0.3, with Postgres 9.1.3, PostGIS v 1.5.3, GDAL
v1.8.0.WFS Posted Query looks like this:The DescribeFeatureType for that
layer shows the following for the attribute:PostgreSQL has the attribute
Thanks Michael!
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Oracle-Locator-support-tp4519962p4537982.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
___
mapserver-users mailing list
Hi Michael,
Thanks, but I only want to know at this stage whether MapServer is written
for Oracle Spatial only, or whether it can support Locator.
I'm guessing from reading Oracle's documentation that since
SDO.GEOM.INTERSECTS and SDO.GEOM.RELATE aren't supported, that MapServer
probably doesn't
Hi Kathleen,
I've used a CGI Variable to pass a variable in the past, for a similar
problem. It does mean that you then use a non-WMS compliant URL query. I
used it with a FILTER statement, but perhaps it might also work with a
PROCESSING instruction eg.
PROCESSING BANDS=%timeband%
Your URL
Hi,
I'm trying to find out if Oracle Locator can be used as an effective Spatial
Database for MapServer. I haven't been able to find a list of what is and
isn't supported for this combination. We've been using PostgreSQL/PostGIS
as our spatial database and are wondering whether a shift to Oracle
Hi,
I think I've found a quirk in MapServer V5.6.0 WFS behaviour - but I'm not
really sure as I don't understand enough about reading an XSD to know
whether or not this is expected behaviour. This particular issue is not
causing me any grief at the moment as I know the work-around, but perhaps
Hi Jukka,
Yes - your example works on my own MapServer (v5.6.0) although I had to put
the propertynames in parentheses eg.
(of course my test had a different URL!)
I'm actually using the commercial services of another company - and it's
their MapServer that is v5.4.2 (not mine, otherwise I
Hi,
I'm a user of a service provider that uses MapServer V5.4.2. I'm using
their WFS Service. I'm trying to restrict the set of attributes that are
returned by using a POST'ed Query in my request. But it doesn't seem to
work. The service provider is using V5.4.2. I've tried equivalent queries
Hi Jukka,
Thanks for your response. Made some progress, but still got some problems.
I tried using the the two following GET requests to restrict the
property/attribute lists, using the syntax/capitalisation as read from the
OGC WFS 1.1.0 recommendation:
This example follows:
This one follows
Hi,
I have MapServer 5.6.0 running on RHEL5.5 (FGS9.5 MapServer package)
I'm behind a proxy (NTLM), and I want to access a WFS source outside that
requires HTTP Authentication. I'm using a WFS Client setup in my Map file,
and I'm accessing my MapServer using WFS too - eg. a WFS Client... all
Thanks Daniel,
I can't get the actual IP because I'm behind a proxy, on an intranet. But I
know the proxy can correctly resolve the URL, because it works fine when I
send a WMS request into my server (which then successfully sends a WMS
request back out to the external source.) Likewise if I
will require a cleaner job, but this quick patch should
work if you are able to build from source.
Daniel
On 11-08-09 10:29 PM, bte...@gmail.com wrote:
Thanks Daniel,
I can't get the actual IP because I'm behind a proxy, on an intranet.
But I
know the proxy can correctly resolve the URL
16 matches
Mail list logo
