I just did this yesterday. I followed the first two links in the index for
COG documentation:
https://docs.geoserver.org/main/en/user/community/cog/index.html
The most relevant lines in indexer.properties are:
Cog=true
CanBeEmpty=true
I also chose to pre-populate granules, and define a layer aft
This is resolved now. The issue was with the operating system; it works
with Windows 10 rather than Windows 11.
Rikesh
On Fri, 3 Nov 2023 at 18:17, Rikesh Lad wrote:
> Hi Zdeněk,
>
> I double-checked all my environment variables but no luck. The error I'm
> getting is below.
>
> [image: image
Cécile,
My customers would find this concept useful, and I would support you in
making a proposal.
I like the idea of making a new REST API endpoint to avoid overlap and
accidental use. Also gives an opportunity for and admin setting to disable
for those inclined.
--
Jody Garnett
On Mon, Feb 12
I sorry you feel that way Andrea.
>From my point of view, there's no direction taken but an open and honest
discussion. And I can't see how my attitude is bad at all, given there's
absolutely no personal direction on any of my comments.
I've a strong opinion on the matter, yes. How relevant is it?
I'm in disagreement with both the direction taken and the attitude shown,
best to put an end to it and make it go through a formal GSIP instead (when
someone has the resources to spend on both the discussion and
implementation of it)
Regards
Andrea
Il gio 15 feb 2024, 20:19 Gabriel Roldan ha
s
Two wrongs don't make a right, IMHO.
I'd rather break convention than introduce such a dangerous parameter to an
existing API endpoint and change its semantics
I'm not talking about a rewrite of the REST API, but a new verb to the
existing API. Don't see how that'd make it harder for the people th
On Thu, Feb 15, 2024 at 3:00 PM Gabriel Roldan
wrote:
> I mean "increases complexity and difficults understanding", of course.
>
But parameters are already widely used in the GeoServer REST API, and
"cascade" is used in other places as well.
This would be breaking convention, making the API hard
Hi,
Good points, Gabriel.
I support having a little more explicit end-points for the different operations.
Regards,
Roar Brænden
> 15. feb. 2024 kl. 15:00 skrev Gabriel Roldan :
>
>
>
> * Flag parameters are bad design, increases complexity and understanding,
> breaks a couple principles.
>
>
> * Flag parameters are bad design, increases complexity and understanding,
> breaks a couple principles.
>
I mean "increases complexity and difficults understanding", of course.
> question arises of how to determine which table to delete once you deleted
> the FeatureType. I guess it should b
Indeed good points about ease of use.
Still, I'd add to the danger list:
* you can't guarantee the atomicity of the operation
* in general terms it is not the exact reverse of the create feature type
functionality. A single db table may be used by several feature types
across different workspaces e
I like Andrea's take but Gabriel made a very good point.
I agree with Gabriel that certain tasks should stay outside GeoServer but
reality is that we have a number of users which have very small
infrastructures and they cannot afford having pipelines to perform some
tasks outside of it and they sim
Hello everybody,
I think the benefits of leaving this possibility to the users might well
overcome the dangers.
I agree this is utterly dangerous, so it would be wise to leave that
feature off by default, and have a config item to activate it on purpose,
so the users and sysadmins shall be well awa
Hi all,
the typical GeoServer approach is not to be opinionated about things.
"Proudly letting users free since 2002" could be our slogan... want to be
strictly OGC compliant? We have a checkbox for you.
Want to do things in a more convenient way and the hell with standard
strictness? We also suppo
Hi,
I do not believe that it is generally possible to know if the table was created
with REST API or by some other means. It is possible to check the owner of the
table and if Geoserver is configured to use a special database account with
well thought-out privileges it might be safe to allow to
14 matches
Mail list logo
