Re: [Geoserver-users] Setting AUTO CRSes

[Jody Garnett]

That is my understanding. I recall taking part in a test bed with uDig and
watching the UTM change as we panned across the map changing lat,long
location with each GetMap request.

Usually AUTO:97002 is one of the SRS options listed, and any client that
chooses that should know what to do.

Note the upcoming temporal based coordinate reference systems are
parametrized in a similar fashion.

Jody

On Tue, Jun 29, 2021 at 6:51 AM Jim Hughes  wrote:

> Hmm I suppose I'm expecting that a string like "AUTO:97002,-74,40.7"
> is sufficient to specify a layer's CRS.
>
> Are you saying that setting the CRS on a layer to "AUTO:97002" should
> work?  And that clients would have to be required to provide a lat/lon at
> request time?
>
> Cheers,
>
> Jim
> On 6/28/2021 6:46 PM, Jody Garnett wrote:
>
> The clients are supposed to be smart enough to pass in the lat/lon when
> making the getmap request. I am not sure if any clients are outside of
> testbeds.
> --
> Jody Garnett
>
>
> On Mon, 28 Jun 2021 at 15:35, Jim Hughes  wrote:
>
>> Hi all,
>>
>> I see that GeoTools has a few auto projections[1].  I tried setting them
>> in the GeoServer UI and that isn't working as I would hope/expect.  The
>> strings I tried were variations on "AUTO:97002,-74,40.7".
>>
>> Incidentally, that does work in a WFS 2.0 request.
>>
>> Is it possible to set the CRS on an entire layer to be one of these AUTO
>> CRSes?
>>
>> Thanks in advance,
>>
>> Jim
>>
>> 1.
>> https://docs.geotools.org/latest/userguide/library/referencing/crs.html
>>
>>
>>
>> ___
>> 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
>>
> --
--
Jody Garnett
___
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] Slow Performance on MSSQL View (Believe Caused by SQL Filter Function)

[mcharton]

We have a MSSQL 2012 View added as a layer in Geoserver 2.17.2 that performs
well with GetMap requests but times out with GetFeature requests.

 

We have tracked it down to the following Query sent from Geoserver to MSSQL:


 

SELECT top 1000 * FROM "schema"."MyTable_view" 

WHERE (

"SHAPE".Filter(geometry::STGeomFromText('POLYGON (())', 4326))
= 1 AND 

  "SHAPE".STIntersects(geometry::STGeomFromText('POLYGON
(())', 4326)) = 1   AND 

  "Field1" = 1234 AND 

"Field1" IS NOT NULL

)

 

The view is just an inner join between two tables, both of which have a
variety of indexes including a proper spatial index on the "shape" field.

 

If I run this query manually against SQL, it basically runs indefinitely.
HOWEVER, 

1.  if I remove the "SHAPE".Filter() function in the where clause, it
returns results in less than a second.
2.  If I remove the subsequent "Field1" query criteria from the where
clause, it returns results in less than a second.  I assume this points to
the culprit here being that it is using the Field1 index instead of the
spatial index on the tables.

 

Is there a good solution to this problem?  We are somewhat new to Geoserver,
so we may very well be doing something wrong.  I have tried to find a way to
force the spatial query in the view with no luck.  Any help would be much
appreciated!

 

Thanks,

 

Matt

___
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

Re: [Geoserver-users] Setting AUTO CRSes

[Jim Hughes]

Hmm I suppose I'm expecting that a string like "AUTO:97002,-74,40.7" 
is sufficient to specify a layer's CRS.


Are you saying that setting the CRS on a layer to "AUTO:97002" should 
work?  And that clients would have to be required to provide a lat/lon 
at request time?


Cheers,

Jim

On 6/28/2021 6:46 PM, Jody Garnett wrote:
The clients are supposed to be smart enough to pass in the lat/lon 
when making the getmap request. I am not sure if any clients are 
outside of testbeds.

--
Jody Garnett


On Mon, 28 Jun 2021 at 15:35, Jim Hughes > wrote:


Hi all,

I see that GeoTools has a few auto projections[1].  I tried
setting them
in the GeoServer UI and that isn't working as I would
hope/expect.  The
strings I tried were variations on "AUTO:97002,-74,40.7".

Incidentally, that does work in a WFS 2.0 request.

Is it possible to set the CRS on an entire layer to be one of
these AUTO
CRSes?

Thanks in advance,

Jim

1.
https://docs.geotools.org/latest/userguide/library/referencing/crs.html




___
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

[Geoserver-users] eMail footer

[Russ Hore]

Might be pedantic but I noticed in the email footer a typo?

- Earning your support instead of buying it, *but* Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/ 


Russ___
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