Hi,
-Query builder. If I make an attribute (string) query, operator
"equal", the combo box "value" shows only 11 values even if the layer
can have more. It should be more useful to see all values
Problem is OpenJUMP does not know the possible attribute values. To fill
the list, query builder scans the first lines of the table
Scanning more
- may take time (but scanning is quite fast)
- you may have thousands of different values (place names for ex.)
I can change 11 to 16, 24, 32...
To have more, it would need something else like a text field offering
text completion (an interesting project...)
- Query build. On "Results" option it would be nice to have two extra
options "Complements results" and "Zoom to selected"
Yes, you can do it with other plugins, but it can be added to this one
too. Could you write a FR for that.
- Attribute query. It seems to me that it makes the same job as Query
Builder, at least a part of it. Can we consider as a duplicate?
I think I developped Query builder for my own use before Attribute query
was added by Martin
to OpenJUMP. If I add the two features you described to query builder, I
agree that attribute
query has no more advantage (except, maybe, simplicity for some basic
needs). We can hide it.
- Other Duplicate plugins. 1) Tools>Analysis>Union/Dissolve/merge and
Tools>Analysis>Union. I will save the first (Michael's one) as it is
full of options (between Union and Dissolve)
If I get one more vote for that, I remove the old union tool.
2) Tools>Analysis>Create Thiessen polygons and Tools>Generate>Voronoi
diagram. The second is far better as it took only 1 second to
calculate 750 points while the 1st took some minutes
The second uses JTS triangulation, I don't know how the former one works.
I'm not sure that the option to limit the diagram (or to extend it) to a
given polygon
is easy to implement.
Is it important for some use cases ?
-Tools>Analysis>"Polygon Overlay" should be renamed "Polygon Overlay
(Union)", I think, to not confuse with the Tools>Analysis>Overlay
(which in turns is basically an Overlay (Intersect)). Overlasy seems
to me a general name ( I wonder what Uwe thinks about)
Maybe overlay could be replaced by Layer intersection.
I don't want to use union in this context, I think it would add confusion.
Regards,
Michaël
regards
Peppe
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
