[Geoserver-users] Fwd: Artifacts in NetCDFs served to Leaflet over WMS

[James Goldie]

Re-sending with attached screenshots linked instead.

-- Forwarded message -
From: James Goldie 
Date: Tue, Mar 6, 2018 at 10:33 AM
Subject: Artifacts in NetCDFs served to Leaflet over WMS
To: geoserver-users@lists.sourceforge.net <
geoserver-users@lists.sourceforge.net>


Hi there,

I'm having some interesting artifacts pop up on the WMS layers I serve to
Leaflet.  The layers come from NetCDF data stores, and they only appear at
closer zooms (higher than 4 or so).

Some of the artifacts appear to be values that appear in regions where
eveyrhting should be NaN (transparent); others appear to be the boundaries
between tiles not lining up properly. However, the tiles appear to be
positioned correctly in Leaflet; when I inspect the tile requests in
Chrome's Developer Tools, the artifacts are present in them.

I'm running Geoserver 2.12.1 on macOS 10.13.3.

I've attached some screenshots showing the changing artifacts as I zoom in
(there are no artifacts in the first):

https://imgur.com/a/FyzgJ (Note: I'm linking to these screenshots, as I
tried attaching them and my mail didn't appear on the mailing list.)

Thanks very much,

James
-- 
=
James Goldie: PhD Student, Climate Change Research Centre
Email: j.gol...@unsw.edu.au, m...@rensa.co
Tel: +61 421 747 208 <0421%20747%20208>
Skype: james-goldie
Web: https://rensa.co
-- 
=
James Goldie: PhD Student, Climate Change Research Centre
Email: j.gol...@unsw.edu.au, m...@rensa.co
Tel: +61 421 747 208
Skype: james-goldie
Web: https://rensa.co
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] how to get pg_admin layer from database schema into geoserver to display as a shapefile

[Rahkonen Jukka (MML)]

Hi,

Your question does not make it especially clear what you have done, how far you 
have gotten, and what stopped you. Anyway, 
you should start by creating a store 
http://docs.geoserver.org/stable/en/user/data/database/postgis.html and then 
publish the layer that you want 
http://docs.geoserver.org/stable/en/user/data/webadmin/layers.html

I do not understand what role QGIS has in this play. Are you using it as a WMS 
client or what? "Display PostGIS data as a shapefile" does not make sense at 
all, please try to explain better what you mean.

-Jukka Rahkonen-

-Alkuperäinen viesti-
Lähettäjä: GeorgeJones92 [mailto:george.jo...@aberdeen.sd.us] 
Lähetetty: 8. maaliskuuta 2018 23:13
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] how to get pg_admin layer from database schema into 
geoserver to display as a shapefile

hi all,
I'm really stumped. I really don't know how to load it in. the current 
documentation does not provide any trouble shooting tips. I currently have 
geoserver 2.10.2 and have QGIS 2.18.7 installed. it could be i need to upgrade 
to a more current version on qgis. 




-any thoughts?

GJ



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
___
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

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] how to get pg_admin layer from database schema into geoserver to display as a shapefile

[GeorgeJones92]

hi all,
I'm really stumped. I really don't know how to load it in. the current
documentation does not provide any trouble shooting tips. I currently have
geoserver 2.10.2 and have QGIS 2.18.7 installed. it could be i need to
upgrade to a more current version on qgis. 




-any thoughts?

GJ



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] GeoServer 2.13-RC1 Released

[Torben Barsballe]

We are happy to announce the release of GeoServer 2.13-RC1
.
Downloads are available (zip

, war

, and exe
)
along with docs and extensions.

This is a release candidate of GeoServer made in conjunction with GeoTools
19-RC1.

We want to encourage people to test the release thoroughly and report back
any issue found. With no further delay, let’s see what’s new, that is, what
is there to test!
Isolated Workspaces

