Hi,
I have a really strange thing going on here. Everytime I restart Geoserver it forgets about the correct type for the geometry attribute of exactly 1 feature type. I have to go to the feature type config, submit it and save the changes.
The DescribeFeatureType request shows the following when run after geoserver has been started:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://irania:10080/geoserver" xmlns:kvla="http://irania:10080/geoserver" xmlns:gml="http://www.opengis.net/gml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="http://localhost:10080/geoserver/schemas/gml/2.1.2/feature.xsd"/>
<xs:complexType name="str_geom_Type">
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
<xs:sequence>
<xs:element type="xs:int" minOccurs="1" name="gid" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="str_schl" nillable="true" maxOccurs="1"/>
<xs:element type="xs:string" minOccurs="1" name="str_name" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="ortsteil" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="gem_schl" nillable="true" maxOccurs="1"/>
<xs:element type="gml:multiLineStringProperty" minOccurs="1" name="the_geom" nillable="true" maxOccurs="1"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="str_geom" type="kvla:str_geom_Type" substitutionGroup="gml:_Feature"/>
</xs:schema>
However the geometry type should be gml:MultiLineStringPropertyType. The feature comes from a postgis database and I have another feature that behaves correctly in the same database. The only difference I can see is that the correct working one is a PointType.
Anybody ever saw something like that? Any known workarounds/fixes?
Andreas
Andreas Pakulat schrieb:
Hi,
I have a really strange thing going on here. Everytime I restart Geoserver it forgets about the correct type for the geometry attribute of exactly 1 feature type. I have to go to the feature type config, submit it and save the changes.
The DescribeFeatureType request shows the following when run after geoserver has been started:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://irania:10080/geoserver" xmlns:kvla="http://irania:10080/geoserver" xmlns:gml="http://www.opengis.net/gml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="http://localhost:10080/geoserver/schemas/gml/2.1.2/feature.xsd"/>
<xs:complexType name="str_geom_Type">
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
<xs:sequence>
<xs:element type="xs:int" minOccurs="1" name="gid" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="str_schl" nillable="true" maxOccurs="1"/>
<xs:element type="xs:string" minOccurs="1" name="str_name" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="ortsteil" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="gem_schl" nillable="true" maxOccurs="1"/>
<xs:element type="gml:multiLineStringProperty" minOccurs="1" name="the_geom" nillable="true" maxOccurs="1"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="str_geom" type="kvla:str_geom_Type" substitutionGroup="gml:_Feature"/>
</xs:schema>
However the geometry type should be gml:MultiLineStringPropertyType. The feature comes from a postgis database and I have another feature that behaves correctly in the same database. The only difference I can see is that the correct working one is a PointType.
Anybody ever saw something like that? Any known workarounds/fixes?
Nobody got an idea why this happens to me?
Andreas
Are you editing it through the web admin tool? That tool doesn't work all that well for modifying individual elements, and we probably should just disable it. If you're editing and it works until you restart, then I imagine it's just not saving right.
But if the type should be gml:multiLineStringPropertyType instead of gml:multiLineStringProperty then that's probably a bug that we can just fix...
Chris
Andreas Pakulat wrote:
Andreas Pakulat schrieb:
Hi,
I have a really strange thing going on here. Everytime I restart Geoserver it forgets about the correct type for the geometry attribute of exactly 1 feature type. I have to go to the feature type config, submit it and save the changes.
The DescribeFeatureType request shows the following when run after geoserver has been started:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://irania:10080/geoserver" xmlns:kvla="http://irania:10080/geoserver" xmlns:gml="http://www.opengis.net/gml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="http://localhost:10080/geoserver/schemas/gml/2.1.2/feature.xsd"/>
<xs:complexType name="str_geom_Type">
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
<xs:sequence>
<xs:element type="xs:int" minOccurs="1" name="gid" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="str_schl" nillable="true" maxOccurs="1"/>
<xs:element type="xs:string" minOccurs="1" name="str_name" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="ortsteil" nillable="true" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="gem_schl" nillable="true" maxOccurs="1"/>
<xs:element type="gml:multiLineStringProperty" minOccurs="1" name="the_geom" nillable="true" maxOccurs="1"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="str_geom" type="kvla:str_geom_Type" substitutionGroup="gml:_Feature"/>
</xs:schema>
However the geometry type should be gml:MultiLineStringPropertyType. The feature comes from a postgis database and I have another feature that behaves correctly in the same database. The only difference I can see is that the correct working one is a PointType.
Anybody ever saw something like that? Any known workarounds/fixes?
Nobody got an idea why this happens to me?
Andreas
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Chris Holmes schrieb:
Are you editing it through the web admin tool? That tool doesn't work all that well for modifying individual elements, and we probably should just disable it. If you're editing and it works until you restart, then I imagine it's just not saving right.
Yes I was, however I removed and recreated the feature types and this time it stored everything correctly.
I also tried to change the .conf files on the disk, however at some point they were always overriden with the "wrong" gml-type again.
But if the type should be gml:multiLineStringPropertyType instead of gml:multiLineStringProperty then that's probably a bug that we can just fix...
Well, the now working schema uses gml:multiLineStringProperty too, however the GetFeatureTypeRequest now correctly has gml:MultiLineStringPropertyType for the corresponding element in the feature type schema.
Thus I'm absolutely unsure what went wrong, anyway I think the recreation fixed everything. Maybe I changed something using the web-config-tool and this somehow confused Geoserver.
Andreas
Andreas Pakulat schrieb:
Chris Holmes schrieb:
Are you editing it through the web admin tool? That tool doesn't work all that well for modifying individual elements, and we probably should just disable it. If you're editing and it works until you restart, then I imagine it's just not saving right.
Yes I was, however I removed and recreated the feature types and this time it stored everything correctly.
I also tried to change the .conf files on the disk, however at some point they were always overriden with the "wrong" gml-type again.
But if the type should be gml:multiLineStringPropertyType instead of gml:multiLineStringProperty then that's probably a bug that we can just fix...
Well, the now working schema uses gml:multiLineStringProperty too, however the GetFeatureTypeRequest now correctly has gml:MultiLineStringPropertyType for the corresponding element in the feature type schema.
Thus I'm absolutely unsure what went wrong, anyway I think the recreation fixed everything. Maybe I changed something using the web-config-tool and this somehow confused Geoserver.
Sorry, seems like it's there again, after a reboot of the machine it still gives me:
<xs:schema targetNamespace="http://irania:10080/geoserver" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="http://irania:10080/geoserver/schemas/gml/2.1.2/feature.xsd"/>
<xs:complexType name="str_geom_Type">
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
<xs:sequence>
<xs:element type="xs:int" minOccurs="1" name="gid" nillable="false" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="str_schl" nillable="false" maxOccurs="1"/>
<xs:element type="xs:string" minOccurs="1" name="str_name" nillable="false" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="ortsteil" nillable="false" maxOccurs="1"/>
<xs:element type="xs:long" minOccurs="1" name="gem_schl" nillable="false" maxOccurs="1"/>
<xs:element type="gml:multiLineStringProperty" minOccurs="1" name="the_geom" nillable="false" maxOccurs="1"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="str_geom" type="kvla:str_geom_Type" substitutionGroup="gml:_Feature"/>
as feature type schema (sorry for the bad layout). So the issue is still there.
Andreas