Opened 14 years ago
Closed 14 years ago
#3304 closed defect (fixed)
gmlsf:intRangeProperty should be an integer value between 0 and 99 in a response to a getfeature
Reported by: | nsavard | Owned by: | mapserverbugs |
---|---|---|---|
Priority: | normal | Milestone: | 6.0 release |
Component: | WFS Server | Version: | svn-trunk (development) |
Severity: | normal | Keywords: | wfs1.1 getfeature response Null intRangeProperty |
Cc: | assefa |
Description
We return Null for gmlsf:intRangeProperty in a response to a getfeature but the value should be 0.
The schema relevant snippet:
<xsd:minInclusive value="0"/> <xsd:maxInclusive value="99"/>
Change History (5)
comment:1 by , 14 years ago
comment:3 by , 14 years ago
Norm,
Looking at the cite-gmlsf0.xsd, It defines the intRangeProperty as being optional:
xsd:element name="intRangeProperty" type="sf:IntRangePropertyType" minOccurs="0"/>
I modified the map file to only have the mandatory elements optput for now:
"gml_include_items" "doubleProperty,strProperty,featureCode"
With this change, the test passed.
There is a bug on a related issue (how to define mandatory and optional attributes #3319) to address this fully.
I am in favor of closing this bug at this point.
Ref: CITE test GetGeature-Get: Test wfs:wfs-1.1.0-Basic-GetFeature-tc26.1
The input data from CITE has null for the intRangeProperty and that is what we have in the postgis db. I am not sure how we should pass this test, unless we read the schema and ouput things according to it. This is not obvious to me at this point.