geotools-gt2-users — Help and support for GeoTools users

Re: [Geotools-gt2-users] unknown source (In AWT-EventQueue-0)

[Jody G. <jod...@gm...>]

Looks like clicking on a button; see the stack trace.

Chances are something made a dynamic proxy or something and thus no line
number.

--
Jody Garnett


On Sat, Dec 16, 2023 at 8:29 AM <pie...@sy...> wrote:

> Hi,
>
>
>
> I have a event in my  AWT-EventQueue-0 thread that has no source and which
> causes my application to stop.
>
>
>
>
>
> …
>
> ContentFeatureStore.addFeatures(FeatureCollection)
> (\gt-main-30.1.jar\org.geotools.data.store\ContentFeatureStore.class:246)
>
> Visualiseur.doPolyMat(Geometry,String)
> (d:\GMT_7023\projet\CadMat\src\main\java\com\pc\app\Visualiseur.java:1063)
>
> Visualiseur.lambda$8(ActionEvent)
> (d:\GMT_7023\projet\CadMat\src\main\java\com\pc\app\Visualiseur.java:494)
>
> *18601987.actionPerformed(ActionEvent) (Unknown source:-1)*
>
> AbstractButton.fireActionPerformed(ActionEvent)
> (\java.desktop\javax.swing\AbstractButton.class:1967)
>
> AbstractButton$Handler.actionPerformed(ActionEvent)
> (\java.desktop\javax.swing\AbstractButton.class:2308)
>
> DefaultButtonModel.fireActionPerformed(ActionEvent)
> (\java.desktop\javax.swing\DefaultButtonModel.class:405)
>
> …
>
>
>
>
>
> What can create this kind of situation?
>
>
>
> Regards,
>
>
>
> Pierre
>
>
>
>
>
>
> _______________________________________________
> GeoTools-GT2-Users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>

[Geotools-gt2-users] unknown source (In AWT-EventQueue-0)

[<pie...@sy...>]

Hi, 

 

I have a event in my  AWT-EventQueue-0 thread that has no source and which
causes my application to stop. 

 

 

.

ContentFeatureStore.addFeatures(FeatureCollection)
(\gt-main-30.1.jar\org.geotools.data.store\ContentFeatureStore.class:246)

Visualiseur.doPolyMat(Geometry,String)
(d:\GMT_7023\projet\CadMat\src\main\java\com\pc\app\Visualiseur.java:1063)

Visualiseur.lambda$8(ActionEvent)
(d:\GMT_7023\projet\CadMat\src\main\java\com\pc\app\Visualiseur.java:494)

18601987.actionPerformed(ActionEvent) (Unknown source:-1)

AbstractButton.fireActionPerformed(ActionEvent)
(\java.desktop\javax.swing\AbstractButton.class:1967)

AbstractButton$Handler.actionPerformed(ActionEvent)
(\java.desktop\javax.swing\AbstractButton.class:2308)

DefaultButtonModel.fireActionPerformed(ActionEvent)
(\java.desktop\javax.swing\DefaultButtonModel.class:405)

.

 

 

What can create this kind of situation?

 

Regards,

 

Pierre

 

 

 

Re: [Geotools-gt2-users] MapLayerTable and MapComponent - GeoTools 30

[<pie...@sy...>]

Hi Jody,

 

 

Now what I see is that there is no code inside the function "MapLayerTable$Listener.layerMoved(MapLayerListEvent)" of the file "MapLayerTable.java"

 

 

 

       @Override

        public void layerAdded(MapLayerListEvent event) {

            if (event.getLayer() == null) {

                List<Layer> layers = table.mapPane.getMapContent().layers();

                for (Layer l : layers.subList(event.getFromIndex(), event.getToIndex() + 1)) {

                    table.onAddLayer(l);

                }

            } else {

                table.onAddLayer(event.getLayer());

            }

        }

 

        @Override

        public void layerRemoved(MapLayerListEvent event) {

            table.onRemoveLayer(event.getLayer());

        }

 

        @Override

        public void layerChanged(MapLayerListEvent event) {

            table.repaint(event.getLayer());

        }

 

        @Override

        public void layerMoved(MapLayerListEvent event) {}

 

        @Override

        public void layerPreDispose(MapLayerListEvent event) {}

 

 

Regards,

 

Pierre

 

 

 

 

De : Jody Garnett <jod...@gm...> 
Envoyé : 12 décembre 2023 15:44
À : Sympatico <pie...@sy...>
Cc : geo...@li...
Objet : Re: [Geotools-gt2-users] MapLayerTable and MapComponent - GeoTools 30

 

Can you step through with a debugger and see what has gone wrong? It feels like something some list copy (for thread safety) has gone wrong.

 

There are not that many desktop users of GeoTools presently, I am glad you are using the functionality.

 

 

 

On Tue, Dec 12, 2023 at 12:07 PM Sympatico <pie...@sy... <mailto:pie...@sy...> > wrote:

Hi,

 

