[Geoserver-users] SchemaLocations WFS Responses

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 continue, 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

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-lenahock@anonymised.com>:
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

Hi Anna,
it is your right to open a ticket in Jira. and if you provide steps to reproduce (sample data, mapping files and so on) it would
be useful as well. But I very much doubt it will change anything, in terms of getting an answer.

If you need a solution now, see this guide:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it


Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail

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

  1. 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-lenahock@anonymised.com>:
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:

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@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/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.no@anonymised.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

  1. 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-lenahock@anonymised.com>:
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:

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

Anna,
do you need them to be all local, or would it be ok if they were all sitting on schemas.opengis.net?
If the latter is ok, then maybe this setting, found in the WFS admin page, is an answer: “encode canonical wfs schema location”

image.png

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it


Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail