Hi Andrei,
I hope I'm not too insistent, but I think I have 3 more feature
requests :)
You're welcome. Asking is free and we are always happy to discuss
technical stuff with new users having needs we didn't think about.
(Getting things done is another thing and may need much patience...)
1. Keep attribute table dialog open while digitizing in order to
introduce a sequence of objects and their attributes (presently the
attribute table collapses each time you start using an editing tool)
The attribute table is not collapsed but hidden by LayerViewPanel as
soon as the last one get the focus (when you start editing for example).
You can make a mosaic with your internal frames (Window > Mosaic)
I'm not sure that having attribute table always on top would be a good
thing. IMHO, what is missing is a good docking framework to lay internal
frames out more easily.
What do you think ?
2. Add a new "split polygon by linestring" option to the right-click
context menu (now you have to follow this path to get the desired
result: {select the polygon and dividing linestring} Tools->Edit
geometry->Split polygon, check "Update the polygon with result"->Ok)
Agree that it would be more user-friendly (and more efficient) to have
the "update" option in the right-click context menu.
Maybe an alternative would be to add an option in each dialog box to
skip the interactive dialog step and run the plugin with the last
checked options (but this is a bigger change)
By the way, do you know EZ button from customize menu ?
It is a very efficient tool from Larry Becker to create a shortcut to
any menu-item.
3. A "Save view at fixed scale" option for both raster and svg
exports. I don't know if you're aware, but the Printer extension
preserves the map layout scale only for PDF exports; the svg and
png-saved images are scaled down a bit (I've already discussed this
problem with Geoffrey Roy and there's not much that can be done, at
least not in the near future ).
I can't understand why there would be a specific problem with svg and
png format and not with pdf, but Geoffrey Roy knows printing functions
much better than me.
I know there is another printing plugin (on sourceforge). Did you try it ?
Do you have more precise information about the origin of the problem ?
I'm really glad I found nearly everything needed to learn how to
develop plug ins and how to translate Open Jump into another language:
http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Developer_Documentation_and_HowTo
We'll be glad to add your language and your contributions to the project.
Regards,
Michaël
Andrei
------------------------------------------------------------------------
*From:* Michaël Michaud <michael.mich...@free.fr>
*To:* Andrei Nacu <andreina...@yahoo.com>
*Sent:* Monday, April 9, 2012 5:35 PM
*Subject:* Re: [JPP-Devel] Feature requests for Open Jump
Hi Andrei,
Hope you don't mind if I make a copy of my answer to the list.
All your ideas are interesting and worth a discussion with other
project members.
In order to get proper results when snapping two line strings, you
have to use the line with less vertices as the reference layer. Or
maybe you can come with something that will automatically create more
vertices for the layer you want to snap. In the attached screen shot
1, for example, you will have to snap the red line to the green line
(reference).
I see. What you try to do is conflation, and it is a bit beyond the
scope of the topology plugin, but, maybe we can go a step further.
I don't like too much the concept of "line with more vertices" because :
- the layer having more vertices may change from one feature to
another, and even for a single feature
- the geometry with more points is probably more precise, and you may
want to use it as the reference
On the other hand, densification of geometries should not be too hard
to implement as the underlying JTS library has this function.
I will add a feature request for that. It may help to control which
layer is your reference and to get correct result.
The only tricky part will be to add z interpolation for 3d geometries.
Yes, I downloaded the PLUS.zip version of Open Jump and it has the
new merge selected features option. Thank you :)
I would like to fill 3 more feature requests, but I want you to check
them and see if they are reasonable.
1. Merge KML file import/export option from Sky Jump:
https://sourceforge.net/projects/skyjump/
SkyJUMP KML's driver is already available for OpenJUMP. See :
http://geo.michaelm.free.fr/OpenJUMP/resources/drivers/
I did not uploaded it on openjump website because I was waiting some
feedback (the only try I had - with a file containing hierarchical kml
data - did not work).
So, your experience with it is very welcome.
2. Add a new tracing constrain. This would be a complex option I
think. The constrain will allow users to snap a line/polygon to
features from other layers without mouse-clicking to match every
vertex. For example (screen shot no. 2) I have to draw a parcel
(polygon) that borders 3 other layers: forest (polygon layer), road
(line layer) and stream (line layer). You can see how many clicks are
needed to digitize the desired polygon. I want to be able to simply
hover the mouse over another feature until left-clicking, and get a
perfectly matched line or polygon.
Did you try the recent "Fill polygon" plugin (AKA "Create Polygon
from Closed Area") in the lower-right corner of the toolbox ?
You need to have a perfectly closed area though (with nodes at each
intersection)
Tell me if it fits your need, as what you describe seems a bit
difficult to me.
3. Allow bottom and top line rendering to create road and railway
design. Basically I now have to duplicate layers in order to create
road or railway patterns (screen shot 3). Also there should be no
overlapping between bottom and top line patterns from different
layers (screen shots 4 and 5) or from same layer in case colour
theming is activated.
OpenJUMP misses many styling options right now.
I think what you ask is more or less implemented in the kosmo version
of jump. Did you try it ?
I wrote on the roadmap that we should study how kosmo implemented
their advanced styling options, but we lack developpers to achieve
such improvements.
(https://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Roadmap)
My idea about this problem, which, I think, would not be too difficult
to implement would be to add the concept of virtual layer which would
be a simple view on a datasource. Adding virtual layers for styling
purpose could be done as you currently do with layer duplication,
except there would be no overhead as data would not be duplicated.
Something to design carefully and to discuss with other developpers.
Best regards,
Michaël
Andrei
------------------------------------------------------------------------
*From:* Michaël Michaud <michael.mich...@free.fr>
<mailto:michael.mich...@free.fr>
*To:* Andrei Nacu <andreina...@yahoo.com> <mailto:andreina...@yahoo.com>
*Sent:* Monday, April 9, 2012 12:17 AM
*Subject:* Re: [JPP-Devel] DEM support in Open Jump
Hi
Thanks, it makes it clear now.
Not so lengthy if one consider that it was not the scenario I had in
mind when I made this plugin (my use case was to snap endpoints of a
network onto another network).
But an option to wrap your process (explode linestring / snap / merge
linestrings) seems interesting to me now that I can see what you get ;-)
I'll add it on my todo list.
Don't bother with the log file.
Download the xxxPLUS.exe or the xxxPLUS.zip
the .exe is a classic windows installer
the .zip contains a bin directory with all the starter scripts (use
oj_windows.bat or OpenJUMP.exe to start it on a windows box)
Michaël
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