I am using JMapFrame in my application. When I add a new Layer, the components MapContent and MapLayerTable are synchronized regarding Layers. But if used the function MapContent.moveLayer(pos1, pos2) to change de zOrder off a Layer, then the order of the Layers in the MapLayerTable is no more synchronized with the order of the Layers in the MapContent. 

 

Any idea about this situation ? 

 

                                                  

Regards,

Pierre

_______________________________________________
GeoTools-GT2-Users mailing list
Geo...@li... <mailto:Geo...@li...> 
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Re: [Geotools-gt2-users] MapLayerTable and MapComponent - GeoTools 30

[Jody G. <jod...@gm...>]

Can you step through with a debugger and see what has gone wrong? It feels
like something some list copy (for thread safety) has gone wrong.

There are not that many desktop users of GeoTools presently, I am glad you
are using the functionality.



On Tue, Dec 12, 2023 at 12:07 PM Sympatico <pie...@sy...>
wrote:

> Hi,
>
>
>
> I am using JMapFrame in my application. When I add a new Layer, the
> components MapContent and MapLayerTable are synchronized regarding Layers.
> But if used the function MapContent.moveLayer(pos1, pos2) to change de
> zOrder off a Layer, then the order of the Layers in the MapLayerTable is no
> more synchronized with the order of the Layers in the MapContent.
>
>
>
> Any idea about this situation ?
>
>
>
>
>
> Regards,
>
> Pierre
> _______________________________________________
> GeoTools-GT2-Users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>

[Geotools-gt2-users] MapLayerTable and MapComponent - GeoTools 30

[Sympatico <pie...@sy...>]

Hi,

 

I am using JMapFrame in my application. When I add a new Layer, the components MapContent and MapLayerTable are synchronized regarding Layers. But if used the function MapContent.moveLayer(pos1, pos2) to change de zOrder off a Layer, then the order of the Layers in the MapLayerTable is no more synchronized with the order of the Layers in the MapContent. 

 

Any idea about this situation ? 

 

                                                  

Regards,

Pierre

[Geotools-gt2-users] Test

[<pie...@sy...>]

Excuse me but I have trouble to find the adress list 

Re: [Geotools-gt2-users] GeoTools EPSG WKT plugin download?

[Ron L. <rli...@ya...>]

 Thanks Brad.I didn't know about the optionals map. "epsg-plugins" would be a more convenient name.
    On Tuesday, 21 November 2023 at 10:19:38 CET, Brad Hards <br...@fr...> wrote:  
 
 On Tuesday, 21 November 2023 8:04:53 PM AEDT Ron Lindhoudt via GeoTools-GT2-Users wrote:
> Hello,
> I notice that the EPSG WKT plugin is not part of the GeoTools bin download
> anymore. File gt-epsg-wkt-*.jar Where can I download
> it?See https://docs.geotools.org/latest/userguide/library/referencing/wkt.h
> tml Thanks for any help.

I just downloaded 30.0 from sourceforge.

bradh@audax:~/Downloads$ unzip -q geotools-30.0-bin.zip 
bradh@audax:~/Downloads$ ls -l geotools-30.0/optional/gt-epsg-wkt-30.0.jar 
-rw-r--r-- 1 bradh bradh 259425 Oct 13 07:42 geotools-30.0/optional/gt-epsg-wkt-30.0.jar

(Note, not under lib/)

HTH

Brad



  

Re: [Geotools-gt2-users] GeoTools EPSG WKT plugin download?

[Ian T. <ijt...@gm...>]

That link should be -
modules/plugin/epsg-wkt/src/main/resources/org/geotools/referencing/epsg/wkt/epsg.properties
if you want to update the docs

Ian

On Tue, 21 Nov 2023 at 09:21, Brad Hards <br...@fr...> wrote:

> On Tuesday, 21 November 2023 8:04:53 PM AEDT Ron Lindhoudt via
> GeoTools-GT2-Users wrote:
> > Hello,
> > I notice that the EPSG WKT plugin is not part of the GeoTools bin
> download
> > anymore. File gt-epsg-wkt-*.jar Where can I download
> > it?See
> https://docs.geotools.org/latest/userguide/library/referencing/wkt.h
> > tml Thanks for any help.
>
> I just downloaded 30.0 from sourceforge.
>
> bradh@audax:~/Downloads$ unzip -q geotools-30.0-bin.zip
> bradh@audax:~/Downloads$ ls -l
> geotools-30.0/optional/gt-epsg-wkt-30.0.jar
> -rw-r--r-- 1 bradh bradh 259425 Oct 13 07:42
> geotools-30.0/optional/gt-epsg-wkt-30.0.jar
>
> (Note, not under lib/)
>
> HTH
>
> Brad
>
>
>
>
>
> _______________________________________________
> GeoTools-GT2-Users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>


-- 
Ian Turton

Re: [Geotools-gt2-users] GeoTools EPSG WKT plugin download?

[Brad H. <br...@fr...>]