The concept of an "Isolated Workspaces" has been added to GeoServer, to
allow for reusing a namespace among multiple workspaces. In particular, an
isolated workspace allows reuse of a namespace already used by another
workspace, but its resources (layers, styles, etc ...) can only be
retrieved when using that workspace's virtual services and will only show
up in those virtual service capabilities documents.

When reusing a namespace among workspaces, exactly one of those must be
non-isolated, and the rest must be isolated; i.e. isolated workspaces have
no restrictions in namespaces usage but the existing restrictions still
apply for non isolated workspaces.

This is particularly useful for those publishing complex schemas for
INSPIRE compliance. For more details, refer to the original proposal

.
GeoWebCache REST API

Two new endpoints have been added to the GeoWebCache REST API:

   - /gwc/rest/blobstores:
  - GET /gwc/rest/blobstores for a list of the blobstores
  - GET /gwc/rest/blobstores/{blobStoreName} for details about a single
  blobstore
  - PUT /gwc/rest/blobstores/{blobStoreName} to create or update a
  blobstore
  - DELETE /gwc/rest/blobstores/{blobStoreName} to remove a blobstore
   - /gwc/rest/gridsets:
  - GET /gwc/rest/gridsets for a list of the gridsets
  - GET /gwc/rest/gridsets/{gridSetName} for details about a single
  gridset
  - PUT /gwc/rest/gridsets/{gridSetName} to create or update a gridset
  - DELETE /gwc/rest/gridsets/{gridSetName} to remove a gridset

API docs for these endpoints will be added to the GeoServer documentation
shortly. Until then, the request body syntax for PUT requests closely
matched the equivalent structures in geowebcache.xml: BlobStores

and GridSets

.

The ArcGISCache backed layers are now also configurable via the REST API.

This release sees a major reworking of the configuration system in
GeoWebCache that will allow for plugging in alternate configuration
persistence mechanisms in future. While these changes should be largely
invisible to users, it is a huge update that impacts all of GeoWebCache.
However, due to these changes, we ask that you *please test the embedded
GeoWebCache*.
UI Improvements

Entering in URLs for data files has been improved with autocomplete - now
GeoServer will scan the path that has already been typed, and suggest
existing files within that path.


In addition, autocomplete support has been added to a number of dropdowns
which contain a long list of values, such as stores or layers. You can now
start typing the name of an option, and the visible options will be
filtered to match.


Editing raster layer parameters made easier, from a wall a text input
fields, to appropriate controls being used depending on the parameter type.
Here is a "before and after" comparison:



Finally, error messages are now displayed both at top (as usual) and bottom
(new!) in all configuration pages. This should make it easier to locate
error messages, especially while editing styles:




GeoPackage performance improvements

GeoPackage reading and rendering performance improved significantly, up to
two times faster on large datasets full extractions and 50% faster on small
bounding box searches, bringing GeoPackage on par with PostGIS. We also
have a Google spreadsheet with more details.


Shapefile remains king of full dataset extractions and the fastest data
source for pure spatial driven queries.
WFS 2.0 and WMTS 1.0 OGC compliance work

During the 

Re: [Geoserver-users] problem with cql_filter "id in(...)"

[Andrea Aime]

I'm afraid it is not documented (pull request welcomed*), but see here:
https://github.com/geotools/geotools/blob/72fc9c6957523db35c4c6b0348ef036f5c875157/modules/library/cql/src/main/jjtree/ECQLGrammar.jjt#L156
https://github.com/geotools/geotools/blob/72fc9c6957523db35c4c6b0348ef036f5c875157/modules/library/cql/src/main/jjtree/ECQLGrammar.jjt#L420

Cheers
Andrea

*: http://docs.geoserver.org/latest/en/docguide/quickfix.html

On Thu, Mar 8, 2018 at 4:23 PM, Jason Newmoyer  wrote:

