Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with a layer of the physics server #158

Closed
maelle opened this issue Feb 28, 2024 · 6 comments · Fixed by #159
Closed

Problem with a layer of the physics server #158

maelle opened this issue Feb 28, 2024 · 6 comments · Fixed by #159
Labels
bug Something isn't working services

Comments

@maelle
Copy link
Collaborator

maelle commented Feb 28, 2024

@salvafern @bart-v is this a known problem?

The "EMODnet:EP_PLATFORMS_MO_ATLAS" layer seems somehow problematic.

wfs <- EMODnetWFS::emodnet_init_wfs_client(service = "physics")
#> Loading ISO 19139 XML schemas...
#> Loading ISO 19115 codelists...
#> ✔ WFS client created successfully
#> ℹ Service: "https://prod-geoserver.emodnet-physics.eu/geoserver/ows"
#> ℹ Version: "2.0.0"
EMODnetWFS::emodnet_get_layer_info(wfs, layers = "EMODnet:EP_PLATFORMS_MO_ATLAS")
#> Error in `purrr::map_chr()`:
#> ℹ In index: 14.
#> Caused by error in `data.frame()`:
#> ! arguments imply differing number of rows: 1, 0
capabilities <- wfs$getCapabilities()
capabilities$getFeatureTypes()[[14]]$getName()
#> [1] "EMODnet:EP_PLATFORMS_MO_ATLAS"
capabilities$getFeatureTypes()[[14]]$getGeometryType()
#> NULL
capabilities$getFeatureTypes()[[14]]$getDescription(pretty = TRUE)
#> Error in data.frame(name = element$getName(), type = element$getType(), : arguments imply differing number of rows: 1, 0

Created on 2024-02-28 with reprex v2.1.0

@maelle maelle added bug Something isn't working services labels Feb 28, 2024
@bart-v
Copy link

bart-v commented Feb 28, 2024

Looks like arguments imply differing number of rows: 1, 0 is an R issue, and not an OGC problem?

@maelle
Copy link
Collaborator Author

maelle commented Feb 28, 2024

but it might be due to this layer being different from the others?

@maelle
Copy link
Collaborator Author

maelle commented Feb 28, 2024

I do wonder whether having a NULL Geometry type is something that is wrong on the server side or on ows4r side. I'll ask there.

@maelle
Copy link
Collaborator Author

maelle commented Feb 28, 2024

eblondel/ows4R#125

@bart-v
Copy link

bart-v commented Feb 28, 2024

If there is no geometry, then there is no layer/map, so I doubt it...

@maelle
Copy link
Collaborator Author

maelle commented Feb 28, 2024

ok, but I do wonder why we didn't run into this before. I'll make a PR with a workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working services
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants