home.social

#fielddata β€” Public Fediverse posts

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

  1. Airbus Partners with GINA Software to integrate emergency response modules

    Airbus Defence and Space has signed a Memorandum of Understanding (MoU) with GINA Software to integrate mission-critical modules…
    #Netherlands #Nederland #NL #Europe #Europa #EU #Airbus #Collaboration #coordination #dataintegration #fielddata #GINASoftware #globalleader #intlbm #MiddleEast #mou #Partnership #publicsafety
    europesays.com/netherlands/968

  2. 🎯 Smart photo stamping in QField 3.7!

    Expression-driven templates auto-stamp GPS coordinates, user info & custom data. Every photo tells the full story! πŸ“ŠπŸ“Έ

    opengis.ch/2025/08/04/qfield-3

  3. 🎯 Smart photo stamping in QField 3.7!

    Expression-driven templates auto-stamp GPS coordinates, user info & custom data. Every photo tells the full story! πŸ“ŠπŸ“Έ

    #QField #FieldData

    opengis.ch/2025/08/04/qfield-3

  4. 🎯 Smart photo stamping in QField 3.7!

    Expression-driven templates auto-stamp GPS coordinates, user info & custom data. Every photo tells the full story! πŸ“ŠπŸ“Έ

    #QField #FieldData

    opengis.ch/2025/08/04/qfield-3

  5. 🎯 Smart photo stamping in QField 3.7!

    Expression-driven templates auto-stamp GPS coordinates, user info & custom data. Every photo tells the full story! πŸ“ŠπŸ“Έ

    #QField #FieldData

    opengis.ch/2025/08/04/qfield-3

  6. 🎯 Smart photo stamping in QField 3.7!

    Expression-driven templates auto-stamp GPS coordinates, user info & custom data. Every photo tells the full story! πŸ“ŠπŸ“Έ

    #QField #FieldData

    opengis.ch/2025/08/04/qfield-3

  7. πŸ“„ New Manuscript published

    "Collaborative creation and management of rich FAIR metadata: Two case studies from robotics field research", by Christian Backe, Veit Briken, Atefeh Gooran Orimi, Rayen Hamlaoui, Malte Wirkus, Bilal Wehbe, and Frank Kirchner

    πŸ”— inggrid.org/article/id/4296/

    #ResearchDataManagement #DataLifecycle #Metadata #FieldData #FAIR #Robotics

  8. πŸ“„ New Manuscript published

    "Collaborative creation and management of rich FAIR metadata: Two case studies from robotics field research", by Christian Backe, Veit Briken, Atefeh Gooran Orimi, Rayen Hamlaoui, Malte Wirkus, Bilal Wehbe, and Frank Kirchner

    πŸ”— inggrid.org/article/id/4296/

    #ResearchDataManagement #DataLifecycle #Metadata #FieldData #FAIR #Robotics

  9. πŸ“„ New Manuscript published

    "Collaborative creation and management of rich FAIR metadata: Two case studies from robotics field research", by Christian Backe, Veit Briken, Atefeh Gooran Orimi, Rayen Hamlaoui, Malte Wirkus, Bilal Wehbe, and Frank Kirchner

    πŸ”— inggrid.org/article/id/4296/

    #ResearchDataManagement #DataLifecycle #Metadata #FieldData #FAIR #Robotics

  10. πŸ“„ New Manuscript published

    "Collaborative creation and management of rich FAIR metadata: Two case studies from robotics field research", by Christian Backe, Veit Briken, Atefeh Gooran Orimi, Rayen Hamlaoui, Malte Wirkus, Bilal Wehbe, and Frank Kirchner

    πŸ”— inggrid.org/article/id/4296/

    #ResearchDataManagement #DataLifecycle #Metadata #FieldData #FAIR #Robotics

  11. πŸ“„ New Manuscript published

    "Collaborative creation and management of rich FAIR metadata: Two case studies from robotics field research", by Christian Backe, Veit Briken, Atefeh Gooran Orimi, Rayen Hamlaoui, Malte Wirkus, Bilal Wehbe, and Frank Kirchner

    πŸ”— inggrid.org/article/id/4296/

    #ResearchDataManagement #DataLifecycle #Metadata #FieldData #FAIR #Robotics

  12. @ml @academicchatter @plantscience Date *everything*, and get into the habit of using an internationally unambiguous date format (eg 2024-08-07, or 7 Aug 2024 or Aug 7 2024, but never 7/8/2024).

    If you’re forced to use Excel, ensure that dates are entered in a way that Excel cannot interpret the column as a date (eg force the column format to character, or type the date as the number 20240807). This avoids date data being occasionally scrambled and corrupted.

    #FieldData #Science

  13. @ml @academicchatter @plantscience Date *everything*, and get into the habit of using an internationally unambiguous date format (eg 2024-08-07, or 7 Aug 2024 or Aug 7 2024, but never 7/8/2024).

    If you’re forced to use Excel, ensure that dates are entered in a way that Excel cannot interpret the column as a date (eg force the column format to character, or type the date as the number 20240807). This avoids date data being occasionally scrambled and corrupted.

    #FieldData #Science

  14. @ml @academicchatter @plantscience Date *everything*, and get into the habit of using an internationally unambiguous date format (eg 2024-08-07, or 7 Aug 2024 or Aug 7 2024, but never 7/8/2024).

    If you’re forced to use Excel, ensure that dates are entered in a way that Excel cannot interpret the column as a date (eg force the column format to character, or type the date as the number 20240807). This avoids date data being occasionally scrambled and corrupted.

    #FieldData #Science

  15. @ml @academicchatter @plantscience Date *everything*, and get into the habit of using an internationally unambiguous date format (eg 2024-08-07, or 7 Aug 2024 or Aug 7 2024, but never 7/8/2024).

    If you’re forced to use Excel, ensure that dates are entered in a way that Excel cannot interpret the column as a date (eg force the column format to character, or type the date as the number 20240807). This avoids date data being occasionally scrambled and corrupted.

    #FieldData #Science

  16. @ml @academicchatter @plantscience Date *everything*, and get into the habit of using an internationally unambiguous date format (eg 2024-08-07, or 7 Aug 2024 or Aug 7 2024, but never 7/8/2024).

    If you’re forced to use Excel, ensure that dates are entered in a way that Excel cannot interpret the column as a date (eg force the column format to character, or type the date as the number 20240807). This avoids date data being occasionally scrambled and corrupted.

    #FieldData #Science

  17. Prepared and curated a large dataset? Deployed stations for an ongoing project? Document it, share it!

    Get the best footprint from your instrument deployment and dataset. Publish it as part of Seismica's data-based reports:

    seismica.library.mcgill.ca/aut

    #seismology #earthquakescience #peerreview #openaccess #OpenScience #diamondopenaccess #fielddata #dataset #Sustainability

  18. Prepared and curated a large dataset? Deployed stations for an ongoing project? Document it, share it!

    Get the best footprint from your instrument deployment and dataset. Publish it as part of Seismica's data-based reports:

    seismica.library.mcgill.ca/aut

    #seismology #earthquakescience #peerreview #openaccess #OpenScience #diamondopenaccess #fielddata #dataset #Sustainability

  19. Prepared and curated a large dataset? Deployed stations for an ongoing project? Document it, share it!

    Get the best footprint from your instrument deployment and dataset. Publish it as part of Seismica's data-based reports:

    seismica.library.mcgill.ca/aut

    #seismology #earthquakescience #peerreview #openaccess #OpenScience #diamondopenaccess #fielddata #dataset #Sustainability

  20. Prepared and curated a large dataset? Deployed stations for an ongoing project? Document it, share it!

    Get the best footprint from your instrument deployment and dataset. Publish it as part of Seismica's data-based reports:

    seismica.library.mcgill.ca/aut

    #seismology #earthquakescience #peerreview #openaccess #OpenScience #diamondopenaccess #fielddata #dataset #Sustainability

  21. Prepared and curated a large dataset? Deployed stations for an ongoing project? Document it, share it!

    Get the best footprint from your instrument deployment and dataset. Publish it as part of Seismica's data-based reports:

    seismica.library.mcgill.ca/aut

    #seismology #earthquakescience #peerreview #openaccess #OpenScience #diamondopenaccess #fielddata #dataset #Sustainability