A location for TIG, TAG, and any future OneGeology technical group to discuss technical issues surrounding portal, catalogue, service implementations, etc
For documentation, including TIG meeting agendas and minutes see the wiki
A location for TIG, TAG, and any future OneGeology technical group to discuss technical issues surrounding portal, catalogue, service implementations, etc
A location for TIG, TAG, and any future OneGeology technical group to discuss technical issues surrounding portal, catalogue, service implementations, etc
For documentation, including TIG meeting agendas and minutes see the wiki
We have a face-to-face TIG meeting once a year, with the last being in Vancouver 13th June 2018. Where should we spend it this year (around June 2019)?
We like if possible to have it coincide with some other conference or event that we might be attending, so for example in Europe June 2019 there's the OGC TC/PC Meetings - Leuven, Belgium that some of us may be attending... and I also have tentative venue for us to use if we decide on this, but at the moment it would be nice to know if you have any other ideas of where and when we might meet. Meetings to coincide with that you intend to attend etc.
Originally posted as: https://forge.brgm.fr/issues/21899
Start date: | 12/12/2018
Originally posted as: https://forge.brgm.fr/issues/24533
Start date: | 04/11/2019
Originally posted as: https://forge.brgm.fr/issues/23818
Start date: | 28/06/2019
Originally posted as: https://forge.brgm.fr/issues/23882
Start date: | 08/07/2019
Originally posted as: https://forge.brgm.fr/issues/24944
Start date: | 22/01/2020
Target version: 2019.2
If I run search on WFS some known services are not found such as GBR BGS 1:625K BEDROCK AGE (GEOSCIML WFS) or GBR BGS 1:625K BEDROCK LITHOLOGY (GEOSCIML WFS).
Same if I run a search for geosciml, some known services are not found like NOR NGU 1:1M EGDI BEDROCK LITHOLOGY (GeoSciML WFS) (GeoSciML Portrayal) and ATA SVL GNS 1:250k Geological Units (GeoSciML WFS) (GeoSciML Portrayal)
Originally posted as: https://forge.brgm.fr/issues/23876
Start date: | 08/07/2019
Originally posted as: https://forge.brgm.fr/issues/24841
Start date: | 16/12/2019
When saving a WMC file from the portal the backdrop layers don't include a service version, standard layers do.
As per below examples.
<Layer queryable="false" hidden="false">
<Server service="OGC:WMS" version="1.3.0">
<OnlineResource xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink"
xlink:href="https://map.bgs.ac.uk/arcgis/services/AGA/BGS_Groundwater/MapServer/WmsServer?"
/>
</Server>
<Name>NGA_BGS_5M_Geology</Name>
<Title>NGA_BGS_5M_Geology</Title>
<FormatList>
<Format current="true">image/png</Format>
</FormatList>
<StyleList>
<Style current="true">
<Name/>
<Title>Default</Title>
</Style>
</StyleList>
</Layer>
Example: standard data layer giving version
<Layer queryable="false" hidden="false">
<Server service="OGC:WMS">
<OnlineResource xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink"
xlink:href="http://ogc2.bgs.ac.uk/geoserver/OneG/ows"/>
</Server>
<Name>ARCTIC_NASA_BLUEMARBLE</Name>
<Title>ARCTIC_NASA_BLUEMARBLE</Title>
<FormatList>
<Format current="true">image/jpeg</Format>
</FormatList>
<StyleList>
<Style current="true">
<Name/>
<Title>Default</Title>
</Style>
</StyleList>
</Layer>
Example backdrop layer without version
Need to have a version so that external WMC clients can make valid GetMap requests.
Should be version="1.3.0" for ARCTIC_NASA_BLUEMARBLE and ATA_USGS_LIMA layers
@heryk got a notification about adding slack to the technical discussion repository. Were you thinking of setting up a channel? Sounds like a good plan to me.
I've been recently using Docker (https://www.docker.com/) to deploy WMS applications (Geoserver, Mapserver, Mapproxy, etc...). A very powerful tool. Anyone has tried it out?
Originally posted as: https://forge.brgm.fr/issues/24948
Start date: | 23/01/2020
Description
Not sure if this is related to the closed issue https://forge.brgm.fr/issues/22220 (Staging portal using WMS 1.1.1 requests ~ closed as resolved )
It appears the portal has reverted to using WMS version 1.1.1 requests instead of WMS 1.3.0 requests. I think we say now that a WMS version 1.3.0 only service is acceptable now, so this is a major issue.
We used to say that we had to support WMS 1.1.1 and WMS 1.3.0 because of issues with GeoNetwork in harvesting from WMS 1.3.0 services, but that restriction no longer applies.
Just noticed when trying to debug an issue with the Arizona Geological Survey service.
Portal sends a GetCapabilities request like:
Gets a WMS 1.3.0 response.
Then sends WMS 1.1.1 GetMap requests.
I note too that the backdrop is also fetched as a WMS 1.1.1 request.
portrayal request is also not working, but this may be an issue at Arizona end...
Originally posted as: https://forge.brgm.fr/issues/22211
Start date: | 21/01/2019
Originally posted as: https://forge.brgm.fr/issues/24068
Start date: | 14/08/2019
Thinking that something like MapProxy could be useful for proxying services that don't make the OneGeology profile, by adding the keywords etc to the proxy config.
Does anyone know if this is possible?
What options/tools/packages do we have for validating services, to ensure they have expected/appropriate metadata (conform to OneGeology profile) +/- are correctly spatially located, +/- fit particular accreditation levels, +/- are INSPIRE compliant, +/- other compliance issues?
Originally posted as: https://forge.brgm.fr/issues/23873
Start date: | 08/07/2019
Originally posted as: https://forge.brgm.fr/issues/23878
Start date: | 08/07/2019
Related and following on from #34
The GTK Mineral Occurrences service (http://gtkimage.gtk.fi/geoserver/onegeology/ows?) has the appropriate trigger keyword Erml_lite_queryable_geoserver in the MR.MineralOccurrence layer, but no minerals portrayal tools are showing in the OneGeology portal.
This used to work.
Originally posted as: https://forge.brgm.fr/issues/23881
Start date: | 08/07/2019
Originally posted as: https://forge.brgm.fr/issues/22216
Start date: | 22/01/2019
Originally posted as: https://forge.brgm.fr/issues/24069
Start date: | 14/08/2019
Originally posted as: https://forge.brgm.fr/issues/23821
Start date: | 28/06/2019
In the older WMS cookbook Appendix B we describe how to create MapServer CLASS definitions from ArcView legends.
We are still creating content for the new cookbooks, so the purpose for asking the question is really centred around whether it's worth updating / transferring this content to the new cookbooks.
When a map is drawn in polar projection, it "stops" drawing , or fail to draw polygons that crosses the date line (-180 / 180). Seems to happen when the data is stored in 4326 or whatever flat projection.
As well as having cookbooks, it has been suggested that we could use videos to show how to configure services and how to use them.
Does anybody have any good videos that they have found useful for this?
Not just English language.
We could also create them but at the moment just looking for good existing material.
In the older WMS cookbook Appendix C we describe how to create MapServer CLASS definitions from ArcGIS legends using a tool called The MXDtoWMS tool. we provide a link to the ArcGIS Code Sharing page, but the tool no longer seems to exist.
Does anybody still run it, or have a copy of it?
There were versions for ArcGIS 8 and ArcGIS 9, so the next related question might be does anybody still run these versions of ArcGIS, because if the tool only works on these versions but nobody runs them...
As per issue 2 the purpose for asking the question is really centred around whether it's worth updating / transferring this content to the new cookbooks.
Continuing on in the vein of having some documentation in the cookbooks (or even providing a suit of tools... containerization... etc for helping to create and configure services)... Does anybody have any experience of using MapManager to create MapServer map files?
Originally posted as: https://forge.brgm.fr/issues/21255
Start date: | 26/09/2018
Check the current licences of software used by Portal code and agree with BRGM an open source licence to propose to OneGeology operations group for use when Portal code is made available.
The go to documentation link in the portal (Portal v2020.0) is pointing at a deprecated version of the cookbook.
The link should now go to https://onegeology.github.io/documentation/portal.html
Originally https://forge.brgm.fr/issues/23197
Start date: | 17/04/2019
And posted as part of a check on the original variant of #52
Originally posted as https://forge.brgm.fr/issues/22502
Listed Start date: | 13/02/2019 , but has been discussed for some time prior to this
Originally posted as: https://forge.brgm.fr/issues/24989
Start date: | 05/02/2020
Looking yesterday with Arizona Geological Survey (AGS) at the portrayal tool in the portal. AGS services have always worked with the portrayal tool, but now are not. They have moved servers around, so were unsure whether the issue was at their end or an issue with the SLD (or both).
It transpires that the SLD generated has two issues (possibly related). It is not schema valid, and it does not include the CGI terms, only INSPIRE terms.
SLD generated by the portal was:
<sld:StyledLayerDescriptor version="1.0.0" xmlns="http://www.opengis.net/ogc"
xmlns:sld="http://www.opengis.net/sld" xmlns:ogc="http://www.opengis.net/ogc"
xmlns:gml="http://www.opengis.net/gml"
xmlns:gsmlp="http://xmlns.geosciml.org/geosciml-portrayal/2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd">
<sld:NamedLayer>
<sld:Name>US-AZ_AZGS_1M_Geologic_Age</sld:Name>
<sld:UserStyle>
<sld:Name>onegeosld</sld:Name>
<sld:FeatureTypeStyle>
<sld:Rule>
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/carboniferous&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/mississippian&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/serpukhovian&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/tournaisian&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/visean&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/pennsylvanian&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/bashkirian&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/moscovian&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/gzhelian&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>representativeAge_uri</ogc:PropertyName>
<ogc:Literal>http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/kasimovian&lt;/ogc:Literal>
</ogc:PropertyIsEqualTo>
<ogc:Or/>
</ogc:Filter>
<sld:PolygonSymbolizer>
<sld:Fill>
<sld:CssParameter name="fill">#FFD800</sld:CssParameter>
</sld:Fill>
</sld:PolygonSymbolizer>
</sld:Rule>
</sld:FeatureTypeStyle>
</sld:UserStyle>
</sld:NamedLayer>
</sld:StyledLayerDescriptor>
Validation issues are related to the <ogc:Filter>
there should be an <ogc:Or>
at the start of the document In the filter.
I'm guessing that what might be missing is <ogc:Or>
followed by all the CGI URI's (that is a single error causing all issues...
Originally posted as: https://forge.brgm.fr/issues/23877
Start date: | 08/07/2019
Originally posted as: https://forge.brgm.fr/issues/22200
Start date: | 21/01/201
Originally posted as: https://forge.brgm.fr/issues/23871
Start date: | 08/07/2019
We (BGS) have used deegree for WFS, but don't use it regularly. Does anybody else have experience?
The documentation is quite good, but it thinking would be nice to write some additional content in the cookbooks on configuring for the OneGeology profile with INSPIRE support if possible. Could anybody help to write this content?
Originally posted as: https://forge.brgm.fr/issues/22464
Start date: | 11/02/2019
Originally posted as: https://forge.brgm.fr/issues/22214
Start date: | 22/01/2019
According to the docs QGIS Server is:
an open source WMS 1.3, WFS 1.0.0 and WCS 1 1.1.1 implementation that, in addition, implements advanced cartographic features for thematic mapping. The QGIS Server is a FastCGI/CGI (Common Gateway Interface) application written in C++ that works together with a web server (e.g., Apache, Lighttpd). It has Python plugin support allowing for fast and efficient development and deployment of new features. It is funded by the EU projects Orchestra, Sany and the city of Uster in Switzerland.
Has anybody had any experience of setting this up and using it?
Could anybody write (or help to write) cookbook documentation on how to configure it to run OneGeology services, ideally with INSPIRE support?
I had a feeling too that this is quite closely related to MapServer, (does anybody know if this is so?) thinking that possibly could use this to configure MapServer (which has support for more versions of OGC interface standards)
Can we use GeoCat with ArcGIS to configure services for OneGeology
discuss
Originally posted as: https://forge.brgm.fr/issues/22188
Start date: | 18/01/2019
Originally posted as: https://forge.brgm.fr/issues/23879
Start date: | 08/07/2019
Originally posted as: https://forge.brgm.fr/issues/23806
Start date: | 28/06/2019
Hi Nicolas,
Regarding the basemaps dropdown.
The "OneGeology" title isn't very descriptive, could we change to "Aerial with Labels"
Also 4 options seems too many, Road and OSM have a lot of overlap, could I suggest we remove road and only use OSM.
and lastly for the above to work we need to change which OSM tiles we're using. The tiles on the OneGeology portal are significantly different to the maps shown on openstreetmap.com (see attached) please can we update to pull in the tiles from openstreetmap as they display them (this then is of sufficient quality to make the road layer redundant).
Issues and comments relating to latest staging portal release (https://onegeology.brgm-rec.fr/mapClient/)
Please add to below list
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.