-
Notifications
You must be signed in to change notification settings - Fork 9
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
GEUS 1:500k geological map #566
Comments
Paper for dataset: https://geusbulletin.org/index.php/geusb/article/view/4727/10367 It notes:
However, attempting to access the given URL gives a "service unavailable" page (HTTP 503) It also notes:
However, the map does not appear to be there either. There is a "GEUS Geology of Greenland" WMS service available from onegeology but it notes:
We're non-commercial but not for 'personal' use. I tried adding the "GEUS Geology of Greenland" WMS layer in QGIS and found that there is a 1:500,000 layer available, but it does not seem to work. I get "map request failed" warning messages in the log. When attempting to hit the request URL directly in the browser, I get a 404 error w/ message "JSP file [/ows/.jsp] not found" |
A WMS version of the map is available via GEUS: https://data.geus.dk/arcgis/rest/services/Greenland/Geological_map_500k/MapServer/WMTS/1.0.0/WMTSCapabilities.xml However, there does not appear to be a legend (the link to the legend is broken, 404). Moreover, this page notes:
|
There are some vector data available via https://dataverse.geus.dk/dataset.xhtml?persistentId=doi:10.22008/FK2/FWX5ET. The data are stored in an Downloading the dataset requires that the user acknowledge their "Dataset Terms":
This bit seems to suggest that we would be OK redistributing the data:
But does providing the data w/ symbology in a QGIS project file consitute a "new map"?
I'm guessing they are trying to prevent someone from taking the data and publishing it as a "new" geological map without proper attribution. Maybe wouldn't hurt to reach out to GEUS and confirm they're ok with us including the data in QGreenland though. |
Blocked until we contact GEUS |
When we do contact GEUS, we might mention that the license terms are a bit vague. |
I was about to send an email to Niels when I realized that we probably had already asked this question of GEUS before. Indeed, we have! Back in Dev. 2020, we asked for permission to include data from the PROMICE portal and also the 1:500 000 geological map! We never got a definitive answer back, as far as I can tell. I'm going to wait to get in touch with Niels or follow up on the existing email thread ("RE: Permissions follow up to seek GEUS permission for including data within QGreenland") until we chat with Twila since she was the primary point of contact. Here's the email text I was about to send:
|
Lets continue the thread in the QGreenland email. I'll follow up. |
I followed-up with GEUS about this today via QGreenland's email. Hopefully we hear back soon that we can use the data in QGreenland v3! |
If we do not receive permission for direct distribution, this should be a dataset that we highlight as an add-on (like with the ArcticDEM custom Greenland dataset and the ADC QGreenland Data Portal). Want to make sure @alysethurber has this in mind for website update - we do want these few specific add-on/data sources top and center on the "Data" page. |
This won't make it in v3, but we may want to link to the data on our website. |
Actually, we got an email from GEUS ~6 hours ago that clears us to use this dataset! |
The dataset provided via the GEUS dataverse is a zip package containing an Esri Map package ( This map package is a 7zip compressed directory that includes esri-specific metadata and datasets. After unzipping the data, I see two directories ( The geodatabases contain vector layers that appear to be the same for both the
These layers are easy enough to extract and can be opened in QGIS. The main problem is related to symbology. The symbology for these layers is important, and the configuration for it appears to be specific to Esri products. I am not sure yet if we can convert these styles into something with QGIS. Each layer on its own has limited value, and it seems like having them all visualized together is important to interpreting the map For example, features in the The image below shows one such feature highlighted. Other features from this layer can be seen as red lines. I plan to do a little more digging into if we can convert the styles from Esri to something compatible with QGIS, but my instinct right now is that this might be more effort than it's worth. Instead, it may be more reasonable to just add this layer as an online-only resource (https://data.geus.dk/arcgis/rest/services/Greenland/Geological_map_500k/MapServer/). |
Nice sleuthing. I think adding it as an online layer is a good temporary compromise. Maybe in the meantime, this dataset becomes more FAIR and easier to add. |
It's kind of blowing my mind that they build the archived dataset this way. I agree that it's reasonable to do a bit more digging (also just interesting learning) but that online-only may be the final conclusion. When I linked to the site I didn't see an option for viewing with QGIS. Is that something we do via one of the other viewing methods they list prominently (all proprietary :( )? |
Agreed. If we go this route I would probably follow up with GEUS again and explain our plan/reasoning. They request a
My guess is that they developed the map & all of it's symbology in Esri products (ArcGIS), which they host a view of via the web map service I mentioned above. When it came to publishing the data, saving it as a map package was probably just a convenient choice. Unfortunately that means hose of us without an ArcGIS license have to do some extra legwork. I wonder if they could easily publish a raster (e.g., GeoTiff)...maybe it's something we could suggest.
I'm not sure QGIS can read the To access the map service, use the "WMS/WMTS" option in the Data Source Manager and create a new connection using this URL: https://data.geus.dk/arcgis/rest/services/Greenland/Geological_map_500k/MapServer/WMTS/1.0.0/WMTSCapabilities.xml . More detailed instructions on adding a WMS layer from our documentation here. |
At least one tool exists for convering ArcGIS .mapx packages into something compatible with QGIS. It's a tool called slyr, produced by a company called North Road. It has a pricey license at 1200 euro. I strongly prefer to look elsewhere before giving this any serious consideration, but I thought I would take note of it. Funnily, one of the examples they have on their website is a collection of geology related layers! We're not the first ones with this problem. |
I took another look at the data this morning, thinking that we could perhaps just add the polygon layer and symbolize by label. This sort of works, but some polygons do not have all of their attributes set, so the legend is still necessary! Moreover, some polygons have a URL associated with them, but all of the ones I tried do not work (I get a message indicating that the geological unit isn't defined in the GEUS data base). |
PR for adding the layer as online-only: https://github.com/nsidc/qgreenland/pull/725/files I plan to follow-up with GEUS to let them know that we plan to utilize their WMS service. |
Thanks @trey-stafford. In your contact with them, a brief note on what was attempted and the problem we encountered would be good to include. And an inquiry on whether they would expect to update/add other formats at some point. |
This might explain why there are two versions of the geodatabase in the |
Should we keep the existing geological map from the Canadian geological survey? |
I think since the GEUS map will be internet-only, it makes sense to keep the current download geological map layers too. |
One of our contacts at GEUS provided us with |
I tried using the
I upgraded to QGIS 3.32 and the plugin didn't work at all (got a "core dumped" message). The plugin says it works with QGIS >=3.4, so I downgraded to 3.4. The result is mixed. I can apply the style of the The
|
Given these issues, sticking with the WMST online-only layer still seems like the right choice. We can re-open if we learn more or come up with another solution. |
Yes, good call. In responding to GEUS, please let them know of this decision and that we would like notification if/when they make further updates. Of course, do tell them you tried this and relate the issues. |
GEUS provided us with
Note that SLD styles were not provided for the geopoint or annotation layers. Our contact at GEUS noted that the geopoint style in particular was giving them trouble, but that they will let us know once it is resolved. Two of the provided Screenshot of the result below: Compare that to the WMS layer: Assuming we want to add these layers, I'll need to do some more research on what each of these actually represent so that I can put something useful in the 'description'. Maybe GEUS can help us with that! |
Sounds like we're in closer contact now, so that's good! |
Draft PR: #739 |
We plan to stick with the WMS version. The styles as defined work, but causes visualization to be extremely slow. Moreover, we agreed upon review that the layer order and symbolization provided by GEUS are still key to interpretation (e.g., many polygons have NULL descriptions but their symbology still indicates the geological unit type), so a rendered view (e.g., from WMS) makes the most sense. The main drawback is the need for a separate legend that has to be downloaded (pdf) and used alongside the layer. Note that I did just try re-configuring the symbology for the polygon layer to use the "categorization" type using the |
Plus, mentioning any elements that we were successful with (e.g., your experiment with "categorization" type) can help GEUS to provide guidance to other users and continue to improve the data on their end. |
Great find! |
Just sent a reply to our email thread with GEUS. Closing this issue for now! |
Joe M. has a link to some data. It’s apparently really large but we could point users to it.
Someone at GEUS noted making a QGIS compatible version of the dataset from Joe M.
The text was updated successfully, but these errors were encountered: