Thanks for reporting to natural earth, from the geotools side this appears
to be inconsistent data. I tend to prefer failing fast on any processing
which could result in loss of data. That way we do not become part of the
problem, only help identify the issue.
Aside: A soft approach would be to
That is good news, please send me your osgeo user id and I will set you up.
--
Jody Garnett
On Tue, 12 May 2020 at 16:20, Jared Erickson
wrote:
> I was wondering if I could get access to https://build.geoserver.org/ so
> I can fix the geoscript-py and geoscript-js builds. I am updating both
>
Oh - I reported the issue to the Natural Earth people -
https://github.com/nvkelso/natural-earth-vector/issues/343
On Tue, May 12, 2020 at 5:11 PM David Blasby
wrote:
> Hi,
>
> I was trying to use the Natural Earth GeoPackage (countries) - link below.
>
> However, I found the rendering was very
Hi,
I was trying to use the Natural Earth GeoPackage (countries) - link below.
However, I found the rendering was very "wrong";
[image: image.png]
This triangle is actually 3 small islands - it's represented in the
GeoPackage as a Multipolygon (one polygon for each island).
This works fine in
I was wondering if I could get access to https://build.geoserver.org/ so I
can fix the geoscript-py and geoscript-js builds. I am updating both
projects so they are up to date with GeoTools. Then I plan on getting the
GeoServer / GeoScript extension working again.
Thanks!
Jared
On Tue, May 12,
GeoTools / GeoServer PMC meeting - 2020-05-12Attending
Torben Barsballe
Andrea Aime
Jukka Rahkonen
Jody Garnett
Actions from last meeting
-
Action: (done) Give Fernado a login to the GeoServerO twitter
-
Action: Announced 2.17 on email lists
-
Action: Update 2.17
Thanks for the roundup. One comment:
>
> *jdbc-mysql*
> Same situation as the others. I might try to setup a build and see how bad
> it is, if we're not too far away, I'd
> create an PR build check for it and keep it (otherwise, bye bye)
>
This already (ostensibly) has an online build running
Hi Paul,
Thanks for reporting, investigating and fixing that. I assume you are working
with a HANA 1 instance. The SRID derivation was removed in HANA 2 because it
caused too many issues.
So, the fix won’t work for HANA 2, but it won’t do any harm either (if the SRID
is omitted in HANA 2, it
Hi,
I have created an issue and a PR:
Jira-issue:
https://osgeo-org.atlassian.net/browse/GEOT-6587
Pull request:
https://github.com/geotools/geotools/pull/2926
Regards,
Paul
Von: Jody Garnett
Gesendet: Dienstag, 12. Mai 2020 02:49
An: Biskup, Paul ; Uhrig, Stefan
Cc: