[Incubator] Request to register CoastalME as an OSGeo community project

Nick Bearman nick at nickbearman.com
Thu Oct 3 04:09:46 PDT 2024


Dear Andres,

Thank you for your email. I have one initial question. I am not clear on 
the relationship between the repo at 
https://github.com/coastalme/coastalme and the repo at 
https://github.com/davefavismortlock/coastalme_TESTING. The TESTING one 
is a fork of the coastalme one, but the coastalme one has not been 
updated in ~6 years.

Also the link from the TESTING repo 
http://coastalme.org.uk/doku/doku.php does not work.

I'm guessing there is some background to this, but it is confusing for 
us, and for any potential user.

Is there any further information you can provide?

Also, is this a standalone program, or a library that can be used in 
other environments (QGIS, R, Python, etc.)?

Others may also have more questions.

Best wishes,
Nick.

On 30/09/2024 19:35, Andres Payo Garcia - BGS via Incubator wrote:
>
> Incubation committee:
>
> I am writing on behalf of the team behind CoastalME (Coastal Modelling 
> Environment Software) project to list my project
>
> on the OSGeo website to be able to join the OSGeo incubation program 
> and ultimately create a global community of developers.
>
>  CoastalME is a software framework to simulate how the 3D coastal 
> landscape evolves
>
> over time scales of decades to centuries under different climate and 
> human intervention conditions.
>
>  The main code is built on C++ and uses GDAL/OGR library to read and 
> write the geospatial input/outputs.
>
>  This modelling framework is described in detail in the Geoscientific 
> Model Development Journal, https://doi.org/10.5194/gmd-10-2715-2017
>
>  Change in coastal morphology is represented by means of dynamically 
> linked raster and geometrical objects.
>
>  A grid of raster cells provides the data structure for representing 
> quasi-3-D spatial heterogeneity and sediment conservation.
>
>  Other geometrical objects (lines, areas and volumes) that are 
> consistent with, and derived from, the raster structure represent a
>
>  library of coastal elements (e.g. shoreline, beach profiles and 
> estuary volumes) as required by different landform-specific models.
>
>  Since the first proof of concept v1.0 (2017, 
> https://github.com/coastalme/coastalme ), CoastalME has been developed 
> significantly (https://github.com/davefavismortlock/coastalme_TESTING),
>
> reaching several releases, with the latest version being 1.1.22. The 
> team of core users and developers of CoastalME has grown significantly 
> over time, and is currently used for both
>
> research applications and decision making applications in England and 
> Spain. The most recent interest has been from the European Space 
> Agency, as part of the Destination Earth program (DestinE, 
> https://destination-earth.eu/)
>
>  that is a flagship initiative of the European Commission to develop a 
> highly-accurate digital model of the Earth (a digital twin of the 
> Earth) to model, monitor and simulate natural phenomena, hazards and
>
>  the related human activities. These groundbreaking features assist 
> users in designing accurate and actionable adaptation strategies and 
> mitigation measures. This has the potential of expanding the CoastalME 
> user and developer
>
> over the next two years. In this context, our goal is to enable the 
> co-development of a coastal simulation model suitable for geospatial 
> decision making and planning.
>
> Historically, CoastalME was a project initiated by Oxford University 
> responding to the demand of holistic simulation models for decision 
> making.
>
>  The research done on Integrated COASTal sediment systems (iCOAST) 
> (2012-2016) (NERC Reference : NE/J005584/1) with EA as an embedded 
> stakeholder produced a
>
>  positive change to UK public services and is enabling the change 
> needed to transition to a better adapted UK coastline to the risk of 
> coastal flooding and erosion.
>
> Out of iCOAST research, the EA produced a report on coastal 
> morphological modelling for decision makers: 
> https://assets.publishing.service.gov.uk/media/603793e0e90e07055b44b743/Coastal_morphological_modelling_for_decision-makers_-_report.pdf
>
> Since its inception as part of the iCOAST project, CoastalME has 
> always been an open-source project, and now has been adopted by the 
> British Geological Survey as the main modelling framework of coastal 
> change.
>
> With the support of OSGeo, CoastalME aims to expand its community,
>
>  enhance its governance, and promote its features to a wider audience.
>
> Community Project Application Checklist:
>
> - 1. Geospatial:
>
>      - 1.1. README or project description:
>
>          - README: [CoastalME 
> README](https://github.com/coastalme/coastalme/README.md or 
> https://github.com/davefavismortlock/coastalme_TESTING/README.md)
>
>          - Project website: [CoastalME 
> Website](https://earthwise.bgs.ac.uk/index.php/Category:Coastal_Modeling_Environment)
>
>      - 1.2. User guide or quickstart:
>
>          - CoastalME Documentation available:
>
> - [CoastalME Documentation](see website and README)
>
> - [Development Documentation](to be developed with support of OSGeo as 
> part of the incubation program)
>
>  - [C++ API 
> Documentation](https://github.com/davefavismortlock/coastalme_TESTING/tree/master/Doxygen
>
> - 2. Free or Open Source License:
>
>      - 2.1. License file:
>
>          - CoastalME is provided under the following license: GPL version
>
>  3 or later. You can find the license here: [CoastalME License](
>
> https://github.com/davefavismortlock/coastalme_TESTING?tab=GPL-3.0-1-ov-file).
>
>          - Note that the main dependency for CoastalME is the GDAL/OGR 
> library, and CoastalME uses the also open source code CSHORE
>
>  modules which are licensed as GPLv3+. Whenever you compile and
>
>  distribute CoastalME with the GPL-licensed, the full packaged result
>
>  is automatically considered as GPL version 3 or later, due to GPL's 
> "viral"
>
> property. If you link and distribute CoastalME with another software
>
>  package, be sure to fully understand the implications and check any
>
>  legal and technical requirements implied by the license.
>
>      - 2.2. Check headers:
>
>          - All files have a licence identifier, [for 
> example](https://github.com/davefavismortlock/coastalme_TESTING/blob/master/src/2di_point.cpp)
>
> - 3. Participatory:
>
>      - 3.1 All required and relevant files are located in the CoastalME
>
> repository:
>
>          - [Contribution Policy](to be developed with support of OSGeo 
> as part of the incubation program)
>
>          - [Code of Conduct](to be developed with support of OSGeo as 
> part of the incubation program)
>
>          - [History of Contributions]( 
> https://doi.org/10.5194/gmd-10-2715-2017)
>
>          - [Closed Merge Requests](to be developed with support of 
> OSGeo as part of the incubation program)
>
> - 4. Open Community:
>
>      - 4.1 communication channel: (to be developed with support of 
> OSGeo as part of the incubation program)
>
> - 5. Development Process
>
>      - version control: We use git. Code is located at 
> [Github](https://github.com/davefavismortlock/coastalme_TESTING)
>
>      - issue tracker: (to be developed with support of OSGeo as part 
> of the incubation program)
>
>      - leadership open to new members: (to be developed with support 
> of OSGeo as part of the incubation program)
>
>      - transparent decision-making: (to be developed with support of 
> OSGeo as part of the incubation program)
>
> - 6. Documentation
>
>      - see 1.2. User guide or quickstart
>
> - 7. Release Procedure
>
>      - Release procedure to be developed with support of OSGeo as part 
> of the incubation program
>
> If you have any questions about the project or our application, please
>
>  let me know and I'll be more than happy to help.
>
>  My OSGeo userid is "coastalme" and I will need permission to create a 
> project page.
>
> Best Regards,
>
> *Andres Payo *PhD, MSc
>
> Head of Coasts & Estuaries
>
> https://www.bgs.ac.uk/geology-projects/coasts-and-estuaries/ 
> <https://www.bgs.ac.uk/geology-projects/coasts-and-estuaries/>
>
> *p *+44 (0)115 9363103 | https://ukri.zoom.us/my/apayo 
> <https://ukri.zoom.us/my/apayo>
>
> *m *+44 (0)742 567 3451
>
> *e *agarcia at bgs.ac.uk <mailto:agarcia at bgs.ac.uk>
> *w *www.bgs.ac.uk <http://www.bgs.ac.uk/>
>
> British Geological Survey | Nicker Hill | Keyworth | Nottingham NG12 
> 5GG | UK
>
>
>
> This email and any attachments are intended solely for the use of the 
> named recipients. If you are not the intended recipient you must not 
> use, disclose, copy or distribute this email or any of its attachments 
> and should notify the sender immediately and delete this email from 
> your system. UK Research and Innovation (UKRI) has taken every 
> reasonable precaution to minimise risk of this email or any 
> attachments containing viruses or malware but the recipient should 
> carry out its own virus and malware checks before opening the 
> attachments. UKRI does not accept any liability for any losses or 
> damages which the recipient may sustain due to presence of any viruses.
>
>
> _______________________________________________
> Incubator mailing list
> Incubator at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/incubator

-- 
Nick Bearman
+44 (0) 7717745715
nick at nickbearman.com - New email address!

Please let me know if I can make any adjustments related to disability or neurodivergence to improve how we interact.

Due to my own life/work balance, you may get emails from me outside of normal working hours. Please do not feel any pressure to respond outside of your own working pattern.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20241003/9d505fe6/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 21194 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20241003/9d505fe6/attachment-0001.png>


More information about the Incubator mailing list