[TinyOWS-users] OSM_line table and failing DescribeFeatureType

[Rahkonen Jukka]

Hi,

I made a TinyOWS feature type (version 0.9.0 on Ubuntu) from OpenStreetMap data imported with osm2pgsql utility.  Feature type creation is successful, GetCapabilities is listing the feature type and GetFeature is returning features. However, DescribeFeatureType leads to some error. 
Browser shows this text (in Finnish):
XML-jäsennysvirhe: elementtiä ei löytynyt
URL: http://my_linux_host/cgi-bin/tinyows_osm?service=WFS&request=DescribeFeatureType&VERSION=1.1.0&TYPENAME=osm_suomi:osm_line
Rivinumero 9, sarake 1:

Translated: 
XML parsing error, could not find element
.....
Row 9, column 1:

The source code of the page shows this very truncated schema:

<?xml version='1.0' encoding='UTF-8'?>
<xs:schema targetNamespace='http://www.openstreetmap.org/' xmlns:osm_suomi='http://www.openstreetmap.org/' xmlns:ogc='http://www.opengis.net/ogc' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:gml='http://www.opengis.net/gml' elementFormDefault='qualified' version='1.1'>
<xs:import namespace='http://www.opengis.net/gml' schemaLocation='http://schemas.opengis.net/gml/3.1.1/base/gml.xsd'/>
<xs:element name='osm_line' type='osm_suomi:osm_lineType' substitutionGroup='gml:_Feature' />
<xs:complexType name='osm_lineType'>
 <xs:complexContent>
  <xs:extension base='gml:AbstractFeatureType'>
   <xs:sequence>

Table osm_line in PostGIS looks pretty standard to me:

          Table "public.osm_line"
       Column       |   Type   | Modifiers
--------------------+----------+-----------
 osm_id             | integer  |
 access             | text     |
 addr:flats         | text     |
 addr:housenumber   | text     |
 addr:interpolation | text     |
 admin_level        | text     |
 aerialway          | text     |
 aeroway            | text     |
 amenity            | text     |
 area               | text     |
 barrier            | text     |
 bicycle            | text     |
 bridge             | text     |
 boundary           | text     |
 building           | text     |
 construction       | text     |
 cutting            | text     |
 disused            | text     |
 embankment         | text     |
 foot               | text     |
 highway            | text     |
 historic           | text     |
 horse              | text     |
 junction           | text     |
 landuse            | text     |
 layer              | text     |
 learning           | text     |
 leisure            | text     |
 lock               | text     |
 man_made           | text     |
 military           | text     |
 motorcar           | text     |
 name               | text     |
 natural            | text     |
 oneway             | text     |
 operator           | text     |
 power              | text     |
 power_source       | text     |
 place              | text     |
 railway            | text     |
 ref                | text     |
 religion           | text     |
 residence          | text     |
 route              | text     |
 service            | text     |
 shop               | text     |
 sport              | text     |
 tourism            | text     |
 tracktype          | text     |
 tunnel             | text     |
 waterway           | text     |
 width              | text     |
 wood               | text     |
 z_order            | integer  |
 way_area           | real     |
 osm_user           | text     |
 osm_uid            | text     |
 osm_version        | text     |
 osm_timestamp      | text     |
 way                | geometry |
 priority           | integer  |

My colleague was able to repeat this error. He even renamed some fields which have been giving problems earlier:
 addr:flats  ->addrflats
 addr:housenumber ->addrhousenumber
 addr:interpolation ->addrinterpolation
 natural ->nature

Renaming the fields did not make DescribeFeatureType to work. Any idea about what is going wrong? DFT works with non-OSM feature types in the same service.

-Jukka Rahkonen-