> I figured something like that. Can you share a reference for that? I know
> I went looking and couldn't find anything.
>
>
> Jason Newmoyer
> Newmoyer Geospatial Solutions
> 843.606.0424 <(843)%20606-0424>
> ja...@newmoyergeospatial.com
>
>
>
> On Thu, Mar 8, 2018 at 10:18 AM, Andrea Aime  > wrote:
>
>> Hi,
>> id, unquoted, is a keyword in CQL, not an attribute name :)
>>
>> Cheers
>> Andrea
>>
>> On Thu, Mar 8, 2018 at 4:08 PM, Jason Newmoyer <
>> ja...@newmoyergeospatial.com> wrote:
>>
>>> Ran into this same issue, but with WMS. For me, quoting "id" in the CQL
>>> made it work. This doesn't seem to be required for other fields in the same
>>> table. So maybe just something special for ones named "id"
>>>
>>>
>>> Jason Newmoyer
>>> Newmoyer Geospatial Solutions
>>> 843.606.0424 <(843)%20606-0424>
>>> ja...@newmoyergeospatial.com
>>>
>>>
>>>
>>> On Wed, Mar 7, 2018 at 6:14 PM, Walter Nordmann 
>>> wrote:
>>>
 got it.

 after setting "id" to be the primary key, the query is returning
 results.

 regards
 walter



 Am 07.03.2018 um 19:31 schrieb Walter Nordmann:

> Hi
>
> still using geoserver 2.8
>
> i'm trying to get some polygons calling my local GeoServer using
> javascript and ajax.
>
> doing this call
>
>data: {
>service : "WFS",
>version : "1.1.0",
> request : "GetFeature",
>   outputFormat : "application/json",
>SrsName : "EPSG:4326",
>typeName: "osm:Admin Boundaries",
>  cql_filter: "id=403139"
>  },
>
> is working fine as can be seen in the log:
>
> 2018-03-07 19:11:39,441 INFO [geoserver.wfs] -
> Request: getFeature
> service = WFS
> version = 1.1.0
> baseUrl = http://localhost:8080/geoserver/
> query[0]:
> filter = [ id = 403139 ]
> srsName = EPSG:4326
> typeName[0] = {osm.osm.org}Admin Boundaries
> outputFormat = application/json
> resultType = results
> 2018-03-07 19:11:39,442 INFO [wfs.json] - about to encode JSON
> 2018-03-07 19:11:39,442 DEBUG [geotools.jdbc] - CREATE CONNECTION
> 2018-03-07 19:11:39,449 DEBUG [geotools.jdbc] - CLOSE CONNECTION
> 2018-03-07 19:11:39,449 DEBUG [geotools.jdbc] - CREATE CONNECTION
> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting SQL
> ComparisonFilter
> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting
> PropertyName
> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting
> LiteralExpression
> 2018-03-07 19:11:39,452 DEBUG [geotools.jdbc] - SELECT count(*) FROM
> (select id,
>value "name",
>localname,
>level admin_level,
>way
>   from boundaries
> ) as "vtable" WHERE  "id" = 403139
> 2018-03-07 19:11:39,454 DEBUG [geotools.jdbc] - CLOSE CONNECTION
> ...
>
> "WHERE id=403139" has been added to the query.
>
> Changing cql_filter to "id in(403139,1374326)" will give no result.
>
> 2018-03-07 19:24:19,377 INFO [geoserver.wfs] -
> Request: getFeature
> service = WFS
> version = 1.1.0
> baseUrl = http://localhost:8080/geoserver/
> query[0]:
> filter = [ 403139, 1374326 ]
> srsName = EPSG:4326
> typeName[0] = {osm.osm.org}Admin Boundaries
> outputFormat = application/json
> resultType = results
> 2018-03-07 19:24:19,378 INFO [wfs.json] - about to encode JSON
> 2018-03-07 19:24:19,378 DEBUG [geotools.jdbc] - CREATE CONNECTION
> 2018-03-07 19:24:19,384 DEBUG [geotools.jdbc] - CLOSE CONNECTION
> 2018-03-07 19:24:19,384 TRACE [geotools.core] - condition:
> Filter.INCLUDE
> 2018-03-07 19:24:19,384 DEBUG [geotools.jdbc] - CREATE CONNECTION
> 2018-03-07 19:24:19,385 DEBUG [geotools.jdbc] - SELECT count(*) FROM
> (select id,
>value "name",
>localname,
>level admin_level,
>way
>   from boundaries
> ) as "vtable" WHERE  0 = 1
> 2018-03-07 19:24:19,386 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>
> Strange to me is "filter [403137, 1374326]" without specifing "id".
>
> any hints?
>

