Hi Apex team, we are trying to push some changes to the config.json file of the Geospatial Explorer through the github repository. The commit was done, but the geospatial explorer was not updated yet. Is it a matter of time or did we miss any steps? thanks.
Hi @salazar ,
Thank you for reaching out. Can you confirm that you are pushing changes for the eo4cm geospatial explorer instance? If that is the case, I would be expecting an update to happen to the following configuration file: apex_geospatial_explorer_configs/eo4cm/config.json at main · ESA-APEx/apex_geospatial_explorer_configs · GitHub. However, looking at this file, it hasn’t changed since 7 months.
Can you share with us the steps you took to pushing your changes?
Hi Bram,
Yes, that is the case. I did commit the changes yesterday, and on Monday. Ok, I see now that I did not create the pull request from the last update yesterday.
The steps where: edit config.json > commit changes > create pull request.
What I can see in the Pull Request window is this
Let me know if any other info is needed, and thanks for the support.
Thank you for the quick response @salazar . I have merged the latest pull request so that the changes end up on the main branch. This is needed to ensure the changes are applied to the GE. For future use, you can also directly apply your changes onto the main branch.
I also noticed the previous PR just now. I guess that one can be removed?
Thanks for the reply. I already closed the previous pulled request. And noted for next updates.
What I can see now in the live GE is that:
- some layers are not visible: these layers have no data, so maybe it is because of that.
- when zooming to one layer, the location goes somewhere else, this happens to all layers.
- point layers are not visible, only polygons.
- descriptions do not recognize bold option for text.
I attach the json file we uploaded so you can also take a look if there is something wrong with it. We run the health check and there was no warning, besides the one that 3 layers are empty, which we know about it.
Thanks for the support again!
config_20261027_0916.json (18.3 KB)
Great, thank you @salazar. I see that the EO4CM is running on an older version than the one used to build the config. I’m updating the GE instance which should ensure that the live version matches with what you see in the config builder. I’ll keep you posted.
@salazar - the EO4CM is now up-to-date (v4.2.1). Can you check if the config is now working similar to the one configured in the Config Builder?
@bram.jansen, now it is working.
We will check more in deep and will get back to you if anything.
Thanks for the help!
Hi @bram.janssen, I tried to make an update to the config.json of the GE directly to main, but I got this message. Please let me know if there is some step missing from our side. Thank you in advance.
Hi @salazar, I have invited you to join the EO4CM organization. Let me know if you haven’t received anything.
In the meantime, I have merged your PR already.
Hi @bram.janssen. thanks, i received the invitation and joined already.