On Tuesday, 21 November 2023 8:04:53 PM AEDT Ron Lindhoudt via GeoTools-GT2-Users wrote:
> Hello,
> I notice that the EPSG WKT plugin is not part of the GeoTools bin download
> anymore. File gt-epsg-wkt-*.jar Where can I download
> it?See https://docs.geotools.org/latest/userguide/library/referencing/wkt.h
> tml Thanks for any help.

I just downloaded 30.0 from sourceforge.

bradh@audax:~/Downloads$ unzip -q geotools-30.0-bin.zip 
bradh@audax:~/Downloads$ ls -l geotools-30.0/optional/gt-epsg-wkt-30.0.jar 
-rw-r--r-- 1 bradh bradh 259425 Oct 13 07:42 geotools-30.0/optional/gt-epsg-wkt-30.0.jar

(Note, not under lib/)

HTH

Brad

[Geotools-gt2-users] GeoTools EPSG WKT plugin download?

[Ron L. <rli...@ya...>]

Hello,
I notice that the EPSG WKT plugin is not part of the GeoTools bin download anymore. File gt-epsg-wkt-*.jar
Where can I download it?See https://docs.geotools.org/latest/userguide/library/referencing/wkt.html
Thanks for any help.
Ron

[Geotools-gt2-users] Latest maintenance release GeoTools 29.3

[Peter S. <gs...@sm...>]

We are pleased to announce the release of the latest maintenance version of
GeoTools (29.3).  More details are available in the related blog post:

https://geotoolsnews.blogspot.com/2023/10/geotools-293-released.html

Peter

Re: [Geotools-gt2-users] geotools artifacts on OSGeo repo - here gt-api

[Brad H. <br...@fr...>]

On Saturday, 21 October 2023 12:20:39 AM AEDT Marco Lechner - FOSSGIS e.V. 
wrote:
> I have an old mvn-based project that needs to be updated. I want to
> update the used geotools version, because 14.5 versions of gt-api,
> gt-referencing, gt-opengis and gt-epsg-hsql are used. The problem is
> that these artifacts seem to be available only partly for several
> geotools versions on OSGeo repo:
> While gt-referencing and gt-epsg-hsql are available for lots of versions
> (30.0, 29.0-29.2 28.0-28.5, ..., 20.0-20.5, 19.0-19.4, ...), gt-opengis
> is lacking the 30.0 artifact and there are no artifacts for gt-api
> between 20.5 and 30.0 (well, but 30.0 is available!)
> 
> This is a little bit confusing. Can anyone enlighten me, whats wromg
> with the geotools artifact versions?
Nothing is "wrong", its just different. There have been significant changes 
since 14.5. Please consult the upgrade guide in the geotools documentation. 

In particular, the gt-opengis package is no more as of 30.0, but there is an 
upgrade script that might (or might not - that is a lot of versions) help.

Possibly gt-api could be a lot different to what it was back then too.

Brad

[Geotools-gt2-users] geotools artifacts on OSGeo repo - here gt-api

[Marco L. - F. e.V. <mar...@fo...>]

Hi,

I have an old mvn-based project that needs to be updated. I want to 
update the used geotools version, because 14.5 versions of gt-api, 
gt-referencing, gt-opengis and gt-epsg-hsql are used. The problem is 
that these artifacts seem to be available only partly for several 
geotools versions on OSGeo repo:
While gt-referencing and gt-epsg-hsql are available for lots of versions 
(30.0, 29.0-29.2 28.0-28.5, ..., 20.0-20.5, 19.0-19.4, ...), gt-opengis 
is lacking the 30.0 artifact and there are no artifacts for gt-api 
between 20.5 and 30.0 (well, but 30.0 is available!)

This is a little bit confusing. Can anyone enlighten me, whats wromg 
with the geotools artifact versions?

Regards
Marco

Re: [Geotools-gt2-users] GeoTools 30.0 released

[Jody G. <jod...@gm...>]

A personal thank you to everyone who tested the RC; this was an excellent
response to our request to test. If I missed anyone in the release
announcement please speak up.

I am impressed!
Jody

On Sun, Oct 15, 2023 at 10:24 PM Jody Garnett <jod...@gm...>
wrote:

> GeoTools 30.0 has been released as the new stable release of the library -
> more details (and a fun diagram) in the release announcement
> <http://geotoolsnews.blogspot.com/2023/10/geotools-300-released.html>.
> The release is available for download and directly from maven.
>
> This update features an api-break due to the refactor of the org.opengis
> package to org.geotools.api package (along with associated cleanup).  The upgrade
> instructions
> <https://docs.geotools.org/stable/userguide/welcome/upgrade.html> include
> a well-tested script you may use on your codebase.  We would like to thank
> Ian Turton, Andrea Aime and Jody Garnett for completing this activity, and
> everyone who helped test the release candidate.
>
> Thanks to Peter Smith and Jody Garnett for making this release.
> --
> Project Management Committee
>

[Geotools-gt2-users] GeoTools 30.0 released

[Jody G. <jod...@gm...>]

