[Geoserver-users] R: INSPIRE - validator - Error in GetMap_Operations
Hi Dominik, To solve your problems you need to install the INSPIRE plugin and also enable in the WMS settings, the option "Strict CITE compliance". However, this does not solve the problem of the VERSION parameter. Pietro Da: Dominik Schilder via Geoserver-users Inviato: venerdì 16 aprile 2021 12:24 A: geoserver-users@lists.sourceforge.net Oggetto: [Geoserver-users] INSPIRE - validator - Error in GetMap_Operations Dear all, I want to publish some raster layers (WMS) in Geoserver 2.18.0. My goal is to publish these data with an WMS service. The service and the data should meet the INSPIRE- requierements. For the data I'm using the raster mosaic and the inspire extension in geoserver. The layers are already configured. I used the INSPIRE validator (https://inspire.ec.europa.eu/validator) for testing the service. But for testing the GetMap_Operations the validator gives me some errors : - A GetMap was requested without mandatory parameter 'VERSION' and the service did not throw an exception. - A GetMap was requested without mandatory parameter 'CRS' and the service did not throw an exception. - A GetMap was requested without mandatory parameter 'TRANSPARENT' and the service did not throw an exception. - A GetMap was requested without mandatory parameter 'STYLES' and the service did not throw an exception. I think for every parameter there is obviously the same issue. The service does not return an OWS Exception report. Are there any possibilities to fix these issue(s) in geoserver? Any hints or ideas are welcome Best regards Dominik ___ 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] R: WFS GetFeature does not work with field "DATE"
The following keywords don't make problem: - ID, GEOMETRY, TYPE The query on DB is like: SELECT GEOMETRY AS GEOMETRY FROM TABLE The following makes problem: - LEVEL, DATE i have to rename the view fields, but i think is a mistake that some sensible oracle keywords works and other not… If I have an obligation to display the data according to specifications, I can't! For example, Inspire provides for some fields called "LEVEL". Regards -Messaggio originale- Da: Richard Duivenvoorde Inviato: lunedì 3 agosto 2020 20:20 A: andrea.a...@geo-solutions.it; Rahkonen Jukka (MML) Cc: geoserver-users@lists.sourceforge.net Oggetto: Re: [Geoserver-users] WFS GetFeature does not work with field "DATE" Also see the answer of Stefan in the issue Pietro created: https://osgeo-org.atlassian.net/browse/GEOS-9712 Regards, Richard Duivenvoorde On 8/3/20 8:07 PM, Andrea Aime wrote: > Hi Jukka, > having a quick look at the code, indeed the name quoting is explicitly > disabled in Oracle, and it has been since many years (probably since the > version of the Oracle support code). > If memory serves me correctly, Oracle Spatial has some weird naming > limitations on top of the already restrictive Oracle naming > conventions... something like, table and geometry columns must actually be > all uppercase in the queries for anything to work (can't remember exactly). > Cheers > Andrea > > > On Mon, Aug 3, 2020 at 7:41 PM Rahkonen Jukka (MML) > <mailto:jukka.rahko...@maanmittauslaitos.fi>> wrote: > > Hi, > > Does it mean that Oracle NG builds queries as nonquoted and the result is > SELECT DATE FROM TABLE instead of > SELECT "DATE" FROM "TABLE", that would work? > > From the referred Oracle document: > > "This section lists Oracle SQL reserved words. You cannot use Oracle SQL > reserved words as nonquoted identifiers. Quoted identifiers can be reserved > words, although this is not recommended." > > -Jukka Rahkonen- > > -Alkuperäinen viesti- > Lähettäjä: Mark Prins mailto:mc.pr...@gmail.com>> > Lähetetty: maanantai 3. elokuuta 2020 18.01 > Vastaanottaja: geoserver-users@lists.sourceforge.net > <mailto:geoserver-users@lists.sourceforge.net> > Aihe: Re: [Geoserver-users] WFS GetFeature does not work with field "DATE" > > On 03-08-2020 11:00, d'Orio, Pietro wrote: > > If an Oracle NG (JNDI) layer contain a field "DATE" the WFS does not > > work for this layer. > > > > Also other "sensitive" oracle DB tags like "SIZE" or "LOCATION" cause > > the same problem. > > > > A special note: "TYPE" does not cause problems > > TYPE is not in the list: > https://docs.oracle.com/database/121/SQLRF/ap_keywd001.htm#SQLRF55621 > (but neither is LOCATION or SIZE so I'm not sure what is going on there) > If you set up geoserver with geotools developer or debug logging you can see > the generated queries in the log. > > As linked there > > https://docs.oracle.com/database/121/REFRN/GUID-6D03E5B5-A23B-499C-B6BC-A31A12FC6C7D.htm#REFRN30204 > talks about which words vcaanot be used where in Orcla, documented > in V$RESERVED_WORDS in your database (the list can/will vary between > versions) > > - M > > > ___ > 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-an > d-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > <mailto: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 thi
[Geoserver-users] WFS GetFeature does not work with field "DATE"
If an Oracle NG (JNDI) layer contain a field "DATE" the WFS does not work for this layer. Also other "sensitive" oracle DB tags like "SIZE" or "LOCATION" cause the same problem. A special note: "TYPE" does not cause problems Pietro d'Orio ___ 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] Full i18n compatibility
Dear community, GeoServer has now reached such a level of quality that you can't keep going around it: It needs that GeoServer supports 100% i18n. The actual situation is that the only that works is the title used in the SLD: This is the default title English title Titolo in italiano It´s also possible to define localized "Keywords" in the Layer definition. What I expect is to make a call to the getcapabilities / getlegendgraphic / getmap with the parameter &lang=XX and get my document 100% in the language I defined. what's missing: For Layers: * Title * Abstract * Keywords: at the moment is possible to define localized keywords. If I configure DE, EN and generic keyword, by calling the getcapabilities with &lang=DE parameter, I obtain all the keywords (what I'd expect is just DE and generic, without the specific EN keywords) For Styles: * Title (already implemented and works great for the getlegendgraphic) * Abstract * Label (by calling the getmap, with &lang=de: see only the DE labels) I hope I haven't opened a double argument. Best Regards Pietro ___ 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