Re: [Geoserver-users] problem with cql_filter "id in(...)"

[Jason Newmoyer]

I figured something like that. Can you share a reference for that? I know I
went looking and couldn't find anything.


Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
ja...@newmoyergeospatial.com



On Thu, Mar 8, 2018 at 10:18 AM, Andrea Aime 
wrote:

> Hi,
> id, unquoted, is a keyword in CQL, not an attribute name :)
>
> Cheers
> Andrea
>
> On Thu, Mar 8, 2018 at 4:08 PM, Jason Newmoyer <
> ja...@newmoyergeospatial.com> wrote:
>
>> Ran into this same issue, but with WMS. For me, quoting "id" in the CQL
>> made it work. This doesn't seem to be required for other fields in the same
>> table. So maybe just something special for ones named "id"
>>
>>
>> Jason Newmoyer
>> Newmoyer Geospatial Solutions
>> 843.606.0424 <(843)%20606-0424>
>> ja...@newmoyergeospatial.com
>>
>>
>>
>> On Wed, Mar 7, 2018 at 6:14 PM, Walter Nordmann  wrote:
>>
>>> got it.
>>>
>>> after setting "id" to be the primary key, the query is returning results.
>>>
>>> regards
>>> walter
>>>
>>>
>>>
>>> Am 07.03.2018 um 19:31 schrieb Walter Nordmann:
>>>
 Hi

 still using geoserver 2.8

 i'm trying to get some polygons calling my local GeoServer using
 javascript and ajax.

 doing this call

data: {
service : "WFS",
version : "1.1.0",
 request : "GetFeature",
   outputFormat : "application/json",
SrsName : "EPSG:4326",
typeName: "osm:Admin Boundaries",
  cql_filter: "id=403139"
  },

 is working fine as can be seen in the log:

 2018-03-07 19:11:39,441 INFO [geoserver.wfs] -
 Request: getFeature
 service = WFS
 version = 1.1.0
 baseUrl = http://localhost:8080/geoserver/
 query[0]:
 filter = [ id = 403139 ]
 srsName = EPSG:4326
 typeName[0] = {osm.osm.org}Admin Boundaries
 outputFormat = application/json
 resultType = results
 2018-03-07 19:11:39,442 INFO [wfs.json] - about to encode JSON
 2018-03-07 19:11:39,442 DEBUG [geotools.jdbc] - CREATE CONNECTION
 2018-03-07 19:11:39,449 DEBUG [geotools.jdbc] - CLOSE CONNECTION
 2018-03-07 19:11:39,449 DEBUG [geotools.jdbc] - CREATE CONNECTION
 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting SQL
 ComparisonFilter
 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting PropertyName
 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting
 LiteralExpression
 2018-03-07 19:11:39,452 DEBUG [geotools.jdbc] - SELECT count(*) FROM
 (select id,
value "name",
localname,
level admin_level,
way
   from boundaries
 ) as "vtable" WHERE  "id" = 403139
 2018-03-07 19:11:39,454 DEBUG [geotools.jdbc] - CLOSE CONNECTION
 ...

 "WHERE id=403139" has been added to the query.

 Changing cql_filter to "id in(403139,1374326)" will give no result.

 2018-03-07 19:24:19,377 INFO [geoserver.wfs] -
 Request: getFeature
 service = WFS
 version = 1.1.0
 baseUrl = http://localhost:8080/geoserver/
 query[0]:
 filter = [ 403139, 1374326 ]
 srsName = EPSG:4326
 typeName[0] = {osm.osm.org}Admin Boundaries
 outputFormat = application/json
 resultType = results
 2018-03-07 19:24:19,378 INFO [wfs.json] - about to encode JSON
 2018-03-07 19:24:19,378 DEBUG [geotools.jdbc] - CREATE CONNECTION
 2018-03-07 19:24:19,384 DEBUG [geotools.jdbc] - CLOSE CONNECTION
 2018-03-07 19:24:19,384 TRACE [geotools.core] - condition:
 Filter.INCLUDE
 2018-03-07 19:24:19,384 DEBUG [geotools.jdbc] - CREATE CONNECTION
 2018-03-07 19:24:19,385 DEBUG [geotools.jdbc] - SELECT count(*) FROM
 (select id,
value "name",
localname,
level admin_level,
way
   from boundaries
 ) as "vtable" WHERE  0 = 1
 2018-03-07 19:24:19,386 DEBUG [geotools.jdbc] - CLOSE CONNECTION

 Strange to me is "filter [403137, 1374326]" without specifing "id".

 any hints?

 Regards
 walter

 btw: i need the select list because this part will be dynamic later.



 --

 Check out the vibrant tech community on one of the world's most
 engaging tech sites, Slashdot.org! http://sdm.link/slashdot
 ___
 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:
 