GeoTools 30.0 has been released as the new stable release of the library -
more details (and a fun diagram) in the release announcement
<http://geotoolsnews.blogspot.com/2023/10/geotools-300-released.html>.  The
release is available for download and directly from maven.

This update features an api-break due to the refactor of the org.opengis
package to org.geotools.api package (along with associated cleanup).
The upgrade
instructions
<https://docs.geotools.org/stable/userguide/welcome/upgrade.html> include a
well-tested script you may use on your codebase.  We would like to thank
Ian Turton, Andrea Aime and Jody Garnett for completing this activity, and
everyone who helped test the release candidate.

Thanks to Peter Smith and Jody Garnett for making this release.
--
Project Management Committee

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

[Jody G. <jod...@gm...>]

 Core-geonetwork was able to migrate to *java.xml.bind.annotation* classes:

   - javax.xml.bind.annotation.XmlElement
   - javax.xml.bind.annotation.XmlElement
   XmlAccessorType(XmlAccessType.PUBLIC_MEMBER)


I think that is sensible advice we can add to our update instructions.
--
Jody Garnett


On Oct 7, 2023 at 12:21:52 AM, Jody Garnett <jod...@gm...> wrote:

> Well apparently we should of tested geonetwork, ... it was using one of
> the annotations that we removed: @XmlElement
>
> I am going to ask if this was just used for documentation or was required
> to support some reflection. For now I have migrated the annotation to the
> geonetwork so the pull-request can build:
> https://github.com/geonetwork/core-geonetwork/pull/7416
> --
> Jody Garnett
>
>
> On Oct 1, 2023 at 3:29:08 PM, Jody Garnett <jod...@gm...> wrote:
>
>> Wow this has been a journey, the GeoTools Project Management committee -
>> and especially the crew attending the Bolsena code sprint
>> <https://www.osgeo.org/events/bolsena-code-sprint-2023/> are pleased to
>> share the GeoTools 30-RC Release Candidate with you.
>>
>> The blog post is here:
>> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>>
>> This is a very unusual and ambitious update for the GeoTools project -
>> with some deliberate breaking API changes (gasp how rude). Indeed in
>> response to a request from OGC members we are making some changes to the
>> structure of our library.
>>
>> But fear not there is a script to help, from the user manual upgrade page
>> <https://docs.geotools.org/stable/userguide/welcome/upgrade.html>:
>>
>>     *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
>> project directory)*
>>
>> As for the refactor:
>>
>>
>>    1. The package org.opengis has changed org.geotools.api.
>>    2. The main data access interfaces have been moved from
>>    org.geotools.data to org.geotools.api.data. This includes, DataStore,
>>    FeatureSource, FeatureIterator, and many others.
>>    As part of the move, the datastore registration files found in
>>    META-INF/services need to be moved as well.
>>    3. Most of the "org.geotools.metadata" package is gone, as these
>>    classes and interfaces were not used.
>>    4. Internationalized error message support has been removed.
>>    5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>>    and supporting classes) were no longer in use. The direct use of JTS
>>    Topology Suite Geometry is now used throughout the library
>>    6. The org.opengis.geometry and org.opengis.geometry.coordinates
>>    interfaces for positions, envelopes and bounding boxes have been revised as
>>    part of their refactor to org.geotools.api.
>>    7. The interface "org.opengis.geometry.Envelope" has been renamed
>>    "org.geotools.api.geometry.Bounds" and some of the confusion related to the
>>    proliferation of envelope-related classes has been cleaned up.
>>
>>
>> The nice thing is that after all this work the library is easier to use
>> with dead code and duplication removed.
>>
>> We have had lots of great feedback from downstream projects and early
>> testers - with this release candidate we wish to cast a wider net asking
>> for YOUR help!
>>
>>
>>    - GeoWebCache <https://github.com/GeoWebCache/geowebcache/issues/1151>
>>    - mapfish-print-v2
>>    <https://github.com/GeoWebCache/geowebcache/issues/1151>
>>    - GeoMesa <https://geomesa.atlassian.net/browse/GEOMESA-3285> - project
>>    has created a small script
>>    <https://geomesa.atlassian.net/browse/GEOMESA-3285> to update Scala
>>    projects!
>>    - GeoServer <https://osgeo-org.atlassian.net/browse/GEOS-11070>
>>    - geotools-devel mailing list
>>
>>
>> Please reply to this email with your success on running the script and
>> updating to GeoTools 30-RC.
>>
>> We look forward to hearing from you!
>> --
>> GeoTools Project Management Committee
>>
>

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

[Jody G. <jod...@gm...>]

 Well apparently we should of tested geonetwork, ... it was using one of
the annotations that we removed: @XmlElement

I am going to ask if this was just used for documentation or was required
to support some reflection. For now I have migrated the annotation to the
geonetwork so the pull-request can build:
https://github.com/geonetwork/core-geonetwork/pull/7416
--
Jody Garnett


