Re: [Geoserver-users] App-schema mappings not returning data [SEC=UNOFFICIAL]

[Nuno Oliveira]

Hi Michael,
I did a quick read of your mappings and they seem fine to me, this
information is particularly relevant:

*If I remove the rows that are appearing, the problematic rows appear in
the feature.*

I see two possible causes for this problem:

   - Id's collision, GeoServer will consider features with the same ID to
   be repeated.
   - Some weird bug where LIMIT clause is added to the final query sent to
   DB.

Kind regards,
Nuno Oliveira



On Mon, Nov 1, 2021 at 1:59 AM Michael Sexton 
wrote:

> Hi GeoServer users group,
>
>
>
> Having an issue with not returning in a two-level deep feature chain for
> the application schema EarthResourceML.
>
>
>
> Attached are the three mapping files, three source data files, and the
> resultant GML feature.
>
>
>
> The problematics rows in each table are highlighted below, which are not
> appearing in the resultant feature. If I remove the rows that are
> appearing, the problematic rows appear in the feature. So it’s not a
> problem with the data in the rows themselves, but something about the way
> the feature chain is picking up the features.
>
>
>
> Any help would be greatly appreciated.
>
>
>
> RESOURCE_NO
>
> ENO
>
> RESOURCE_ID
>
> RECORD_DATE
>
> ORE
>
> INCLUDESRESERVES
>
> UOM_CODE
>
> UOM_TITLE
>
> UOM_HREF
>
> CATEGORY_TITLE
>
> CATEGORY_HREF
>
> CLASSIFICATIONMETHOD
>
> SOURCEREF_TITLE
>
> SOURCEREF_HREF
>
>
>
> 12223
>
> 339086
>
> 12223.ifr
>
> 4-Mar-10
>
> 1.1
>
> FALSE
>
> Mt
>
> megatonne
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/Mt
>
> inferred mineral resource
>
>
> http://resource.geosciml.org/classifier/cgi/resource-assessment-category/inferred-mineral-resource
>
>
> http://resource.geosciml.org/classifier/cgi/classification-method-used/jorc-code
>
> Meridian Minerals announces Cadjetbut Splay Mineral Resource trebles to
> 1.1Mt on the Lennard Shelf Project in WA
>
> http://www.opengis.net/def/nil/OGC/0/inapplicable
>
>
>
> 14200
>
> 339086
>
> 14200.ifr
>
> 24-Mar-11
>
> 1.6
>
> FALSE
>
> Mt
>
> megatonne
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/Mt
>
> inferred mineral resource
>
>
> http://resource.geosciml.org/classifier/cgi/resource-assessment-category/inferred-mineral-resource
>
>
> http://resource.geosciml.org/classifier/cgi/classification-method-used/jorc-code
>
> Meridian Increases Total Mineral Resource 130% to 17.7Mt in 16 Months at
> Lennard Shelf Project - 24 Mar 2011
>
> http://www.opengis.net/def/nil/OGC/0/inapplicable
>
>
>
>
>
> GRADE_NO
>
> RESOURCE_NO
>
> RESOURCE_ID
>
> GRADE_ID
>
> COMMODITYAMOUNT
>
> COMMODITYAMOUNT_CODE
>
> COMMODITYAMOUNT_TITLE
>
> COMMODITYAMOUNT_HREF
>
> GRADE
>
> GRADE_CODE
>
> GRADE_TITLE
>
> GRADE_HREF
>
> COMMODITY_TITLE
>
> COMMODITY_HREF
>
> 19849
>
> 12223
>
> 12223.ifr
>
> 19849.ifr
>
> 0.094
>
> Mt
>
> megatonne
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/Mt
>
> 8.5
>
> %
>
> percentage
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/percent
>
> lead
>
> http://resource.geosciml.org/classifier/cgi/commodity-code/lead
>
> 19850
>
> 12223
>
> 12223.ifr
>
> 19850.ifr
>
> 0.026
>
> Mt
>
> megatonne
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/Mt
>
> 2.4
>
> %
>
> percentage
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/percent
>
> zinc
>
> http://resource.geosciml.org/classifier/cgi/commodity-code/zinc
>
> 19851
>
> 12223
>
> 12223.ifr
>
> 19851.ifr
>
> 0.017
>
> Kt
>
> kilotonnes
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/kt
>
> 15.7
>
> g-t
>
> grams per tonne
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/g-t
>
> silver
>
> http://resource.geosciml.org/classifier/cgi/commodity-code/silver
>
> 23544
>
> 14200
>
> 14200.ifr
>
> 23544.ifr
>
> 0.032
>
> Mt
>
> megatonne
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/Mt
>
> 2
>
> %
>
> percentage
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/percent
>
> zinc
>
> http://resource.geosciml.org/classifier/cgi/commodity-code/zinc
>
> 23545
>
> 14200
>
> 14200.ifr
>
> 23545.ifr
>
> 0.133
>
> Mt
>
> megatonne
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/Mt
>
> 8.3
>
> %
>
> percentage
>
> http://pid.geoscience.gov.au/def/voc/ga/uom/percent
>
> lead
>
> http://resource.geosciml.org/classifier/cgi/commodity-code/lead
>
>
>
>
>
> 
>   
>
>   **
>  xlink:href="
> http://resource.geosciml.org/classifier/cgi/classification-method-used/jorc-code
> "/>
> 
> 
> 2011-03-23Z
> 
> 
> 
>  xlink:href="
> http://www.opengis.net/def/nil/OGC/0/inapplicable;
> xlink:title="Meridian Increases Total Mineral
> Resource 130% to 17.7Mt in 16 Months at Lennard Shelf Project - 24 Mar 2011"
> />
> 
> 
>  xlink:href="
> http://pid.geoscience.gov.au/def/voc/ga/uom/Mt;
>   

