Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
Great! Well done. Please let us know if you encounter any further difficulties. Kind regards, Ben. On 13/10/11 16:35, TRD wrote: > Finally I got it working (as no error appears anymore). The last error showed > up because a mismatch of namespaces. After correcting them everything seems > to work fine for now :D -- Ben Caradoc-Davies Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
Finally I got it working (as no error appears anymore). The last error showed up because a mismatch of namespaces. After correcting them everything seems to work fine for now :D -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6888099.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
You are totally right, those "-" were in the original xsd-file and truly are
not wanted there. I removed them and added the missing XMLSchema namespace.
This solved the occurence of the error "No top level element found in
schemas" but instead I'm getting "XSD type definition not found in schemas:
{http://www.opengis.net/iso19112}SI_LocationInstanceType. I checked the
linked iso19112.xsd for this type and it seems that this type is defined
there.
So I cannot detect why this error shows up.
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6888071.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
Should element-FormDefault be elementFormDefault? And should substitution-Group be substitutionGroup? Please resend as an attachment to ensure it is not being corrupted by email reformatting. Your schema element has no xmlns="http://www.w3.org/2001/XMLSchema"; which I thought was required to define your root element namespace. I'm not sure if this will cause your problems, but other schemas I use have it. Have you tried loading your schema in a validating editor. Eclipse (uses xerces) goes crazy. Your schemaUri element looks good. On 13/10/11 15:42, TRD wrote: > This is the schema file called dog_hk.xsd: > > > http://www.lverma.nrw.de/namespaces/dog"; > xmlns:dog="http://www.lverma.nrw.de/namespaces/dog"; > xmlns:gml="http://www.opengis.net/gml"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:iso19112="http://www.opengis.net/iso19112"; > xmlns:app="http://www.deegree.org/app"; > xmlns:wfs="http://www.deegree.org/wfs"; > xmlns:ogc="http://www.opengis.net/ogc"; > xmlns:deegreewfs="http://www.deegree.org/wfs"; > element-FormDefault="qualified" attributeFormDefault="unqualified"> > > Dieses Schema baut auf dem DOG-Profil für > Hauskoordinaten > Deutschland in der Version 1.0.1 auf. > > http://www.opengis.net/iso19112"; > schemaLocation="http://frameworkwfs.usgs.gov/framework/schemas/gazetteer/1.0.0/gmlsf1/iso19112.xsd"; > /> > >substitution-Group="iso19112:SI_LocationInstance" /> > > > > > >type="xsd:string" minOccurs="0" /> >type="xsd:integer" minOccurs="0" /> >minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >name="strassenname_normalisiert" type="xsd:string" > minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >name="ortsteilname_normalisiert" type="xsd:string" > minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >name="postOrtsteil_normalisiert" type="xsd:string" > minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >name="ortsnamePost_normalisiert" type="xsd:string" > minOccurs="0" /> >type="xsd:string" minOccurs="0" /> >name="zusatzOrtsname_normalisiert" type="xsd:string" > minOccurs="0" /> > > > > > > > and this is the reference for the schema file above: > > > http://localhost/dog_hk.xsd > > > > > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6887948.html > Sent from the GeoServer - User mailing list archive at Nabble.com. > > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > ___ > Geoserver-users mailing list > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Ben Caradoc-Davies Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oc
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
This is the schema file called dog_hk.xsd: http://www.lverma.nrw.de/namespaces/dog"; xmlns:dog="http://www.lverma.nrw.de/namespaces/dog"; xmlns:gml="http://www.opengis.net/gml"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:iso19112="http://www.opengis.net/iso19112"; xmlns:app="http://www.deegree.org/app"; xmlns:wfs="http://www.deegree.org/wfs"; xmlns:ogc="http://www.opengis.net/ogc"; xmlns:deegreewfs="http://www.deegree.org/wfs"; element-FormDefault="qualified" attributeFormDefault="unqualified"> Dieses Schema baut auf dem DOG-Profil für Hauskoordinaten Deutschland in der Version 1.0.1 auf. http://www.opengis.net/iso19112"; schemaLocation="http://frameworkwfs.usgs.gov/framework/schemas/gazetteer/1.0.0/gmlsf1/iso19112.xsd"; /> and this is the reference for the schema file above: http://localhost/dog_hk.xsd -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6887948.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
Please email your schema to the list. Please also show me the content of your schemaUri element in your mapping file. On 13/10/11 15:13, TRD wrote: > I am using another server for this purpose. Geoserver listens on port 8080, > the other one listens on port 80 so everything is fine. My schema file is > correctly transfered into the app-schema-cache folder. > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6887881.html > Sent from the GeoServer - User mailing list archive at Nabble.com. > > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > ___ > Geoserver-users mailing list > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Ben Caradoc-Davies Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
I am using another server for this purpose. Geoserver listens on port 8080, the other one listens on port 80 so everything is fine. My schema file is correctly transfered into the app-schema-cache folder. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6887881.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
If you are serving the schema from localhost via GeoServer, it will not be located, because GeoServer tries to download the schema (for app-schema) before GeoServer starts serving content. Or are you using another server on localhost? Try installing your schema in: app-schema-cache/localhost/path/to/your/schema.xsd and referring to it in your mapping as http://localhost/path/to/your/schema.xsd Then app-schema will resolve it in the cache. Kind regards, Ben. On 13/10/11 14:42, TRD wrote: > The file is shortened to contain only one FeatureType, in detail > "Hauskoordinate" which is used in the mapping. I did not edit the version in > my app-schema-cache directly. I edited the file located at my localhost and > deleted the file in the cache. This schema file does contain an element with > the appropiate WFS feature type. -- Ben Caradoc-Davies Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
The file is shortened to contain only one FeatureType, in detail "Hauskoordinate" which is used in the mapping. I did not edit the version in my app-schema-cache directly. I edited the file located at my localhost and deleted the file in the cache. This schema file does contain an element with the appropiate WFS feature type. > your message describes encountering an error, but does not give any > details. Do you see any errors in geoserver.log when it starts? Do you > see any errors when you attempt to query the service? > What is the nature of your error? Well, I assume that the email does not contain any raw-tag I used to provide the content of files and for the occured error too. So I'd like you to review my post at http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-td6884793.html This is the visual frontend of my topic with all replies and contains more information than the generated email. > I assume that you have configured your data store as described here: > http://docs.geoserver.org/latest/en/user/data/app-schema/data-stores.html#postgis That's true. And this is working if I edit the tutorial config to access my postgis database instead of propery-files. > Note that AppSchemaDataAccess.xsd is only used to assist editing with > schema-aware editors. It is not required by the app-schema plugin. Thank you for this hint. So I could remove the schema without any error. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6887829.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
What exactly do you mean when you say "This schema file is shortened so it only contains the referenced featureType"? Did you edit the version in your app-schema-cache? Note that the schema must contain an with the name of the WFS feature type. (A WFS type name is a schema element name.) How are you specifying your schema in your mapping file? What is the content of your targetTypes/FeatureType/schemaUri ? Schema resolution is detailed here: http://docs.geoserver.org/latest/en/user/data/app-schema/app-schema-resolution.html On 12/10/11 20:33, TRD wrote: > This schema file is shortened so it only contains the referenced featureType > (in fact there are some more types). The referenced iso19112.xsd in the > schema above is a local copy of this one: > http://frameworkwfs.usgs.gov/framework/schemas/gazetteer/1.0.0/gmlsf1/iso19112.xsd > and is available because geoserver is able to copy it to its > app-schema-cache dir. -- Ben Caradoc-Davies Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] App-Schema plugin, No top level element found in schemas
TRD, your message describes encountering an error, but does not give any details. Do you see any errors in geoserver.log when it starts? Do you see any errors when you attempt to query the service? What is the nature of your error? I assume that you have configured your data store as described here: http://docs.geoserver.org/latest/en/user/data/app-schema/data-stores.html#postgis One difference between PostGIS and property files is that, in a mapping file for PostGIS, all database identifiers (table and column names) must be lowercase (the tutorial uses all uppercase): http://docs.geoserver.org/latest/en/user/data/app-schema/mapping-file.html#database-identifiers Note that AppSchemaDataAccess.xsd is only used to assist editing with schema-aware editors. It is not required by the app-schema plugin. Kind regards, Ben. On 12/10/11 20:33, TRD wrote: > Dear Subsribers, > > I'm using the app-schema plugin for realizing a complex feature mapping. I'm > really new to this and that's why I cannot solve the following error for > myself. > I adapted the tutorial for the app-schema and want my data to be loaded from > a postgis database running on the same machine as the geoserver. While > geoserver is starting all datastores are detected and were checked to be > accessible. My newly created datastore is recognized but not accessible. > Geoserver shows me a > > Of course I googled around, found some topics with the same issue but > different reasons for occurence (not applicable here). I'm almost giving up > hope to get my configuration working. > > My configuration is the following one: > > folderpath inside workspaces-folder in geoserver's data_dir > dog > -dog_hauskoordinaten > --dog_hauskoordinaten > ---featuretype.xml > --AppSchemaDataAccess.xsd > --datastore.xml > --dog_hauskoordinaten.xml > -namespace.xml > -workspace.xml > > Assuming that namespace.xml and workspace.xml are well formed, > AppSchemaDataAccess.xsd is a direct copy of the one in the tutorial dir and > datastore.xml is well formed because geoserver is detecting my datastore > then the content of my files is described as follows: > > dog/dog_hauskoordinaten/dog_hauskoordinaten.xml (this file is referenced in > datastore.xml as mentioned in the tutorial) > > The database connection is definetely correct because I modified the > tutorial data to read the data out of my postgis database instead of > property-files (of course I created the neccessary table and recordsets). > The path to the given schema-file is correct, too. The file is copied into > the app-schema-cache folder of data_dir. I shortened the mapping of the > tutorial data and modified it to match my dog database. Maybe this mapping > contains some errors which I cannot detect for myself. > > dog/dog_hauskoordinaten/dog_hauskoordinaten/featuretype.xml > > This file is nearly the same as provided in the tutorial, I only changed id, > name and namespace to match with my environment. > > Finally here is the content of my schema file. > > This schema file is shortened so it only contains the referenced featureType > (in fact there are some more types). The referenced iso19112.xsd in the > schema above is a local copy of this one: > http://frameworkwfs.usgs.gov/framework/schemas/gazetteer/1.0.0/gmlsf1/iso19112.xsd > and is available because geoserver is able to copy it to its > app-schema-cache dir. > > It seems I am not as familiar with app-schema as needed to make the desired > changes for my environment and so I hope you can provide me help to get rid > of the shown error upwards. > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6884793.html > Sent from the GeoServer - User mailing list archive at Nabble.com. > > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > ___ > Geoserver-users mailing list > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Ben Caradoc-Davies Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net
[Geoserver-users] App-Schema plugin, No top level element found in schemas
Dear Subsribers, I'm using the app-schema plugin for realizing a complex feature mapping. I'm really new to this and that's why I cannot solve the following error for myself. I adapted the tutorial for the app-schema and want my data to be loaded from a postgis database running on the same machine as the geoserver. While geoserver is starting all datastores are detected and were checked to be accessible. My newly created datastore is recognized but not accessible. Geoserver shows me a Of course I googled around, found some topics with the same issue but different reasons for occurence (not applicable here). I'm almost giving up hope to get my configuration working. My configuration is the following one: folderpath inside workspaces-folder in geoserver's data_dir dog -dog_hauskoordinaten --dog_hauskoordinaten ---featuretype.xml --AppSchemaDataAccess.xsd --datastore.xml --dog_hauskoordinaten.xml -namespace.xml -workspace.xml Assuming that namespace.xml and workspace.xml are well formed, AppSchemaDataAccess.xsd is a direct copy of the one in the tutorial dir and datastore.xml is well formed because geoserver is detecting my datastore then the content of my files is described as follows: dog/dog_hauskoordinaten/dog_hauskoordinaten.xml (this file is referenced in datastore.xml as mentioned in the tutorial) The database connection is definetely correct because I modified the tutorial data to read the data out of my postgis database instead of property-files (of course I created the neccessary table and recordsets). The path to the given schema-file is correct, too. The file is copied into the app-schema-cache folder of data_dir. I shortened the mapping of the tutorial data and modified it to match my dog database. Maybe this mapping contains some errors which I cannot detect for myself. dog/dog_hauskoordinaten/dog_hauskoordinaten/featuretype.xml This file is nearly the same as provided in the tutorial, I only changed id, name and namespace to match with my environment. Finally here is the content of my schema file. This schema file is shortened so it only contains the referenced featureType (in fact there are some more types). The referenced iso19112.xsd in the schema above is a local copy of this one: http://frameworkwfs.usgs.gov/framework/schemas/gazetteer/1.0.0/gmlsf1/iso19112.xsd and is available because geoserver is able to copy it to its app-schema-cache dir. It seems I am not as familiar with app-schema as needed to make the desired changes for my environment and so I hope you can provide me help to get rid of the shown error upwards. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/App-Schema-plugin-No-top-level-element-found-in-schemas-tp6884793p6884793.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