On Oct 1, 2023 at 3:29:08 PM, Jody Garnett <jod...@gm...> wrote:

> Wow this has been a journey, the GeoTools Project Management committee -
> and especially the crew attending the Bolsena code sprint
> <https://www.osgeo.org/events/bolsena-code-sprint-2023/> are pleased to
> share the GeoTools 30-RC Release Candidate with you.
>
> The blog post is here:
> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>
> This is a very unusual and ambitious update for the GeoTools project -
> with some deliberate breaking API changes (gasp how rude). Indeed in
> response to a request from OGC members we are making some changes to the
> structure of our library.
>
> But fear not there is a script to help, from the user manual upgrade page
> <https://docs.geotools.org/stable/userguide/welcome/upgrade.html>:
>
>     *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
> project directory)*
>
> As for the refactor:
>
>
>    1. The package org.opengis has changed org.geotools.api.
>    2. The main data access interfaces have been moved from
>    org.geotools.data to org.geotools.api.data. This includes, DataStore,
>    FeatureSource, FeatureIterator, and many others.
>    As part of the move, the datastore registration files found in
>    META-INF/services need to be moved as well.
>    3. Most of the "org.geotools.metadata" package is gone, as these
>    classes and interfaces were not used.
>    4. Internationalized error message support has been removed.
>    5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>    and supporting classes) were no longer in use. The direct use of JTS
>    Topology Suite Geometry is now used throughout the library
>    6. The org.opengis.geometry and org.opengis.geometry.coordinates
>    interfaces for positions, envelopes and bounding boxes have been revised as
>    part of their refactor to org.geotools.api.
>    7. The interface "org.opengis.geometry.Envelope" has been renamed
>    "org.geotools.api.geometry.Bounds" and some of the confusion related to the
>    proliferation of envelope-related classes has been cleaned up.
>
>
> The nice thing is that after all this work the library is easier to use
> with dead code and duplication removed.
>
> We have had lots of great feedback from downstream projects and early
> testers - with this release candidate we wish to cast a wider net asking
> for YOUR help!
>
>
>    - GeoWebCache <https://github.com/GeoWebCache/geowebcache/issues/1151>
>    - mapfish-print-v2
>    <https://github.com/GeoWebCache/geowebcache/issues/1151>
>    - GeoMesa <https://geomesa.atlassian.net/browse/GEOMESA-3285> - project
>    has created a small script
>    <https://geomesa.atlassian.net/browse/GEOMESA-3285> to update Scala
>    projects!
>    - GeoServer <https://osgeo-org.atlassian.net/browse/GEOS-11070>
>    - geotools-devel mailing list
>
>
> Please reply to this email with your success on running the script and
> updating to GeoTools 30-RC.
>
> We look forward to hearing from you!
> --
> GeoTools Project Management Committee
>

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

[Ian T. <ijt...@gm...>]

On Fri, 6 Oct 2023 at 17:20, Jody Garnett <jod...@gm...> wrote:

> Nice,
>
> Do you have examples of the 'ReferencedEnvelope.create(' lines that did
> not get picked up? Maybe we can adjust the script ..
>


They are split over 2 lines which I think caused the problem:

ReferencedEnvelope bounds = ReferencedEnvelope.create(new Envelope(xMin,
xMax, yMin, yMax),
        coordinateReferenceSystem);

Ian