Re: [Geoserver-users] WPS and CORS

[emmexx]

On 11/4/21 8:34 PM, br...@frogmouth.net wrote:
> Exactly what have you done to enable the filters? Can you show the headers 
> for the two different calls (not debugger, but actual output, say from wget).

I followed the manual:

https://docs.geoserver.org/latest/en/user/production/container.html#enable-cors

I uncommented the suggested filters from web.xml
I left url-pattern = *

The following is not from wget but from the raw output of the debugger:

xhr OPTIONS request:

OPTIONS /geoserver/wps HTTP/1.1
Host: mysite2:8080
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101
Firefox/84.0
Accept: */*
Accept-Language: it,en-GB;q=0.8,en;q=0.5,en-US;q=0.3
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type
Referer: http://mysite/mypage
Origin: http://mysite
DNT: 1
Connection: keep-alive
Cache-Control: max-age=0

Response:

HTTP/1.1 403 Forbidden
Server: Apache-Coyote/1.1
Content-Type: text/plain
Content-Length: 0
Date: Thu, 04 Nov 2021 21:53:15 GMT

This call is followed (it is listed in the debugger after the previous
one) by the following:

jquery xhr POST request:

POST /geoserver/wps undefined
Host: mysite2:8080
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101
Firefox/84.0
Accept: application/xml, text/xml, */*; q=0.01
Accept-Language: it,en-GB;q=0.8,en;q=0.5,en-US;q=0.3
Accept-Encoding: gzip, deflate
Content-Type: text/xml
Content-Length: 1470
Origin: http://mysite
DNT: 1
Connection: keep-alive
Referer: http://mysite/mypage

If that is not useful I'll try with wget.

maxx


___
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] Requesting app-schema by featureID on Oracle returns error [SEC=UNOFFICIAL]

[Nuno Oliveira]

Hi Michael,
that error seems to imply that the parameters of the prepared
statement sent to the database are not correctly set.
I would need to check the GeoServer logs in DEBUG level to see the SQL
queries sent to Oracle to understand what's happening.

The only unusual aspect of your WFS request (at least for me) is the
multiple dots on the type name.

Kind regards,
Nuno Oliveira



On Mon, Nov 1, 2021 at 1:16 AM Michael Sexton 
wrote:

