by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 09 09:33
    SergSm commented #89
  • May 08 15:02
    dersteppenwolf commented #231
  • May 06 09:55
    inakidiazdecerio starred geopython/GeoHealthCheck
  • Apr 26 12:55

    tomkralidis on 133-retry-on-fail

    (compare)

  • Apr 26 12:51
    justb4 commented #319
  • Apr 26 12:51

    justb4 on master

    Fix for #133 use requests Sessi… (compare)

  • Apr 26 12:51
    justb4 closed #319
  • Apr 26 11:48
    justb4 commented #318
  • Apr 26 11:33
    justb4 milestoned #320
  • Apr 26 11:33
    justb4 labeled #320
  • Apr 26 11:33
    justb4 opened #320
  • Apr 26 11:13
    justb4 synchronize #319
  • Apr 26 11:13

    justb4 on 133-retry-on-fail

    #318 revert gunicorn back to ve… Merge remote-tracking branch 'o… (compare)

  • Apr 26 11:00

    justb4 on master

    #318 revert gunicorn back to ve… (compare)

  • Apr 25 19:01
    justb4 commented #318
  • Apr 25 15:10
    justb4 synchronize #319
  • Apr 25 15:10

    justb4 on 133-retry-on-fail

    #133 use requests Session objec… (compare)

  • Apr 25 15:08
    justb4 review_requested #319
  • Apr 25 15:08
    justb4 assigned #319
  • Apr 25 15:08
    justb4 review_requested #319
Tom Kralidis
@tomkralidis
ok good idea. I say remove paver since users can always use a previous version of GHC that uses Paver. Given we are pre 1.0 we are not bound to supporting a stable branch.
re: CLI name. I imagine still calling it ghc is risky enough? GeoHealthCheck doesn’t bother me too much but not sure about others. @justb4 / @archaeogeek ?
Rob van Loon
@borrob
It doesn't bother me either, but I'm a bit hesitant with the capitals
Tom Kralidis
@tomkralidis
true, not very UNIX-y
Just van den Broecke
@justb4

re: CLI name. I imagine still calling it ghc is risky enough? GeoHealthCheck doesn’t bother me too much but not sure about others. @justb4 / @archaeogeek ?

Yes ghc is Haskell-related. Always short commands and lowercase on Unix (he, I worked for the company that invented ls and cd, and C!), hence my suggestion for geohc. (Still need to go through PR & comments, but this was easy to answer).