>
> I am going to get core-geonetwork today and report back.
>
> Jody
>
> On Fri, Oct 6, 2023 at 8:29 AM Ian Turton <ijt...@gm...> wrote:
>
>>
>> Everything went pretty well in the repos I've tested - a few
>> `ReferencedEnvelope.creates(` didn't get picked up by the conversion tool
>> but nothing too severe
>>
>> Ian
>>
>>
>> On Sun, 1 Oct 2023 at 23:30, Jody Garnett <jod...@gm...> wrote:
>>
>>> Wow this has been a journey, the GeoTools Project Management committee -
>>> and especially the crew attending the Bolsena code sprint
>>> <https://www.osgeo.org/events/bolsena-code-sprint-2023/> are pleased to
>>> share the GeoTools 30-RC Release Candidate with you.
>>>
>>> The blog post is here:
>>> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>>>
>>> This is a very unusual and ambitious update for the GeoTools project -
>>> with some deliberate breaking API changes (gasp how rude). Indeed in
>>> response to a request from OGC members we are making some changes to the
>>> structure of our library.
>>>
>>> But fear not there is a script to help, from the user manual upgrade
>>> page <https://docs.geotools.org/stable/userguide/welcome/upgrade.html>:
>>>
>>>     *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
>>> project directory)*
>>>
>>> As for the refactor:
>>>
>>>
>>>    1. The package org.opengis has changed org.geotools.api.
>>>    2. The main data access interfaces have been moved from
>>>    org.geotools.data to org.geotools.api.data. This includes, DataStore,
>>>    FeatureSource, FeatureIterator, and many others.
>>>    As part of the move, the datastore registration files found in
>>>    META-INF/services need to be moved as well.
>>>    3. Most of the "org.geotools.metadata" package is gone, as these
>>>    classes and interfaces were not used.
>>>    4. Internationalized error message support has been removed.
>>>    5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>>>    and supporting classes) were no longer in use. The direct use of JTS
>>>    Topology Suite Geometry is now used throughout the library
>>>    6. The org.opengis.geometry and org.opengis.geometry.coordinates
>>>    interfaces for positions, envelopes and bounding boxes have been revised as
>>>    part of their refactor to org.geotools.api.
>>>    7. The interface "org.opengis.geometry.Envelope" has been renamed
>>>    "org.geotools.api.geometry.Bounds" and some of the confusion related to the
>>>    proliferation of envelope-related classes has been cleaned up.
>>>
>>>
>>> The nice thing is that after all this work the library is easier to use
>>> with dead code and duplication removed.
>>>
>>> We have had lots of great feedback from downstream projects and early
>>> testers - with this release candidate we wish to cast a wider net asking
>>> for YOUR help!
>>>
>>>
>>>    - GeoWebCache
>>>    <https://github.com/GeoWebCache/geowebcache/issues/1151>
>>>    - mapfish-print-v2
>>>    <https://github.com/GeoWebCache/geowebcache/issues/1151>
>>>    - GeoMesa <https://geomesa.atlassian.net/browse/GEOMESA-3285> - project
>>>    has created a small script
>>>    <https://geomesa.atlassian.net/browse/GEOMESA-3285> to update Scala
>>>    projects!
>>>    - GeoServer <https://osgeo-org.atlassian.net/browse/GEOS-11070>
>>>    - geotools-devel mailing list
>>>
>>>
>>> Please reply to this email with your success on running the script and
>>> updating to GeoTools 30-RC.
>>>
>>> We look forward to hearing from you!
>>> --
>>> GeoTools Project Management Committee
>>> _______________________________________________
>>> GeoTools-GT2-Users mailing list
>>> Geo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>>>
>>
>>
>> --
>> Ian Turton
>>
>

-- 
Ian Turton

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

[Jody G. <jod...@gm...>]

Nice,

Do you have examples of the 'ReferencedEnvelope.create(' lines that did not
get picked up? Maybe we can adjust the script ..

I am going to get core-geonetwork today and report back.

Jody

On Fri, Oct 6, 2023 at 8:29 AM Ian Turton <ijt...@gm...> wrote:

>
> Everything went pretty well in the repos I've tested - a few
> `ReferencedEnvelope.creates(` didn't get picked up by the conversion tool
> but nothing too severe
>
> Ian
>
>
> On Sun, 1 Oct 2023 at 23:30, Jody Garnett <jod...@gm...> wrote:
>
>> Wow this has been a journey, the GeoTools Project Management committee -
>> and especially the crew attending the Bolsena code sprint
>> <https://www.osgeo.org/events/bolsena-code-sprint-2023/> are pleased to
>> share the GeoTools 30-RC Release Candidate with you.
>>
>> The blog post is here:
>> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>>
>> This is a very unusual and ambitious update for the GeoTools project -
>> with some deliberate breaking API changes (gasp how rude). Indeed in
>> response to a request from OGC members we are making some changes to the
>> structure of our library.
>>
>> But fear not there is a script to help, from the user manual upgrade page
>> <https://docs.geotools.org/stable/userguide/welcome/upgrade.html>:
>>
>>     *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
>> project directory)*
>>
>> As for the refactor:
>>
>>
>>    1. The package org.opengis has changed org.geotools.api.
>>    2. The main data access interfaces have been moved from
>>    org.geotools.data to org.geotools.api.data. This includes, DataStore,
>>    FeatureSource, FeatureIterator, and many others.
>>    As part of the move, the datastore registration files found in
>>    META-INF/services need to be moved as well.
>>    3. Most of the "org.geotools.metadata" package is gone, as these
>>    classes and interfaces were not used.
>>    4. Internationalized error message support has been removed.
>>    5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>>    and supporting classes) were no longer in use. The direct use of JTS
>>    Topology Suite Geometry is now used throughout the library
>>    6. The org.opengis.geometry and org.opengis.geometry.coordinates
>>    interfaces for positions, envelopes and bounding boxes have been revised as
>>    part of their refactor to org.geotools.api.
>>    7. The interface "org.opengis.geometry.Envelope" has been renamed
>>    "org.geotools.api.geometry.Bounds" and some of the confusion related to the
>>    proliferation of envelope-related classes has been cleaned up.
>>
>>
>> The nice thing is that after all this work the library is easier to use
>> with dead code and duplication removed.
>>
>> We have had lots of great feedback from downstream projects and early
>> testers - with this release candidate we wish to cast a wider net asking
>> for YOUR help!
>>
>>
>>    - GeoWebCache <https://github.com/GeoWebCache/geowebcache/issues/1151>
>>    - mapfish-print-v2
>>    <https://github.com/GeoWebCache/geowebcache/issues/1151>
>>    - GeoMesa <https://geomesa.atlassian.net/browse/GEOMESA-3285> - project
>>    has created a small script
>>    <https://geomesa.atlassian.net/browse/GEOMESA-3285> to update Scala
>>    projects!
>>    - GeoServer <https://osgeo-org.atlassian.net/browse/GEOS-11070>
>>    - geotools-devel mailing list
>>
>>
>> Please reply to this email with your success on running the script and
>> updating to GeoTools 30-RC.
>>
>> We look forward to hearing from you!
>> --
>> GeoTools Project Management Committee
>> _______________________________________________
>> GeoTools-GT2-Users mailing list
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>>
>
>
> --
> Ian Turton
>

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

