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
Hi Christophe
Here's a quick hack to convert from PostGIS to PostGIS (JNDI), if you want
to try it. It works for me.
Assumption: you have read/write server access to the configuration
directory GEOSERVER_DATA_DIR
cd GEOSERVER_DATA_DIR/workspaces//
edit the file datastore.xml
change line 5 from
Hello Christophe,
You can copy your files to the folder matching your new datastore and you
have to change the technical IDs of the datastore in your files indeed.
Regards
Alexandre
Le mar. 20 févr. 2024 à 15:15, a écrit :
> Thanks Jody and Graham, it works fine and it’s well documented. That
Hi,
it cannot be done using the default security subsystem, but the GeoFence
extension allows to perform data clipping
on polygons based on the current user instead (it's a bit complicated to
use though).
Cheers
Andrea
On Tue, Feb 20, 2024 at 3:48 PM Markus Strauch
wrote:
> Hello,
>
>
>
> is
Thanks Jody and Graham, it works fine and it’s well documented. That is exactly
what I was looking for.
Now I need to figure out how to move all the already published layers from the
old postgis datastore to the new JNDI one since it’s the same database. I guess
moving the content of the
Hello,
is it possible to restrict the visibility of a layer to a certain bounding box,
ideally on a per-user basis? Think of a network operator that wants to publish
different parts of the network to different construction companies.
I have tried to publish a shapefile and decrease the size of
On Fri, Feb 16, 2024 at 3:27 PM Gabriel Roldan <
gabriel.rol...@camptocamp.com> wrote:
> Believe me I absolutely understand the convenience of just adding a
> parameter to the existing delete featuretype api. Heck, we would have saved
> all the time invested in this discussion an my customers
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:
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