Tom Kralidis
@tomkralidis
sigh, ok then. geohc it is.
Tom Kralidis
@tomkralidis
@borrob / @justb4 FYI heads up on next OWSLib release: geopython/OWSLib#641
Just van den Broecke
@justb4
@tomkralidis yes, we're - @borrob - following closely, e.g. geopython/GeoHealthCheck#312.
Rob van Loon
@borrob
There is an error popping on when running the resource tests of GHC with respect to pygeoapi. It does not validate the OpenAPI Compliance with this error:
GeoHealthCheck.probe - INFO - Result: success=False msg=Validate OpenAPI Compliance:HTTP Error 404: Not Found
I didn't dive into this yet, but was there a change with the specs or pygeoapi, or is this a big of GHC ?
Rob van Loon
@borrob
It also fails in the current master branch
Just van den Broecke
@justb4
Finally tracked it down I think: read here: opengeospatial/wps-rest-binding#63 , thus looks like no GHC nor pygeoapi error...
Tom Kralidis
@tomkralidis
marinevliz
@marinevliz
Hi there, we have installed GeoHealthCheck in a docker but are running in to issues with bootstrap.min.css it is blocking from loading css on the page (0 rules processed)
here is a screenshot of the issue
Rob van Loon
@borrob
Hi @marinevliz, did you build a docker image yourself, or did you take it from the docker hub?
marinevliz
@marinevliz
Hi @borrob I used the docker hub.
Just van den Broecke
@justb4
we need to see a screenshot of your "Network" tab and your networking/proxy setup. Looks like a Proxy-config or subpath issue.
Rob van Loon
@borrob
@marinevliz All the other static files (like sb-admin-2.css, font-awesome, leaflet.js, ...) work fine? Can you right-click on file in the network-tab, and choose "open in new tab". Does it load then?
marinevliz
@marinevliz
right click and open in new tab in the network tab gives met this: https://imgur.com/4dYcyE1
Here is the network tab: https://imgur.com/5iEX0Qa
Proxy settings: https://imgur.com/4vtoQOr
its weird if i refresh it works, if i refresh again it breaks again
Rob van Loon
@borrob
Well, the first screen shot shows the file is actually there and that you are able to access it. That would suggest all docker and proxy settings are fine. I don't understand the refreshing behaviour. Could that be a caching issue?
marinevliz
@marinevliz
Could be, I can only replicate it on windows 7 machines using chrome or firefox
Rob van Loon
@borrob
Sorry, I can't really help you with windows machines.
Jo Cook
@archaeogeek
Hi there, I have a question about using geohealthcheck with docker, I'm not sure if it's an issue or if my understanding is at fault. My problem is that if I pass a SCRIPT_NAME environment variable with the docker run command, whatever path I include seems to get used twice. My run command is: docker run -d --name ghc_web -p 8083:80 -e SCRIPT_NAME=foo -v ghc_sqlitedb:/GeoHealthCheck/DB geopython/geohealthcheck:latest
... but then when I load the page at http://localhost:8083/foo then all the references in the page are to http://localhost:8083/foo/foo/?lang=en
If I don't include a SCRIPT_NAME variable then it loads as expected at http://localhost:8083, but unfortunately I need it to run in a sub directory
is this a bug or have I missed something in my understanding of how this should be working?
Just van den Broecke
@justb4
Well, first of all SCRIPT_NAME is meant for the case where GHC is run behind a proxy like Apache or Traefik which you probably intend, though it should work in isolation as well. I remember this question came up before, and you contributed a nice piece of documentation for that case: https://docs.geohealthcheck.org/en/latest/install.html#running-under-a-sub-path . Is it maybe you forgot a slash i.e. /foo i.s.o. foo?
Jo Cook
@archaeogeek
@justb4 this will be run behind nginx, and that's where I first hit the problem
I can't get the nginx config to work (using my documentation from earlier :-) ) because it is creating the nested sub-directory. I have an older version (0.6 ish) working outside of docker with gunicorn and supervisord and that is working just fine and the nginx config ought to be the same
Just van den Broecke
@justb4
is nginx also running in Docker? With docker-compose? Then the Docker networking (hostnames/ports) is all internal.
Jo Cook
@archaeogeek
no, nginx is running externally (on the same server but outside of docker). It can "see" geohealthcheck and get to the index page but then the links are all broken
but... surely it should work in isolation (ignoring nginx) so adding a script name as an environment variable should not create the nested sub directory- it should just create one?
Just van den Broecke
@justb4
and you've set it to /foo? There is no directory, it is just a sub-path.
Jo Cook
@archaeogeek
If I set -e SCRIPT_NAME=foo then the URLs are of the form http://localhost:8083/foo/foo/?lang=en when they should presumably be of the form http://localhost:8083/foo/?lang=en
ah- so docker run -d --name ghc_web -p 8083:80 -e SCRIPT_NAME=/foo -v ghc_sqlitedb:/GeoHealthCheck/DB geopython/geohealthcheck:latest seems to work
I'll try that in my server environment
Jo Cook
@archaeogeek
Yes! that's working just fine. I might add that to the documentation so that others don't go round in circles like I did- thanks for your help @justb4
Just van den Broecke
@justb4
welcome!
Maxime Audet-Roberge
@audetrobergem
Good day, I recently install GeoHealthCheck and I am in the process of adding resources. I have an error when I try to add probes to a WFS resource. For example, the probe WFS GetFeature in BBOX for ALL FeatureTypes give me an ‘Error getting Probe form for GeoHealthCheck.plugins.probe.wfs.WfsGetFeatureBboxAll’. The log error message says: ‘UnboundLocalError: local variable 'feature_type_entry' referenced before assignment’ for ‘crs_list = feature_type_entry.crsOptions’. I am using 0.8.dev0. Someone has an idea why I have this message? Thanks a lot!
Just van den Broecke
@justb4
Hmm, sounds like an old bug. Have you tried the latest master version?
Maxime Audet-Roberge
@audetrobergem
I think it is the latest master version, I installed it 2 weeks ago from git.
Just van den Broecke
@justb4
Ok, I cannot reproduce on de demo.geohealthcheck.org site (runs latest master) using a public WFS from the Dutch SDI: http://geodata.nationaalgeoregister.nl/bag/wfs . But I can see where it happens in the code. There a random feature type entry is fetched but it is appearantly empty (code should be more defensive though). I see two possible causes: 1) your WFS provides different options/encodings as e.g. the one above. Or 2) a mismatch with the OWSLib version you are using. So can you give the WFS URL you are using? And the OWSLib version?
Maxime Audet-Roberge
@audetrobergem
I use OWSLib version 0.17.1. The WFS I use is password protected, there are no layers that can be accessed without being logged in. Is it possible that crs_list is done on an empty WFS (before authentication is performed)? I tried the public WFS from the Dutch SDI and it worked on my instance.
Just van den Broecke
@justb4
image.png
OWSLib 0.17.1 is ok (same as used on demo). The auth should not be the problem. All info is pared from the Capabilities doc, guess the Capabilities Probe works ok. As the public WFS URL works, there is something in the capabilities doc different. For one thing: I see that the WFS Probe fetches using WFS 1.1.0, could that be a problem (e.g. only 2.0.0 is supported). You may want to look into the Caps doc, it should read like:
Maxime Audet-Roberge
@audetrobergem
The general structure of the GetCapabilities document is the same. However, I see a difference in the CRS. There are in my file 2 x ':' between EPSG and the code when there's only one in the public WFS from the Dutch SDI Caps. For example, '<DefaultCRS>urn:ogc:def:crs:EPSG::4326</DefaultCRS>'. I use GeoServer to publish data.