[Ian T. <ijt...@gm...>]

Everything went pretty well in the repos I've tested - a few
`ReferencedEnvelope.creates(` didn't get picked up by the conversion tool
but nothing too severe

Ian


On Sun, 1 Oct 2023 at 23:30, Jody Garnett <jod...@gm...> wrote:

> Wow this has been a journey, the GeoTools Project Management committee -
> and especially the crew attending the Bolsena code sprint
> <https://www.osgeo.org/events/bolsena-code-sprint-2023/> are pleased to
> share the GeoTools 30-RC Release Candidate with you.
>
> The blog post is here:
> https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html
>
> This is a very unusual and ambitious update for the GeoTools project -
> with some deliberate breaking API changes (gasp how rude). Indeed in
> response to a request from OGC members we are making some changes to the
> structure of our library.
>
> But fear not there is a script to help, from the user manual upgrade page
> <https://docs.geotools.org/stable/userguide/welcome/upgrade.html>:
>
>     *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your
> project directory)*
>
> As for the refactor:
>
>
>    1. The package org.opengis has changed org.geotools.api.
>    2. The main data access interfaces have been moved from
>    org.geotools.data to org.geotools.api.data. This includes, DataStore,
>    FeatureSource, FeatureIterator, and many others.
>    As part of the move, the datastore registration files found in
>    META-INF/services need to be moved as well.
>    3. Most of the "org.geotools.metadata" package is gone, as these
>    classes and interfaces were not used.
>    4. Internationalized error message support has been removed.
>    5. The org.opengis.geometry interfaces (for Point, Curve and Surface
>    and supporting classes) were no longer in use. The direct use of JTS
>    Topology Suite Geometry is now used throughout the library
>    6. The org.opengis.geometry and org.opengis.geometry.coordinates
>    interfaces for positions, envelopes and bounding boxes have been revised as
>    part of their refactor to org.geotools.api.
>    7. The interface "org.opengis.geometry.Envelope" has been renamed
>    "org.geotools.api.geometry.Bounds" and some of the confusion related to the
>    proliferation of envelope-related classes has been cleaned up.
>
>
> The nice thing is that after all this work the library is easier to use
> with dead code and duplication removed.
>
> We have had lots of great feedback from downstream projects and early
> testers - with this release candidate we wish to cast a wider net asking
> for YOUR help!
>
>
>    - GeoWebCache <https://github.com/GeoWebCache/geowebcache/issues/1151>
>    - mapfish-print-v2
>    <https://github.com/GeoWebCache/geowebcache/issues/1151>
>    - GeoMesa <https://geomesa.atlassian.net/browse/GEOMESA-3285> - project
>    has created a small script
>    <https://geomesa.atlassian.net/browse/GEOMESA-3285> to update Scala
>    projects!
>    - GeoServer <https://osgeo-org.atlassian.net/browse/GEOS-11070>
>    - geotools-devel mailing list
>
>
> Please reply to this email with your success on running the script and
> updating to GeoTools 30-RC.
>
> We look forward to hearing from you!
> --
> GeoTools Project Management Committee
> _______________________________________________
> GeoTools-GT2-Users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>


-- 
Ian Turton

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

[Jody G. <jod...@gm...>]

Thanks Mark!

Anyone else in position to test :)

On Mon, Oct 2, 2023 at 1:04 AM mark <mc....@gm...> wrote:

> Op 02-10-2023 om 00:29 schreef Jody Garnett:
>
> > Please reply to this email with your success on running the script and
> > updating to GeoTools 30-RC.
>
> Upgraded some of our projects last week, most of them took me less than
> 10 mins to produce a PR. All testsuites pass.
>
> Only thing I ran into was we had our own "Bounds" object somewhere in
> our own API and that started conflicting with the upgraded code which
> replaces (opengis)Envelope with (geotools)Bounds, but that is a trivial fix
>
> Mark
>
>
> _______________________________________________
> GeoTools-GT2-Users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>

