Re: [Geoserver-users] SchemaLocations WFS Responses

[Anna-Lena Hock via Geoserver-users]

Hello,  Usually the schemaLocations are generated by Geoserver and use the same schemaLocation like the service-uri. Every schemaLocation points to those local uri, but there is only one schemaLocation which points to schemas.opengis.net. And there are other references to schema.opengis.net which are downloaded and defined twice in concequence - once by schema.opengis.net and our local uri.  I hope this one was better to understand.  I will open an issue on jira now.  Thanks for the reply!  Kind regards Anna-Lena  Am 21.02.2024 um 08:17 schrieb Roar Brænden <roar.brenden...@gmail.com>: Hi, Ï'm struggling to understand what you are asking about. You're saying: The user downloaded all the schemaLocations, which were all referenced locally until he came to this reference: What was he using when he downloaded those schemaLocations? How did those xsd-files end up on that server https://sgx.geodatenzentrum.de/web_geoserver_schemas? I suppose a solution would be to go through all the xsd-files at that location to make sure none of them are referring to an external entity if a local copy is present. Best regards, Roar Brænden 20. feb. 2024 kl. 13:07 skrev Anna-Lena Hock via Geoserver-users <geoserver-users@lists.sourceforge.net>: Hello, Unfortunately there was no reply to my question. Is it useful to open an issue on jira? Kind regards, Anna-Lena Am 31.01.2024 um 09:50 schrieb Anna-Lena Hock <anna-lenah...@gmx.de>: Hello everyone, currently we are facing problems with the schemaLocations used in the WFS-Responses. The user downloaded all the schemaLocations, which were all referenced locally until he came to this reference: https://sgx.geodatenzentrum.de/web_geoserver_schemas/gml/3.2.1/coordinateOperations.xsd Here is the problematic schemaLocation to schemas.opengis.net. Now the problems continues, because the objects will be defined twice - locally from sgx.geodatenzentrum.de and from schemas.opengis.net. Is there a workaround for this problem or a possibility to solve it? Kind regards, anna-lena _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users

_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users