Re: [Geoserver-users] problem with cql_filter "id in(...)"

[Andrea Aime]

Hi,
id, unquoted, is a keyword in CQL, not an attribute name :)

Cheers
Andrea

On Thu, Mar 8, 2018 at 4:08 PM, Jason Newmoyer  wrote:

> Ran into this same issue, but with WMS. For me, quoting "id" in the CQL
> made it work. This doesn't seem to be required for other fields in the same
> table. So maybe just something special for ones named "id"
>
>
> Jason Newmoyer
> Newmoyer Geospatial Solutions
> 843.606.0424 <(843)%20606-0424>
> ja...@newmoyergeospatial.com
>
>
>
> On Wed, Mar 7, 2018 at 6:14 PM, Walter Nordmann  wrote:
>
>> got it.
>>
>> after setting "id" to be the primary key, the query is returning results.
>>
>> regards
>> walter
>>
>>
>>
>> Am 07.03.2018 um 19:31 schrieb Walter Nordmann:
>>
>>> Hi
>>>
>>> still using geoserver 2.8
>>>
>>> i'm trying to get some polygons calling my local GeoServer using
>>> javascript and ajax.
>>>
>>> doing this call
>>>
>>>data: {
>>>service : "WFS",
>>>version : "1.1.0",
>>> request : "GetFeature",
>>>   outputFormat : "application/json",
>>>SrsName : "EPSG:4326",
>>>typeName: "osm:Admin Boundaries",
>>>  cql_filter: "id=403139"
>>>  },
>>>
>>> is working fine as can be seen in the log:
>>>
>>> 2018-03-07 19:11:39,441 INFO [geoserver.wfs] -
>>> Request: getFeature
>>> service = WFS
>>> version = 1.1.0
>>> baseUrl = http://localhost:8080/geoserver/
>>> query[0]:
>>> filter = [ id = 403139 ]
>>> srsName = EPSG:4326
>>> typeName[0] = {osm.osm.org}Admin Boundaries
>>> outputFormat = application/json
>>> resultType = results
>>> 2018-03-07 19:11:39,442 INFO [wfs.json] - about to encode JSON
>>> 2018-03-07 19:11:39,442 DEBUG [geotools.jdbc] - CREATE CONNECTION
>>> 2018-03-07 19:11:39,449 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>>> 2018-03-07 19:11:39,449 DEBUG [geotools.jdbc] - CREATE CONNECTION
>>> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting SQL
>>> ComparisonFilter
>>> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting PropertyName
>>> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting
>>> LiteralExpression
>>> 2018-03-07 19:11:39,452 DEBUG [geotools.jdbc] - SELECT count(*) FROM
>>> (select id,
>>>value "name",
>>>localname,
>>>level admin_level,
>>>way
>>>   from boundaries
>>> ) as "vtable" WHERE  "id" = 403139
>>> 2018-03-07 19:11:39,454 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>>> ...
>>>
>>> "WHERE id=403139" has been added to the query.
>>>
>>> Changing cql_filter to "id in(403139,1374326)" will give no result.
>>>
>>> 2018-03-07 19:24:19,377 INFO [geoserver.wfs] -
>>> Request: getFeature
>>> service = WFS
>>> version = 1.1.0
>>> baseUrl = http://localhost:8080/geoserver/
>>> query[0]:
>>> filter = [ 403139, 1374326 ]
>>> srsName = EPSG:4326
>>> typeName[0] = {osm.osm.org}Admin Boundaries
>>> outputFormat = application/json
>>> resultType = results
>>> 2018-03-07 19:24:19,378 INFO [wfs.json] - about to encode JSON
>>> 2018-03-07 19:24:19,378 DEBUG [geotools.jdbc] - CREATE CONNECTION
>>> 2018-03-07 19:24:19,384 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>>> 2018-03-07 19:24:19,384 TRACE [geotools.core] - condition: Filter.INCLUDE
>>> 2018-03-07 19:24:19,384 DEBUG [geotools.jdbc] - CREATE CONNECTION
>>> 2018-03-07 19:24:19,385 DEBUG [geotools.jdbc] - SELECT count(*) FROM
>>> (select id,
>>>value "name",
>>>localname,
>>>level admin_level,
>>>way
>>>   from boundaries
>>> ) as "vtable" WHERE  0 = 1
>>> 2018-03-07 19:24:19,386 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>>>
>>> Strange to me is "filter [403137, 1374326]" without specifing "id".
>>>
>>> any hints?
>>>
>>> Regards
>>> walter
>>>
>>> btw: i need the select list because this part will be dynamic later.
>>>
>>>
>>>
>>> --
>>>
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> 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-req
>>> uesting-and-integrating-new-features-and-improvements-in-GeoServer
>>>
>>>
>>> Geoserver-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>
>>
>> 