Re: [Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

[mark <mc....@gm...>]

Op 02-10-2023 om 00:29 schreef Jody Garnett:

> Please reply to this email with your success on running the script and 
> updating to GeoTools 30-RC.

Upgraded some of our projects last week, most of them took me less than 
10 mins to produce a PR. All testsuites pass.

Only thing I ran into was we had our own "Bounds" object somewhere in 
our own API and that started conflicting with the upgraded code which 
replaces (opengis)Envelope with (geotools)Bounds, but that is a trivial fix

Mark

[Geotools-gt2-users] GeoTools 30-RC release candidate available - please test!

[Jody G. <jod...@gm...>]

Wow this has been a journey, the GeoTools Project Management committee -
and especially the crew attending the Bolsena code sprint
<https://www.osgeo.org/events/bolsena-code-sprint-2023/> are pleased to
share the GeoTools 30-RC Release Candidate with you.

The blog post is here:
https://geotoolsnews.blogspot.com/2023/09/geotools-30-rc-released.html

This is a very unusual and ambitious update for the GeoTools project - with
some deliberate breaking API changes (gasp how rude). Indeed in response to
a request from OGC members we are making some changes to the structure of
our library.

But fear not there is a script to help, from the user manual upgrade page
<https://docs.geotools.org/stable/userguide/welcome/upgrade.html>:

    *ant -f remove-opengis.xml -Dproject.dir=(absolute path to your project
directory)*

As for the refactor:


   1. The package org.opengis has changed org.geotools.api.
   2. The main data access interfaces have been moved from
   org.geotools.data to org.geotools.api.data. This includes, DataStore,
   FeatureSource, FeatureIterator, and many others.
   As part of the move, the datastore registration files found in
   META-INF/services need to be moved as well.
   3. Most of the "org.geotools.metadata" package is gone, as these classes
   and interfaces were not used.
   4. Internationalized error message support has been removed.
   5. The org.opengis.geometry interfaces (for Point, Curve and Surface and
   supporting classes) were no longer in use. The direct use of JTS Topology
   Suite Geometry is now used throughout the library
   6. The org.opengis.geometry and org.opengis.geometry.coordinates
   interfaces for positions, envelopes and bounding boxes have been revised as
   part of their refactor to org.geotools.api.
   7. The interface "org.opengis.geometry.Envelope" has been renamed
   "org.geotools.api.geometry.Bounds" and some of the confusion related to the
   proliferation of envelope-related classes has been cleaned up.


The nice thing is that after all this work the library is easier to use
with dead code and duplication removed.

We have had lots of great feedback from downstream projects and early
testers - with this release candidate we wish to cast a wider net asking
for YOUR help!


   - GeoWebCache <https://github.com/GeoWebCache/geowebcache/issues/1151>
   - mapfish-print-v2
   <https://github.com/GeoWebCache/geowebcache/issues/1151>
   - GeoMesa <https://geomesa.atlassian.net/browse/GEOMESA-3285> - project
   has created a small script
   <https://geomesa.atlassian.net/browse/GEOMESA-3285> to update Scala
   projects!
   - GeoServer <https://osgeo-org.atlassian.net/browse/GEOS-11070>
   - geotools-devel mailing list


Please reply to this email with your success on running the script and
updating to GeoTools 30-RC.

We look forward to hearing from you!
--
GeoTools Project Management Committee

Re: [Geotools-gt2-users] getting a ysld symbol from geoserver

[RIOU Y. PP-D. S. <yva...@in...>]

Hi mark :)

Thank you for your answer !

Meanwhile, I corrected my bad coding because I looked at the source code 
of Ysld.java :

‌       StringBuilder gareInput;
         gareInput = new StringBuilder();

         String inputLine;

         while ((inputLine = in.readLine()) != null) {
             gareInput.append(inputLine);
             gareInput.append('\n');
         }
         in.close();

         StyledLayerDescriptor gareSldDesc = 
Ysld.parse(gareInput.toString());


But then how would you get the style of gareSldDesc object in order to 
display the wfs layer ?
I tried that code but nothing got displayed :

‌        NamedLayer gareLayer = (NamedLayer) 
gareSldDesc.getStyledLayers()[0];

         Style gareStyle;
         gareStyle = gareLayer.getStyles()[0];

         Layer layer = new FeatureLayer(featureSource, gareStyle);
         map.addLayer(layer);

         // Now display the map
         JMapFrame.showMap(map);


Thank you for your help :)

Re: [Geotools-gt2-users] getting a ysld symbol from geoserver

[mark <mc....@gm...>]

Op 21-09-2023 om 16:03 schreef RIOU Yvan PP-DILT SDT:
> /        StringBuilder response = new StringBuilder();//
> //        String inputLine;//
> ////
> //        while ((inputLine = in.readLine()) != null) {//
> //            response.append(inputLine);//
> //        }//
> ////
> //        in.close(); //
> ////
> //        System.out.println(response);//
> ////
> //        StyledLayerDescriptor gareSldDesc = Ysld.parse(response);/

You need to pass something that implements the Readable interface to the 
parse method. eg.  new StringReader(response.toString())

see 
https://github.com/geotools/geotools/blob/9adf1357cb29a81b44c8cef9cb3fc3197385da92/modules/extension/ysld/src/main/java/org/geotools/ysld/Ysld.java#L54-L81