> Hi GeoServer community
>
>
>
> When I try to make a feature ID request to GeoServer I get the following
> error
>
>
>
>
> http://localhost:8080/er/ows?service=WFS=2.0.0=GetFeature=er%3AMineralOccurrence=gml32=ga.er.mineraloccurrence.339086
>
>
>
>
>
> <*ows:Exception* exceptionCode="NoApplicableCode">
>
> <*ows:ExceptionText*>
>
> *java.lang.RuntimeException: java.io.IOExceptionjava.io.IOExceptionMissing
> IN or OUT parameter at index:: 1*
>
> 
>
> 
>
>
>
> However a full request limited to count=1 returns the feature
>
>
>
>
> http://localhost:8080/er/ows?service=WFS=2.0.0=GetFeature=er%3AMineralOccurrence=gml32=1
>
>
>
> Database is Oracle, GeoServer version is 2.19.2
>
>
>
> Thanks
>
>
>
> *Michael Sexton *
>
>
>
> Lockdown hours
>
> Monday 9am – 5pm
>
> Tuesday-Friday 12:30pm - 6pm
>
>
> Data Analyst  |  MEGIS
>
> Minerals Energy Groundwater  *|*  *GEOSCIENCE AUSTRALIA*
>
> *__**__*
>
> Phone:  +61 2 6249 9262Fax:  +61 2 6249 
>
> Email:  michael.sex...@ga.gov.auWeb:  www.ga.gov.au
>
> Cnr Jerrabomberra Avenue and Hindmarsh Drive Symonston ACT 2609
>
> GPO Box 378 Canberra ACT 2601 Australia
>
> *Applying geoscience to Australia’s most important challenges*
>
>
>
> Geoscience Australia Disclaimer: This e-mail (and files transmitted with
> it) is intended only for the person or entity to which it is addressed. If
> you are not the intended recipient, then you have received this e-mail by
> mistake and any use, dissemination, forwarding, printing or copying of this
> e-mail and its file attachments is prohibited. The security of emails
> transmitted cannot be guaranteed; by forwarding or replying to this email,
> you acknowledge and accept these risks.
> ___
> 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,

Nuno Oliveira

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Technical Lead / Project Manager


GeoSolutions Group
phone: +39 0584 962313
fax:  +39 0584 1660272

https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
---


Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.
___
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] WPS and CORS

[bradh]

CORS is on the container, not on geoserver. 

Exactly what have you done to enable the filters? Can you show the headers for 
the two different calls (not debugger, but actual output, say from wget).

Brad




___
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] WPS and CORS

[Olivier Gagnon]

Hi,

For "header ‘Access-Control-Allow-Origin’ missing",  confirm that the header is 
actually present.

Also try with * instead of a specific domain to see if it works. You'll be able 
to set/find a specific value afterwards.

Hope this helps. Good luck !


Envoyé à partir d’Outlook


De : emmexx 
Envoyé : 4 novembre 2021 12:13
À : geoserver-users@lists.sourceforge.net 

Objet : [Geoserver-users] WPS and CORS

In one web application I use a call to WPS. The call worked ok on an old
instance of geoserver 2.8.1 where I had added an external library file
and some configuration in web.xml.

On a test server I'm using 2.19.0 where, from my understanding, CORS is
already there and you only need to enable the filters in web.xml.

I enabled the filters and restarted tomcat and I suppose CORS is working
(a ows call that gave a cors error before enabling the filters is now
working). But the calls to wps give a Cors error:

(Firefox debugger output)

XHR OPTIONS http://vmysite:8080/geoserver/wps CORS Missing Allow Origin

Cross-Origin Request Blocked: The Same Origin Policy disallows reading
the remote resource at http://mysite:8080/geoserver/wps. (Reason: CORS
header ‘Access-Control-Allow-Origin’ missing).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading
the remote resource at http://mysite:8080/geoserver/wps. (Reason: CORS
request did not succeed).

What can I check to solve the problem?

Thank you
maxx


___
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] WPS and CORS

[emmexx]

In one web application I use a call to WPS. The call worked ok on an old
instance of geoserver 2.8.1 where I had added an external library file
and some configuration in web.xml.

On a test server I'm using 2.19.0 where, from my understanding, CORS is
already there and you only need to enable the filters in web.xml.

I enabled the filters and restarted tomcat and I suppose CORS is working
(a ows call that gave a cors error before enabling the filters is now
working). But the calls to wps give a Cors error:

(Firefox debugger output)

XHR OPTIONS http://vmysite:8080/geoserver/wps CORS Missing Allow Origin