Re: [Geoserver-users] problem with cql_filter "id in(...)"

[Jason Newmoyer]

Ran into this same issue, but with WMS. For me, quoting "id" in the CQL
made it work. This doesn't seem to be required for other fields in the same
table. So maybe just something special for ones named "id"


Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
ja...@newmoyergeospatial.com



On Wed, Mar 7, 2018 at 6:14 PM, Walter Nordmann  wrote:

> got it.
>
> after setting "id" to be the primary key, the query is returning results.
>
> regards
> walter
>
>
>
> Am 07.03.2018 um 19:31 schrieb Walter Nordmann:
>
>> Hi
>>
>> still using geoserver 2.8
>>
>> i'm trying to get some polygons calling my local GeoServer using
>> javascript and ajax.
>>
>> doing this call
>>
>>data: {
>>service : "WFS",
>>version : "1.1.0",
>> request : "GetFeature",
>>   outputFormat : "application/json",
>>SrsName : "EPSG:4326",
>>typeName: "osm:Admin Boundaries",
>>  cql_filter: "id=403139"
>>  },
>>
>> is working fine as can be seen in the log:
>>
>> 2018-03-07 19:11:39,441 INFO [geoserver.wfs] -
>> Request: getFeature
>> service = WFS
>> version = 1.1.0
>> baseUrl = http://localhost:8080/geoserver/
>> query[0]:
>> filter = [ id = 403139 ]
>> srsName = EPSG:4326
>> typeName[0] = {osm.osm.org}Admin Boundaries
>> outputFormat = application/json
>> resultType = results
>> 2018-03-07 19:11:39,442 INFO [wfs.json] - about to encode JSON
>> 2018-03-07 19:11:39,442 DEBUG [geotools.jdbc] - CREATE CONNECTION
>> 2018-03-07 19:11:39,449 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>> 2018-03-07 19:11:39,449 DEBUG [geotools.jdbc] - CREATE CONNECTION
>> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting SQL
>> ComparisonFilter
>> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting PropertyName
>> 2018-03-07 19:11:39,452 DEBUG [geotools.filter] - exporting
>> LiteralExpression
>> 2018-03-07 19:11:39,452 DEBUG [geotools.jdbc] - SELECT count(*) FROM
>> (select id,
>>value "name",
>>localname,
>>level admin_level,
>>way
>>   from boundaries
>> ) as "vtable" WHERE  "id" = 403139
>> 2018-03-07 19:11:39,454 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>> ...
>>
>> "WHERE id=403139" has been added to the query.
>>
>> Changing cql_filter to "id in(403139,1374326)" will give no result.
>>
>> 2018-03-07 19:24:19,377 INFO [geoserver.wfs] -
>> Request: getFeature
>> service = WFS
>> version = 1.1.0
>> baseUrl = http://localhost:8080/geoserver/
>> query[0]:
>> filter = [ 403139, 1374326 ]
>> srsName = EPSG:4326
>> typeName[0] = {osm.osm.org}Admin Boundaries
>> outputFormat = application/json
>> resultType = results
>> 2018-03-07 19:24:19,378 INFO [wfs.json] - about to encode JSON
>> 2018-03-07 19:24:19,378 DEBUG [geotools.jdbc] - CREATE CONNECTION
>> 2018-03-07 19:24:19,384 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>> 2018-03-07 19:24:19,384 TRACE [geotools.core] - condition: Filter.INCLUDE
>> 2018-03-07 19:24:19,384 DEBUG [geotools.jdbc] - CREATE CONNECTION
>> 2018-03-07 19:24:19,385 DEBUG [geotools.jdbc] - SELECT count(*) FROM
>> (select id,
>>value "name",
>>localname,
>>level admin_level,
>>way
>>   from boundaries
>> ) as "vtable" WHERE  0 = 1
>> 2018-03-07 19:24:19,386 DEBUG [geotools.jdbc] - CLOSE CONNECTION
>>
>> Strange to me is "filter [403137, 1374326]" without specifing "id".
>>
>> any hints?
>>
>> Regards
>> walter
>>
>> btw: i need the select list because this part will be dynamic later.
>>
>>
>>
>> --
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> 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-req
>> uesting-and-integrating-new-features-and-improvements-in-GeoServer
>>
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning 

