03-02-2017 11:46 PM
03-03-2017 03:10 AM
I created a new GP instance and it works if I add a WMS there but in the AdminPortal it doesn’t. (Previously I compiled a workspace in the AdminPortal and then set it to the GP, that’s why it didn’t work.)
So I decided to repair and reconfigure the WebMap with EP06 installer maybe it helps to repair the AdminPortal too, but not. The log level of it is in INFO and doesn’t sign any warn or error during adding WMS.
I attach the gpw file I created in the AdminPortal.
03-03-2017 05:16 AM - edited 03-03-2017 05:21 AM
Thanks Dávid. This looks like a bug in AdminPortal as some things look they have not been updated with EP releases. I can display this GPW in a clean Geospatial Portal instance, but not in AdminPortal.
03-03-2017 05:21 AM
Update - I can display the GPW, ONLY if I display another GPW previously.
Can you please try displaying the attached GPW?
(still not sure what's going on in the AdminPortal)
03-03-2017 05:31 AM
Now the question is from which place does the AdminPortal take this definition. It uses the same CRSConfig file...
03-06-2017 02:53 AM
Thank you, it is solved. The GPW file you attached behaves the same as mine and both contain "axesDirections": [1, 2], order. I changed it manually to [2, 1] as see in your attached picture and so it works. Furthermore I had to delete the WFS quirks from the config file, in this setting they are not necessary.
It seems that in the GPW file only this crsList section takes its settings from the CRSConfig file and it is appropriate.
"axesDirections": [2, 1],
"axesDirections": [1, 2],
"axesDirections": [2, 1],
Only in the maps section misbehaves but who knows why.
Thank you once again,
03-06-2017 02:57 AM
No problem, glad that it helped.
I logged SR/CR for this on behalf of Csongor's account since I couldn't find yours in Siebel / eService.
Let's see what the development will find out.
09-26-2017 06:42 AM
I also have this problem with Portuguese SRS, in AdminPortal. This is very inconvenient as we intend to pass the administration of legend to customers and having to change GPW manually is not an option. The only workaround we have for now is to generate the GPW in a standard Geospatial Portal instance, save it as GPW in User Maps, and load it again in AdminPortal so we can set it for some instance. But is an aditional step that brings even more complexity to the software administration (we also use this to set categories properly as AdminPortal do not allow it, but that is another question).
Is there any update on this problem related SR?