Cross-Origin Request Blocked: The Same Origin Policy disallows reading
the remote resource at http://mysite:8080/geoserver/wps. (Reason: CORS
header ‘Access-Control-Allow-Origin’ missing).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading
the remote resource at http://mysite:8080/geoserver/wps. (Reason: CORS
request did not succeed).

What can I check to solve the problem?

Thank you
maxx


___
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] Translation workflow improvement

[Rahkonen Jukka (MML)]

Hi,

As far as I know in the Java property files the special characters must be 
written with Unicode strings like here 
https://github.com/openjump-gis/openjump/blob/main/src/language/jump_de.properties
 or here 
https://github.com/openjump-gis/openjump/blob/main/src/language/jump_fr.properties.

-Jukka Rahkonen-

Lähettäjä: Alexandre Gacon 
Lähetetty: torstai 4. marraskuuta 2021 16.38
Vastaanottaja: geoserver-users 
Aihe: [Geoserver-users] Translation workflow improvement

Hi,

After the recent debate on the translation of GeoServer, I have spent some time 
setting up a small project to see how the transifex-github integration works.

First, I have created a fork of the GeoServer repo on my own GitHub account and 
created a new branch named `test_transifex` 
(https://github.com/AlexGacon/geoserver/tree/test_transifex).

Then, I have activated the transifex-github integration between my GitHub 
account and the GeoServer Transifex project (to be removed and replaced later 
if we continue this way).

I have also created a new project in Transifex to avoid polluting the existing 
work of people working on translation 
(https://www.transifex.com/GeoServer/geoservertestgithub/dashboard/).

I have initiated my project with the property file of web/wms 
(https://github.com/AlexGacon/geoserver/blob/test_transifex/src/web/wms/src/main/resources/GeoServerApplication.properties),
 with a manual upload.

The next step was to upload some existing translations from transifex in 
language not available in GitHub to check later the behavior of the integration 
in this case.

After activation of the integration for my transifex project:
- The main property file is synchronized on Transifex with the content from 
GitHub
- The languages available on GitHub are visible on Transifex with the 
translation from GitHub
- The imported languages are still visible on Transifex

After manual sync from Transifex to GitHub, PRs were created in GitHub for each 
new language.

As a final test, I updated in Transifex the GitHub French translation (54% 
coverage) with the one available in Transifex (more than 85% coverage), by 
downloading the translation file and then uploading it in the new transifex 
project. After manual sync request, a PR is created in GitHub for the new 
language (https://github.com/AlexGacon/geoserver/pull/7) : the diff result is 
not very clear (some lines are marked as removed and added whereas the content 
is the same).

Is it normal that for some languages you have unicode encoded characters ? (for 
example in Russian).

The main drawback on the configuration side of transifex is to have to 
configure all the different property files we want to translate and then upload 
the translations we want to retrieve from Transifex.

Regards

--
Alexandre Gacon
___
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] Translation workflow improvement

[Ian Turton]

On Thu, 4 Nov 2021 at 14:40, Alexandre Gacon 
wrote:

> Hi,
>
> As a final test, I updated in Transifex the GitHub French translation (54%
> coverage) with the one available in Transifex (more than 85% coverage), by
> downloading the translation file and then uploading it in the new transifex
> project. After manual sync request, a PR is created in GitHub for the new
> language (https://github.com/AlexGacon/geoserver/pull/7) : the diff
> result is not very clear (some lines are marked as removed and added
> whereas the content is the same).
>
>
That is most likely a mismatch between tabs and spaces in the two files.

Ian
___
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] Translation workflow improvement

[Alexandre Gacon]

Hi,

After the recent debate on the translation of GeoServer, I have spent some
time setting up a small project to see how the transifex-github integration
works.

First, I have created a fork of the GeoServer repo on my own GitHub account
and created a new branch named `test_transifex` (
https://github.com/AlexGacon/geoserver/tree/test_transifex).

Then, I have activated the transifex-github integration between my GitHub
account and the GeoServer Transifex project (to be removed and replaced
later if we continue this way).

I have also created a new project in Transifex to avoid polluting the
existing work of people working on translation (
https://www.transifex.com/GeoServer/geoservertestgithub/dashboard/).

I have initiated my project with the property file of web/wms (
https://github.com/AlexGacon/geoserver/blob/test_transifex/src/web/wms/src/main/resources/GeoServerApplication.properties),
with a manual upload.

The next step was to upload some existing translations from transifex in
language not available in GitHub to check later the behavior of the
integration in this case.

After activation of the integration for my transifex project:
- The main property file is synchronized on Transifex with the content from
GitHub
- The languages available on GitHub are visible on Transifex with the
translation from GitHub
- The imported languages are still visible on Transifex

After manual sync from Transifex to GitHub, PRs were created in GitHub for
each new language.

As a final test, I updated in Transifex the GitHub French translation (54%
coverage) with the one available in Transifex (more than 85% coverage), by
downloading the translation file and then uploading it in the new transifex
project. After manual sync request, a PR is created in GitHub for the new
language (https://github.com/AlexGacon/geoserver/pull/7) : the diff result
is not very clear (some lines are marked as removed and added whereas the
content is the same).

Is it normal that for some languages you have unicode encoded characters ?
(for example in Russian).

The main drawback on the configuration side of transifex is to have to
configure all the different property files we want to translate and then
upload the translations we want to retrieve from Transifex.

Regards

-- 
Alexandre Gacon
___
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] Problem with encoding of supported language in Geoserver 2.20.0 INSPIRE extension

[Elena Grigoriou]

Hi all,

I am using the INSPIRE extension with Geoserver 2.20.0, to provide INSPIRE
services. I am testing the implementation with the INSPIRE validator (the
one provided by JRC along with a local installation).

I would like to know if anyone has noticed problematic behavior, as regards
the encoding of other supported languages.

Bellow I am describing the problem I noticed:

*Correct INSPIRE extended caps schema (TechnicalGuidance_ViewServices_v3.0
)*




http://discoveryService 

<
inspire_common:MediaType>application/vnd.ogc.csw….



dut


eng



dut



   1. *same default and supported language in wms INSPIRE extension
   configuration *

When the default and other supported language is the same, the capabilities
document omits the element
/../inspire_vs:ExtendedCapabilities/inspire_common:SupportedLanguages/inspire_common:SupportedLanguage.
Since the element is not mandatory, the INSPIRE validation is successful
(at least as regards the schema validation).

[image: image]

[image: image]


   1. *no other supported language*
   When no other supported language is selected, the element
   
/../inspire_vs:ExtendedCapabilities/inspire_common:SupportedLanguages/inspire_common:SupportedLanguage
   is present in the capabilities document but it is not correctly encoded.

[image: image]


[image: image]


The child element
/../inspire_vs:ExtendedCapabilities/inspire_common:SupportedLanguages/inspire_common:SupportedLanguage/inspire_common:Language
is missing so the schema validation fails.

The INSPIRE validator returns the following message:

*Schema not valid: [org.xml.sax.SAXException: Fatal error:
org.xml.sax.SAXParseException; lineNumber: 110; columnNumber: 48;
cvc-complex-type.2.4.b: The content of element
'inspire_common:SupportedLanguage' is not complete. One of
'{"http://inspire.ec.europa.eu/schemas/common/1.0
":Language}' is expected.
Response did not validate against schema
'http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd'
.]*

   1. *different default and other supported languages*
   The desired configuration in our case is to provide different default
   and supported languages, using the i18n configuration for the
   internationalization of the capabilities response.

[image: image]

When this configuration is present, the capabilities response is again not
correctly according to the INSPIRE validator.

[image: image]


The relevant test fails for the schema validation. The error is
*Schema not valid: [org.xml.sax.SAXException: Fatal error:
org.xml.sax.SAXParseException; lineNumber: 110; columnNumber: 85;
cvc-complex-type.2.3: Element 'inspire_common:SupportedLanguage' cannot
have character [children], because the type's content type is element-only.
Response did not validate against schema 'http://inspire.ec.europa.eu/
*

Note #1 : The i18n
configuration does not affect geoserver’s behavior regarding the inspire
extended caps.
Note #2 : The above
testing was made for the following virtual wms
http://beta.geoportal.ypen.gr/geoserver/aqd-wms/ows?service=wms=1.3.0=GetCapabilities

Thanx,

Elena
___
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