Opened 13 years ago

Last modified 13 years ago

#3426 new bug

WFS attribute table is missing most of the data

Reported by: tybion Owned by: mhugent
Priority: major: does not work as expected Milestone: Version 1.7.0
Component: WMS Version: Trunk
Keywords: wfs attribute table Cc:
Must Fix for Release: No Platform: Windows
Platform Version: Windows XP Awaiting user input: no

Description

To observe problem -

  1. Create WFS layer with URL - http://ogi.state.ok.us/geoserver/wfs
  2. Read layer ogi:doq_centroids (about 5,048 points)
  3. After points have appeared on the screen, open the Attribute Table
  4. Look at row where gid=1 - only gid, tot_q_sqmi and usgs_qd_id have data - all other fields are blank

If I download the WFS as a file, the data for gid=1 is as follows. ie. many of the fields have data.

<gml:featureMember> <ogi:doq_centroids fid="doq_centroids.nfm-374592a4_12d9b67bb06_-e80"> <gml:boundedBy><gml:Box srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"> <gml:coordinates xmlns:gml="http://www.opengis.net/gml" decimal="." cs="," ts=" ">-103.03125032,36.96874905 -103.03125032,36.96874905</gml:coordinates> </gml:Box></gml:boundedBy> <ogi:gid>1</ogi:gid> <ogi:sdsm_id >1</ogi:sdsm_id ><ogi:area >0.016000</ogi:area ><ogi:perimeter >0.500000</ogi:perimeter > <ogi:q_24ks_ >1878</ogi:q_24ks_ ><ogi:q_24ks_id >31191</ogi:q_24ks_id ><ogi:quad_name >Goodson School</ogi:quad_name > <ogi:map_edit >1</ogi:map_edit ><ogi:st_fips1 >35</ogi:st_fips1 ><ogi:st_name1 >New Mexico</ogi:st_name1 > <ogi:st1_sq_mi >58</ogi:st1_sq_mi ><ogi:st_fips2 >8</ogi:st_fips2 ><ogi:st_name2 >Colorado</ogi:st_name2 ><ogi:st2_sq_mi >1</ogi:st2_sq_mi > <ogi:st_fips3 >40</ogi:st_fips3 ><ogi:st_name3 >Oklahoma</ogi:st_name3 ><ogi:st3_sq_mi >1</ogi:st3_sq_mi ><ogi:st_fips4 >0</ogi:st_fips4 > <ogi:st4_sq_mi >0</ogi:st4_sq_mi ><ogi:tot_q_sqmi>120</ogi:tot_q_sqmi><ogi:date_pub >75</ogi:date_pub ><ogi:usgs_qd_id>36103-H11</ogi:usgs_qd_id> <ogi:urlcode >36103/36103h11</ogi:urlcode ><ogi:file_loc >36103\36103h11.bil</ogi:file_loc ><ogi:mrsidurl >36103/mrsid/36103h11</ogi:mrsidurl > <ogi:utmdrgurl >36103/data/o36103h1</ogi:utmdrgurl ><ogi:albdrgurl >36103/al36103H1</ogi:albdrgurl ><ogi:utmzone >13</ogi:utmzone > <ogi:centerx >-103.031250</ogi:centerx ><ogi:centery >36.968750</ogi:centery > <ogi:the_geom><gml:Point srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"><gml:coordinates xmlns:gml="http://www.opengis.net/gml" decimal="." cs="," ts=" ">-103.03125032,36.96874905</gml:coordinates></gml:Point></ogi:the_geom> </ogi:doq_centroids> </gml:featureMember>

Change History (5)

comment:1 by dr, 13 years ago

Confirm. I think this problem because your xml tags contains many spaces, eg: <ogi:area >0.016000</ogi:area > (see source code of XML answer). Tags without spaces shows correctly in attribute table.

comment:2 by tybion, 13 years ago

Thanks, DR.

Good work. This GML comes straight out of Geoserver, but there must be something weird in the PostGIS table. Will ask the provider to check it out.

Regards, Tybion

comment:3 by dr, 13 years ago

It will be so useful if wfs provider could remove whitespace from the start and end of the tag name.

comment:4 by dr, 13 years ago

... or works with such tags correctly (shows in attribute table).

comment:5 by tybion, 13 years ago

Regarding '.. or works with such tags correctly (shows in attribute table)'

Should Quantum be able to -

  1. handle spaces in XML

OR

  1. report that the XML is incorrectly formatted

Isn't it a bug that Quantum does not at least tell the user that there is a problem with the XML?

Note: See TracTickets for help on using tickets.