Re: [Geoserver-users] CSW questions and maybe issues

[Andrea Aime]

On Tue, Mar 6, 2018 at 3:21 PM, Jörg Roth  wrote:

> Hi List,
>
> I’m using geoserver for quite a long time and i am very happy with it.
> This is the first time a have to use the CSW-extension and i ran into a
> couple of issues.
>
> 1.) Enabling CSW in a workspace does not work for me (tested with 2.11.5,
> 2.12.1/2, 2.13-beta)
>
> When i enable CSW in a workspace (e.g. test) and fill out the form, an
> almost correct csv.xml will be created in the data/workspace/test/ but with
> the same -tag as the csw.xml in the data-root.
>
> When i restart geoserver i get an error in the log:
>
> Failed to load the service configuration in directory:
> /var/lib/tomcat8/apps/geoserver-2.11.5/data/workspaces/test with loader
> for interface org.geoserver.csw.CSWInfo
> java.lang.IllegalArgumentException: service with name 'My GeoServer CSW'
> already exists in workspace 'null'
>
> When i stop tomcat and change the -tag of the
> workspace-csw.xml, geoserver starts, does not complain, but CSW is not
> enabled in the workspace even when the workspace-csw.xml shows
> true.
>
> The csw-getCapabilites-request shows the information of the
> data-root-csw.xml and the data-root-global.xml in both requests (root and
> workspace).
>
> The getRecords-Request works fine in the workspace (and the
> workspace-records are hidden in the root-request when workspace is isolated
> in 2.13-beta).
>
>
This looks like a but, I'd suggest to open a ticket for this one, see
https://osgeo-org.atlassian.net/projects/GEOS/summary


