Replace JTS with EPLicense version from LocationTech
See original GitHub issueAfter gtfs addition we need to update the NOTICE file and use the EDL version for jts once released:
<groupId>org.locationtech.jts</groupId>
<artifactId>jts</artifactId>
<version>1.15.0</version>
Include elevation data attribution and GTFS attribution in the NOTICE file or somewhere else.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
jts/LICENSE_EPLv2.txt at master · locationtech/jts - GitHub
The JTS Topology Suite is a Java library for creating and manipulating vector geometry. - jts/LICENSE_EPLv2.txt at master · locationtech/jts.
Read more >State of JTS | GeoMesa
License Change. • LocationTech Incubation. • Build Infrastructure. • Official Maven Deployment. • Long term hopes. • Additional Contributors.
Read more >Migrating com.vividsolutions.jts to org.locationtech.jts still ...
I have updated all the imports to use org.locationtech version. However, in my function I'm still getting an error related to com.vividsolutions ...
Read more >State of JTS | OSGeo
License Change. • LocationTech Incubation. • Long term hopes. • Additional Contributors. • Funding for JTS 2.0. • Build Infrastructure.
Read more >locationtech / jts Download - JitPack
The JTS Topology Suite is a Java library for creating and manipulating vector geometry. ... Upgrade Guide - How to migrate from previous...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Okay! If you decide you’d like to give the fork a go, let me know and I can put together PRs for those dependencies.
(Upstream seems to go in a somewhat different direction anyway, so I don’t think I have to worry about keeping future developments mergeable.)