Sorry, pressed the wrong reply button... :(
Cheers
Carsten
___
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.
Hallo Frau Hock,
auch ich denke, dass ein Jira-Issue hier zunächst noch verfrüht ist und
nicht weiter hilft. Ich schreibe Ihnen direkt (nicht an die Liste);
vielleicht können wir so klären, wo das Problem liegt, bzw. ob der
GeoServer hier etwas falsch macht.
Der GeoServer enthält die Schemas
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: image.png]
Cheers
Andrea
On Wed, Feb 21, 2024 at 11:
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 ar
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 ser
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/
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 :
> Hello everyone,
>
> currently we are facing problems with the schemaLocations used in the
> WFS-Responses.
>
> The u