> 2.) Maybe related: customizing the MD_Metadata.properties
>
> Is it possible having an own MD_Metadata.properties per workspace or per
> layer?
>

Nope, this is not currently possible, as far as I know at least.
This would be a feature request, see:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


>
> 3.) date-definition in the MD_Metadata.properties
>
> Where exactly do i have to define this metadata-tag? I tried to modify the
> featuretype.xml of the layer but this value will not be mapped and got
> deleted when i modify the layer info.
>
>   
> false
> 2018-03-03
>   
>

I don't know how to answer this one off the top of my head, sorry!
Hopefully someone else will chime in. :-)


>
> 4.) Is it possible to map values from the workspace-settings.xml in
> MD_Metadata.properties.



Same answer as 2)

Cheers
Andrea


==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 

Re: [Geoserver-users] Reorder Layer Groups

[Andrea Aime]

Hi,
I assume you're talking about ordering the layer groups in the capabilities
document?
That is currently not possible. There was a pull request to allow global
ordering some time ago,
but did not pass the first review and the fixes were never implemeneted:
https://github.com/geoserver/geoserver/pull/2125

If someone is interesting in resuming the work, it could get merged, it was
not far off

Cheers
Andrea


On Wed, Mar 7, 2018 at 10:23 PM, Robbins, Amber 
wrote:

> How do I reorder Layer Groups?
>
>
>
> For example:
>
>
>
> *Current Layer Group order:*
>
> Land Layer Group
>
> Business Development Layer Group
>
> Geology Layer Group
>
>
>
> *The Layer Group order I want:*
>
>
>
> Business Development Layer Group
>
> Geology Layer Group
>
> Land Layer Group
>
>
>
> Thank you,
>
>
>
> Amber Robbins
>
>
>
> Senior Geoscience Technician
>
> Castleton Resources, LLC
>
> w. 281-714-2988 <(281)%20714-2988>
>
> c. 307-399-3254 <(307)%20399-3254>
>
> [image: CastletonResourcesLogo]
>
>
>
> __
>
> CONFIDENTIALITY NOTICE: This electronic transmission (including any files
> attached hereto) (this "Communication") contains information that is or may
> be legally privileged, confidential, and exempt from disclosure without our
> express permission in advance. The information is intended only for the use
> of the individual or entity named above. If the reader of this message is
> not the intended recipient or any employee or agent responsible for
> delivering the message to the intended recipient, you are hereby notified
> that any disclosure, dissemination, copying, distribution, or the taking of
> any action in reliance on the contents of this electronic Communication is
> strictly prohibited. If you have received this Communication in error,
> please notify the sender immediately and destroy the transmitted
> information in its entirety.
> __
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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
>
>


-- 

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, 

Re: [Geoserver-users] LDAP group authorisation

[BartO]

I have exactly the same problem using geoserver 2.12.1.
I can connect with the LDAP user, I also see the LDAP groups as geoserver
Roles. But the connection between LDAP users and LDAP groups seems to be
lost.

What I have already found is that it is has something to do with the LDAP
tree I'm using. When adding another tree with nearly the same configuration,
then it works. 

For the moment I did not found a sollution to fix it for the right tree




--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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