Opened 20 years ago
Closed 19 years ago
#954 closed defect (fixed)
add contact information
Reported by: | tomkralidis | Owned by: | sdlime |
---|---|---|---|
Priority: | high | Milestone: | 4.4 release |
Component: | WCS Server | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
In WCS Capabilities, between service level <keywords> and <fees>. Here is the structure: <responsibleParty> <individualName>[ows_contactinfo_name]</individualName> <organisationName>[ows_contactinfo_org]</organisationName> <positionName>[ows_contactinfo_pos]</positionName> <contactInfo> <phone> <voice>[ows_contactinfo_tel]</voice> <facsimile>[ows_contactinfo_fax]</facsimile> </phone> <address> <deliveryPoint>[ows_contactinfo_address]</deliveryPoint> <city>[ows_contactinfo_city]</city> <administrativeArea>[ows_contactinfo_stateprov]</administrativeArea> <postalCode>[ows_contactinfo_postcode]</postalCode> <country>[ows_contactinfo_country]</country> <electronicMailAddress>[ows_contactinfo_email]</electronicMailAddress> </address> <onlineResource xlink:type="simple" xlink:href="[ows_contactinfo_url]"/> </contactInfo> </responsibleParty>
Change History (9)
comment:2 by , 20 years ago
Guys, Any way we can slip this one into 4.4.0? Seeing that this will be the first official release with OGC:WCS.
comment:3 by , 20 years ago
Status: | new → assigned |
---|
Yes, there were a couple of outstanding WCS ones that will make it. Ain't hard just takes time... Steve
comment:4 by , 19 years ago
Milestone: | → 4.4 release |
---|
Setting to 4.4 release after Steve's confirmation in comment #3
comment:5 by , 19 years ago
Fixing now. I'm trying to support both a WCS specific method (i.e. wcs_responsibleparty_name) and the WMS method (i.e. wms_contactperson). Note that I don't see support for *_contactinfo_* metadata anyplace. Steve
comment:6 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed although only lightly tested. Both the wcs_responsibleparty_* metadata and the WMS contact metadata are supported (although you can't mix and match). If both are present the WCS specific encoding takes precedence. Note that WMS did not have the equivalent of onlineResource so wcs_responsibleparty_onlineresource is supported regardless. Also note that WCS getCapabilities.xsd schema spells "organization" as "organisation". MapServer expects wcs_responsibleparty_organizationname as metadata but produces XML that validates against that schema. J.F. if you have time and could verify... Steve
comment:7 by , 19 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comments: 1./ typo in: <organisationName>Environment Canada</oranisationName> Closing element should be "organisationName" to match opening element (line 374). 2./ typo when mapows.c looks up facsimile in both WCS and WMS metadata (lines 394 and 422) (should be facsimile, not facimile) 3./ for onlineResource, use the new "ows_service_onlineresource" (line 451) when a WCS equivalent is not found. This should do it -- let me know when I can retest.
Note:
See TracTickets
for help on using tickets.