Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory layers with a field type of "Geometry" cannot have features added. #344

Open
akater320 opened this issue Mar 27, 2019 · 3 comments
Open
Labels

Comments

@akater320
Copy link
Contributor

To reproduce:

  1. Layer > Create
  2. Choose "Geometry" as the "Type" for the geometry column.
  3. Attempt to add a feature with the "Create Point" tool or one of the other "Create ..." tools.
  • An IllegalArgumentException should be logged.

I believe this is caused by a bug in GeoTools.
GEOT-6275

PostGIS layers with type "Geometry" seem to work correctly.

@fgdrf fgdrf added the bug label Mar 27, 2019
@fgdrf
Copy link
Contributor

fgdrf commented Mar 27, 2019

Thanks for reporting. Would you add details about the version of uDig you are tested with? Wondering if this is 1.2.x, 1.4.x or even 2.x? I've seen GeoTools version 2.6.6 and 20.3 is set in mentioned issued field, looks like it is an old bug that still exists in current GT-Releases..

@nprigour
Copy link
Contributor

nprigour commented Mar 27, 2019

Hi All,

I just tried this to my machine running udig 2.x. It seems that the problem does exist when you create a layer with geom type 'Geometry' with null allowed set to false. In that case indeed a

java.lang.IllegalArgumentException: class com.vividsolutions.jts.geom.Geometry is not supported by this method

is thrown. However wif during creation null allowed is set to true then creation and saving is possible (in the latter case though occasianally another issue may arise related to the assignment of fid values).

@akater320
Copy link
Contributor Author

Hey guys, thanks for checking this out.
(I try to confirm issues in the master branch before reporting them.)

The geometry layers do seem to work fine when "null allowed" is true.

I can confirm the fid issue.
It you have a create-geometry tool active and switch to a different layer that also supports that geometry it often shows the fid exception until you choose a different tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants