home.social

#geonetwork — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #geonetwork, aggregated by home.social.

fetched live
  1. @pokateo The change from mailing-lists to discourse has been slow and then sudden with @osgeo committees and projects starting to make the switch.

    You are welcome to drop-in discourse.osgeo.org and check it out.

  2. @pokateo The change from mailing-lists to discourse has been slow and then sudden with @osgeo committees and projects starting to make the switch.

    You are welcome to drop-in discourse.osgeo.org and check it out.

    #osgeo #foss4g #geoserver #GeoNetwork #gischat

  3. Helpful examples of how to use Elasticsearch with record data docs.geonetwork-opensource.org

    Thanks to Jose from @geocat for these examples :)

    (helpful for those updating scripts from GeoNetwork 3.12 which reaches end-of-life soon).

  4. Helpful #geonetwork examples of how to use Elasticsearch with record data docs.geonetwork-opensource.org

    Thanks to Jose from @geocat for these examples :)

    (helpful for those updating scripts from GeoNetwork 3.12 which reaches end-of-life soon).

  5. @osgeo upgrade guidance - PR now merged and docs are available: docs.geonetwork-opensource.org

    Although GeoNetwork 4 has been out for some time it was a lot of work to determine which:
    1. Web services had migrated to Elasticserach
    2. Web Services had been dropped (but could be migrated)
    3. Services had been dropped forever (depended on Lucene engine)

    Also the documentation looks good with version selector for 4.4 latest / 4.2 stable

  6. @osgeo #geonetwork upgrade guidance - PR now merged and docs are available: docs.geonetwork-opensource.org

    Although GeoNetwork 4 has been out for some time it was a lot of work to determine which:
    1. Web services had migrated to Elasticserach
    2. Web Services had been dropped (but could be migrated)
    3. Services had been dropped forever (depended on Lucene engine)

    Also the #mkdocs_material documentation looks good with version selector for 4.4 latest / 4.2 stable

  7. Trying for one @osgeo thing a week this year:

    Week 1: CRA statement
    Week 2: Sponsorship statement
    Week 3: 3 --> 4 Upgrade Guidance

    github.com/geonetwork/core-geo

  8. Trying for one @osgeo thing a week this year:

    Week 1: CRA statement
    Week 2: Sponsorship statement
    Week 3: #GeoNetwork 3 --> 4 Upgrade Guidance

    github.com/geonetwork/core-geo

  9. @jcarlson If using set up "harvest" on a daily or weekly schedule to check your webservices and manage layers added/removed.

    As I understand it is halfway between a catalogue and a web feature service; which each record capturing quite detailed information about an individual image (time, sensor, angle, etc...)

  10. @jcarlson If using #geonetwork set up "harvest" on a daily or weekly schedule to check your webservices and manage layers added/removed.

    As I understand it #STAC is halfway between a catalogue and a web feature service; which each record capturing quite detailed information about an individual image (time, sensor, angle, etc...)

  11. @GISLemur @jcarlson Nice! I did a similar approach to generate metadata entries for

    Making use of postgresql description information in the tables to provide a title. The nice part was folks could then use an editor to provide as much (or as little) detail as they wanted.

  12. @GISLemur @jcarlson Nice! I did a similar approach to generate metadata entries for #geonetwork

    Making use of postgresql description information in the tables to provide a title. The nice part was folks could then use an editor to provide as much (or as little) detail as they wanted.

  13. @pokateo

    I think metadata is dreaded as folks miss the point; and elitist technical language is used that obscures the value.

    Keep it simple, use normal words. Here is my recent talk / rant on the subject.

    youtu.be/_ZCcRgyI6yg?si=rxZ38_

  14. @pokateo #gischat

    I think metadata is dreaded as folks miss the point; and elitist technical language is used that obscures the value.

    Keep it simple, use normal words. Here is my recent talk / rant on the subject.

    youtu.be/_ZCcRgyI6yg?si=rxZ38_

    #geonetwork #osgeo #foss4g

  15. @pokateo Checking in to from yyj, and this this week I have wins: 2.24-RC 30-RC replacing
    @opengeospatial
    conflict, mkdocs, and my first module

  16. @pokateo Checking in to #gischat from yyj, and this this week I have wins: #GeoServer 2.24-RC #GeoTools 30-RC replacing
    @opengeospatial
    conflict, #geonetwork mkdocs, and my first #python module

  17. @squidfunk thanks for your work, and excellent documentation. I have been in the process of transitioning a open source project from sphinx-build to material-for-mkdocs.

    Simple pandoc was not going to cut it given all the crazy doc and ref directives in use; so I ended up making a script to scan and fix and pre / post process.

    github.com/jodygarnett/transla

    Are you aware of similar efforts; or should I package this up for wider use.

  18. @squidfunk thanks for your work, and excellent documentation. I have been in the process of transitioning a open source project from sphinx-build to material-for-mkdocs.

    Simple pandoc was not going to cut it given all the crazy doc and ref directives in use; so I ended up making a script to scan and fix and pre / post process.

    github.com/jodygarnett/transla

    Are you aware of similar efforts; or should I package this up for wider use.

    #mkdocs #geonetwork

  19. geOrchestra code sprint on February 7-9 in Rennes, France by @fvanderbiest

    Six @camptocamp developers will participate in the #geOrchestra code sprint in Rennes, France over 3 days at TiLab.

    Our main objectives for this code sprint are to improve the default user experience, increase data discoverability, but also improve the path for new developers of the solution (better integration of #geonetwork microservices, core modularization, etc. ).

    Read more on: camptocamp.com/en/news-events/

    #gischat

  20. 🗞 La #GeoRDP est en ligne depuis vendredi dernier : static.geotribu.fr/rdp/2023/rd

    Une édition particulière car la part des news proposées par des contributeur/ices externes est majoritaire ! Et, franchement, ça fait plaisir donc merci !

    Vous aussi, essayez : contribuer.geotribu.fr/rdp/add

    👥 Contributeur/ices : @Data_Wax, @geojulien, Loïc Bartoletti, Guilhem Allaman, Olivia Guyot et Benoît Blanc

    #Geotribu #veille #géomatique #GeoNetwork #GIS #SIG ODK #OpenStreetMap CESBIO #cybersécurité 🌱 ♾ #GeoNight

  21. 🗞 La #GeoRDP est en ligne depuis vendredi dernier : static.geotribu.fr/rdp/2023/rd

    Une édition particulière car la part des news proposées par des contributeur/ices externes est majoritaire ! Et, franchement, ça fait plaisir donc merci !

    Vous aussi, essayez : contribuer.geotribu.fr/rdp/add

    👥 Contributeur/ices : @Data_Wax, @geojulien, Loïc Bartoletti, Guilhem Allaman, Olivia Guyot et Benoît Blanc

    #Geotribu #veille #géomatique #GeoNetwork #GIS #SIG ODK #OpenStreetMap CESBIO #cybersécurité 🌱 ♾ #GeoNight

  22. geocat.ch has been upgraded to version 4 of #GeoNetwork #opensource. Among the important features:
    - #elasticsearch as indexing engine for efficient indexing of metadata.
    - a new user interface with also a full screen map section
    - a new system architecture allowing the integration of microservices.

    Let's now clean up this brand new version and wait for the next year's developments. We will include a new user interface library to greatly improve metadata editing. #gischat