WFS Metadata versus connection string (envdat WFS)

Yewondwossen Assefa assefa at DMSOLUTIONS.CA
Mon Nov 22 13:16:23 PST 2004


Tom,

  You still can acheive what you want if you set on your layer
"wfs_request_method" "GET" forcing mapserver to send a get request. I
tried it your data and It seems to work. There was a small problem tough
were the connection element in your demo map file for your layer was
missing a trailing "?". There was no check done on this (Bug 1082 has
been enered for this).

Later,

Kralidis,Tom [Burlington] wrote:

> Assefa,
>
> This might the case.  The server is running 4.2.0, client 4.4.0-beta2.
> I won't be pushing our people to update until 4.4.0 proper on the server
> side.
>
> ..Tom
>
>
>
>>-----Original Message-----
>>From: Yewondwossen Assefa [mailto:assefa at dmsolutions.ca]
>>Sent: Monday, 22 November, 2004 15:38
>>To: Kralidis,Tom [Burlington]
>>Cc: MAPSERVER-USERS at LISTS.UMN.EDU
>>Subject: Re: [UMN_MAPSERVER-USERS] WFS Metadata versus
>>connection string (envdat WFS)
>>
>>
>>Tom,
>>
>>  Ist it possible that the wfs *server* is running an older
>>version of
>>Mapserver (when the xml post requests were not yet supported)
>>and that
>>the client is runnign using a more recent version ?
>>
>>Later,
>>
>>Kralidis,Tom [Burlington] wrote:
>>
>>
>>>>Tyler Mitchell wrote:
>>>>
>>>>
>>>>>I'm working with this WFS data:
>>>>>
>>>>
>>>>http://map.ns.ec.gc.ca/envdat/map.aspx?service=WFS&version=1
>>
>>.0.0&reque
>>
>>>>>st=GetCapabilities
>>>>>
>>>>>It works, but I'm a bit confused when using the data in my
>>>>
>>>>map file.
>>>>
>>>>
>>>>>If I put the parameters manually into the connection string/URL, it
>>>>>works.  But if I put parameters like wfs_version,
>>>>
>>>>wfs_request into the
>>>>
>>>>
>>>>>metadata section for the layer (and remove them from the URL) it
>>>>>doesn't seem to work anymore.
>>>>>
>>>>
>>>>Are you using 4.2 or 4.4?
>>>>
>>>>If you are using 4.4, then wfs_* metadata should be supported
>>>>(and the old method of passing everything in the CONNECTION
>>>>string deprecated), but unfortunately the WFS Client HOWTO
>>>>still hasn't been updated to reflect that. You may find some
>>>>useful hints in bug 417:
>>>>http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=417
>>>
>>>
>>>Actually, I just tested this again with 4.4.0-beta2, and
>>
>>get the same
>>
>>>issues Tyler has (parameters embedded in CONNECTION work,
>>
>>parameters
>>
>>>as
>>>METADATA/wfs_* with no parameters in CONNECTION does not).
>>>
>>>When I try this, .gml files are written to my temp directory.  Upon
>>>checking these w.r.t. this issue, they all come back as OGC service
>>>exceptions, like:
>>>
>>>"VERSION keyword missing"
>>>
>>>..and so on.
>>>
>>>..Tom
>>>
>>>
>>
>>
>>--
>>----------------------------------------------------------------
>>Assefa Yewondwossen
>>Software Analyst
>>
>>Email: assefa at dmsolutions.ca
>>http://www.dmsolutions.ca/
>>
>>Phone: (613) 565-5056 (ext 14)
>>Fax:   (613) 565-0925
>>----------------------------------------------------------------
>>
>>
>>
>
>
>


--
----------------------------------------------------------------
Assefa Yewondwossen
Software Analyst

Email: assefa at dmsolutions.ca
http://www.dmsolutions.ca/

Phone: (613) 565-5056 (ext 14)
Fax:   (613) 565-0925
----------------------------------------------------------------



More information about the MapServer-users mailing list