Ying,

I missed that one. It should be gsml:principalValue not gsml:value

<targetAttribute>gsml:positionalAccuracy/gsml:CGI_NumericValue/gsml:principalValue</targetAttribute>

gsml:CGI_NumericValue has no property gsml:value

If you look in the exception, the permitted properties are listed.

Kind regards,
Ben.



On 14/10/10 17:57, ssss wrote:
> Hi Ben,
> 
> Thanks for your message and sorry for the spelling mistakes. I change to
> 
> 
>                  <AttributeMapping>
>                      
> <targetAttribute>gsml:positionalAccuracy</targetAttribute>
>                      
> <targetAttributeNode>gsml:CGI_NumericValuePropertyType</targetAttributeNode>
>                  </AttributeMapping>
>                  <AttributeMapping>
>                      
> <targetAttribute>gsml:positionalAccuracy/gsml:CGI_NumericValue/gsml:value</targetAttribute>
>                      <sourceExpression>
>                          <OCQL>MF_POSACCU</OCQL>
>                      </sourceExpression>
>                      <ClientProperty>
>                          <name>uom</name>
>                          <value>'urn:ogc:def:uom:UCUM:m'</value>
>                      </ClientProperty>
>                  </AttributeMapping>
> 
> 
> However, I get the error message as
> 
> <ows:ExceptionReport version="1.0.0" 
> xsi:schemaLocation="http://www.opengis.net/ows 
> http://127.0.0.1:8080/geoserver/schemas/ows/1.0.0/owsExceptionReport.xsd";>
> <ows:Exception exceptionCode="NoApplicableCode">
> <ows:ExceptionText>
> java.lang.IllegalArgumentException: gsml:value is not a valid location path 
> for type urn:cgi:xmlns:CGI:GeoSciML:2.0:CGI_NumericValueType. gsml:value ns: 
> urn:cgi:xmlns:CGI:GeoSciML:2.0, CGI_NumericValueType properties: 
> urn:cgi:xmlns:CGI:GeoSciML:2.0#qualifier, 
> urn:cgi:xmlns:CGI:GeoSciML:2.0#minusDelta, 
> urn:cgi:xmlns:CGI:GeoSciML:2.0#plusDelta, 
> urn:cgi:xmlns:CGI:GeoSciML:2.0#principalValue
> gsml:value is not a valid location path for type 
> urn:cgi:xmlns:CGI:GeoSciML:2.0:CGI_NumericValueType. gsml:value ns: 
> urn:cgi:xmlns:CGI:GeoSciML:2.0, CGI_NumericValueType properties: 
> urn:cgi:xmlns:CGI:GeoSciML:2.0#qualifier, 
> urn:cgi:xmlns:CGI:GeoSciML:2.0#minusDelta, 
> urn:cgi:xmlns:CGI:GeoSciML:2.0#plusDelta, 
> urn:cgi:xmlns:CGI:GeoSciML:2.0#principalValue
> </ows:ExceptionText>
> </ows:Exception>
> </ows:ExceptionReport>
> 
> 
> Sorry, I can not understand what this means. It seems the problem of 
> gsml:value.
> 
> Thanks,
> 
> Ying
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> Date: Thu, 14 Oct 2010 09:53:33 +0800
>> From: [email protected]
>> To: [email protected]
>> CC: [email protected]
>> Subject: Re: [Geoserver-users] about gsml:positionalAccuracy in GeoSciML
>>
>> Ying,
>>
>> gsml:CGI_NumericValuePropertyType is a perfectly legal type for
>> gsml:positionalAccuracy. However, you have misspelled it as
>> "gsml:CGI_NumbericValuePropertyType" (you have an extra "b" in the type
>> name). Change:
>> gsml:CGI_NumbericValuePropertyType
>> to:
>> gsml:CGI_NumericValuePropertyType
>>
>> Your targetAttribute xpath is also misspelled (with an extra "b"):
>> gsml:positionalAccuracy/gsml:CGI_NumbericValue/gsml:value
>> should be:
>> gsml:positionalAccuracy/gsml:CGI_NumericValue/gsml:value
>>
>> Kind regards,
>> Ben.
>>
>> On 13/10/10 22:47, ssss wrote:
>>> Hi,
>>>
>>> A simple question concerning GeoSciM:
>>>
>>> When I deal with the gsml:positionalAccuracy in GeoSciML, I think it is 
>>> more reasonable to use gsml:CGI_NumbericValue. However, when I check the 
>>> user manual from
>>>
>>> http://docs.geoserver.org/trunk/en/user/data/app-schema/mapping-file.html
>>>
>>> The example is like
>>>
>>>
>>> <AttributeMapping>
>>> <targetAttribute>gsml:positionalAccuracy</targetAttribute>
>>> <targetAttributeNode>gsml:CGI_TermValuePropertyType</targetAttributeNode>
>>> </AttributeMapping>
>>>
>>> where gsml:CGI_TermValue is considered.
>>>
>>> So if define
>>>
>>> <AttributeMapping>
>>> <targetAttribute>gsml:positionalAccuracy</targetAttribute>
>>> <targetAttributeNode>gsml:CGI_NumbericValuePropertyType</targetAttributeNode>
>>> </AttributeMapping>
>>> <AttributeMapping>
>>> <targetAttribute>gsml:positionalAccuracy/gsml:CGI_NumbericValue/gsml:value</targetAttribute>
>>> <sourceExpression>
>>> <OCQL>MF_POSACCU</OCQL>
>>> </sourceExpression>
>>> <ClientProperty>
>>> <name>uom</name>
>>> <value>'urn:ogc:def:uom:UCUM:m'</value>
>>> </ClientProperty>
>>> </AttributeMapping>
>>>
>>> I get error message.
>>>
>>> My question is which one, gsml:CGI_NumbericValue or gsml:CGI_TermValue is 
>>> right in gsml:positionalAccuracy?
>>>
>>> Thanks,
>>>
>>> Ying
>>
>>
>> --
>> Ben Caradoc-Davies<[email protected]>
>> Software Engineering Team Leader
>> CSIRO Earth Science and Resource Engineering
>> Australian Resources Research Centre


-- 
Ben Caradoc-Davies <[email protected]>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to