Activity for michael michaud
-
michael michaud posted a comment on discussion Problems with PlugIns
Hi Sivio, I'm not familiar with this extension, but I tried to reproduce the problem and noticed that the plugin checks input data is valid but omit to display a clear message if it is not. Before I could see the "parameter" tab, I get errors first because both raser input were the same, then because they have not the same resolution... There is no message displayed on screen but one can grab it in the log file. Could you check your log file or send it to me so I can see if we can find some explanations...
-
Hi hydroy, Can you give us more details (OpenJUMP version, data type loaded in your project) ? Until now I could not reproduce the error. I tried with version 1.16 (last 1.x) and 2.2.0 (recommended), I loaded two tif images with the Image Raster (Sextante) loader, made one visible and the second one invisible and could save the project. The only thing I noticed is that the visibilty is lost after re-opening the project. Michaël
-
Jukka, you are the expert about spatialite. I made a quick test but a confirmation from you would be welcome. I think OpenJUMP is not ready to manage the full set of geometries with Z, M and ZM, but it should read geometries with Z without losing Z and read geometries with ZM at least as geometries with Z.
-
Peppe, this plugin is still present in OpenJUMP 2.0. Can you tell us where we are about this ticket ?
-
OpenJUMP fails to read 4D geom from postgis
-
4D geometries are still not fully read, but they are now correctly interpreted as 3D geometries Example : LINESTRINGZM(1 2 3 4, 5 6 7 8, 9 10 11 12) is read as LINESTRING Z ( 1 2 3, 5 6 7, 9 10 11 ) I close the ticket
-
Replace geometric algo by JTS
-
Will ask for a double check on OpenJUMP 2.0 before closing the ticket
-
JTS Densifier will take care of Z in the next version. Note here as a reminder. Let's say target version for this change is 2.1.x (adoption of next JTS version)
-
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hi Ede,Are you sure you tested the extension from the plugins menu and using the drag mode as stated by Peppe and not the measure tool of the toolbar which works fine for me also ?Michaëlenvoyé : 22 novembre 2021 à 14:06de : ede via Jump-pilot-devel <jump-pilot-devel@lists.sourceforge.net>à : jump-pilot-devel@lists.sourceforge.netcc : ede <edso@users.sourceforge.net>objet : [JPP-Devel] [jump-pilot:bugs] #521 Error on Measure Toolbox...
-
Sorry, https://ojrepo.soldin.de "2.0-SNAPSHOT" is referencing jts1.18.1 but "2.0-main-SNAPSHOT" is referencing jts 1.18.2 and measure-toolbox is pointing to the second. So I have no idea about what happens. By the way, is there a reason to keep 2 snapshots in the repo ? Michaël
-
Hi, My fault, checksum was ok, but I did a mistake in the file name. I could compile and package locally now, but it still throws an exception. The only thing I can think about is that measure-toolbox still compile against https://ojrepo.soldin.de/ which reference 1.18.1 Michaël
-
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hi Ede,I tried to follow your procedure, but I can't build OpenJUMP against the new measure-toolbox-extension-2.1.1-alpha release because of the sha1 checksum.I updated OpenJUMP pom with the checksum taken from measure-toolbox-extension-2.1.1-alpha.zip.sha1 computed at the same time as the .zip itselfHere after the message I get while building the project with mavenAny idea ?Michaël [INFO] Downloading: https://github.com/openjump-gis/measure-toolbox-extension/releases/download/2.1.1-alpha/measure-toolbox-extension-2.1.0-alpha.zip[INFO]...
-
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hi,Quite strange error. I think fix would be easy by using an alternative method like CoordinateList.add(Coordinate,boolean), but I would rather understand what happens.In the past few years, CoordinateList.add(Coordinate) has been added to CoordinateList class with a signature incompatible with the signature of its parent class ArrayList (void add(Coordinate) instead of boolean add(Coordinate)), then the return type has been fixed...
-
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hi Johns,Maybe you'll find what you need in the VertexSymbol plugin.With this extension, you can - create your camera position as points in your map with an attribute for camera orientation in degrees- add a custom symbol (ex. camera outline + angle of view) by adding its wkt geometry description in %openjump%/lib/ext/VertexImages- select your symbol with the plugin > Styles > Symbols tab- link the orientation attribute to the symbol...
-
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hi Ede,Nice idea. Seems to me that the only check call involved is in EnableCheckMenuItemShownListener.Don't you thing it maybe an overkilled solution. It means that opening a new menu will create as many threads as visible menuitems. I don't want to slow down every enablecheck just to solve a rare case that we can may be identify and solve independantly.Anyway, your solution maybe also be a temporary step to identify where the slowdown...
-
Some menus may be slow down by enableCheck associated to them. Most enable checks just check general properties of the layer, but some may implement specific checks on feature geometries. In case of heavy geometries, such check may slowdown the UI responsiveness.
-
SelectFilesOptionPanel and extensions
-
Fixed by Ede's refactoring of I18N class in OpenJUMP 2 and by an upgrade of all extensions hosted on github.
-
Java2xml framework : no default default value
-
Added on 2021-09-07. See BasicStyle.java2xml for an example.
-
Hey, I made a quick test with OpenJUMP 2.0 (snapshot) and it seems to read geometry 3d correctly (thanks to JTS 1.18 upgrade). Note that I could read it with a spatialite db created from postgis, but I could not read any geometry from my first try with a database opened in spatialite_gui where I imported shapefiles. Any spatialite user to confirm this ticket can be closed ?
-
Raster styling bug
-
fix regression introduced in r6621 & r6662 in raster Vectorizer
-
Fix GradientCanvas (synchronize with github repo)
-
try catch getImageInfo for the case it can't be parsed by commons imaging
-
Set bpp to 16b for flt, asc and txt
-
Replace geometric algo by JTS
-
Add TODO to old classes which can be replaced by JTS classes
-
Fix javadoc
-
Fix I18N for fr
-
Fix javadoc and improve pre-java5 code
-
Set java source version to 8 to avoid some errors when generating javadoc from java 11
-
Java2xml framework : no default default value
-
Add nodata value in the index to avoid a NPE
-
Use english locale to format numbers
-
Raster styling bug
-
should be fixed in r6656
-
fix #517 : raster styling of float32 image
-
Raster styling bug
-
update readme, exclude hamcrest and rhino:js from the distribution
-
replace MergeSelectedPolygonsWithNeighbourPlugIn by MergePolygonsWithNeighbourPlugIn :faster, transactional, more options
-
replace MergeSelectedPolygonsWithNeighbourPlugIn by MergePolygonsWithNeighbourPlugIn :faster, transactional, more options
-
RemodelerTool not correct
-
Should be fixed. Waiting for feedback from a known user.
-
Delete Incremental Warping Vector tool does not work
-
CropWarp raster plugin can't overload existing file
-
Thank Peppe, I let it opened as it may probably be fixed in a better way, but it can be postponed to version 2. Currently, a first dialog ask the user if he wants to overwrite the existing file. If yes, the user is informed it is not possible.
-
Georeferenced RasterImage : useless dialog to create a worlfile
-
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> Hi Ede,Thank you for the overview of the main raster classes.I don't know if your proposition of saving the displayed image to disk would improve performance/memory usage. It would need tests. Anyway, let's postpone this to v2. From my point of view, making raster code more robust and simpler is more important, but making it faster or less greedy in memory would also be nice.Michaël envoyé : 26 novembre 2020 à 14:43de : ede <edso@users.sourceforge.net>à...
-
ChangeLog
-
Fix modeler : now, operations resulting in invalid geometries should be rolled back
-
Even after several bug fixes, I still not have a good understanding of the image framework. To be able to imagine improvements, I would need a more precise idea about when the image is read from disk and when/where/what is cached. It would deserve a page on the wiki if it does not exists so that we know precisely what we are taking about. Not sure I understand your proposition. Can you explain what would be the benefit of reading a lossless compressed tiff image from a temp folder compared to reading...
-
Remodeler : fixes on z interpolation
-
RemodelerTool not correct
-
Fix related to #515 + remove duplicate code which could cause OOME
-
Raster display in low memory situation
-
Update changes file
-
Find a way to free TiffUtilsV2 cache when necessary (and to avoid useless fiel lock).
-
Some cleaning in CropWarpPlugIn : move class variable to local variable when possible
-
Clean System.out
-
forgot cz...
-
Log case where GeoKeyDirectoryTag has the wrong type (e.g. string instead of short)
-
I18N for no-georeference found
-
Make it possible to read images with wrongly typed geotags like ones exported by Gimp
-
Free/close resources to avoid memory leaks and/or filelocks
-
I did further tests and observed something strange which may be related (or not) to this bug. I crop an image and save the result in a new file, it creates a new RasterImageLayer. I remove this new RasterImageLayer from the LayerNamePanel : the underlying file stay locked Now I remove also the original RasterImageLayer : now the file containing the cropped image is unlocked ! I tried to close a few streams and RenderedOp in TiffUtils2, but nothing fixed the problem. I also think that the big cache...
-
Images with positive y-scale
-
Did you have a try, Ede ? Can we close ?
-
Create Polygon From a Raster bug
-
I close the ticket and let Peppe open a new ticket or report Jukka's suggestion to use statistics in the wiki.
-
All this ticket is about situations where memory consumption is high compared to max available memory. Original behaviour : symbolizing process was cut off and image was displayed with a wrong appearance First fix : when available memory is too low, additional images are no more displayed Now : when available memory is too low, additional images are not displayed and a yellow warning is emitted Note : at the time where new images are loaded in OpenJUMP, memory maybe sufficient (for example if other...
-
Peppe, Seems that your noWF.tif contains invalid geotags. ExifTools shows the following warning "Non-standard format (string) for IFD0 0x87af GeoTiffDirectory" which explains why OpenJUMP throws an exception when it tries to read tag 34735 (waiting for unisgned short array, find a string) Can you explain how you made this file. If image is produced by a well-known gis tool, I'll try to throw a better mesage or to read the tag anyway.
-
Fix more deeply and document the half pixel shift problem
-
Fix more deeply and document the half pixel shift problem
-
Thanks for the reminder Peppe. It was useful. Initial statement should be fixed in r6623. I did not understand your last statement. Can you tell if it is solved by r6623, and if not, elaborate.
-
fix #512 about georeferencing (introduced by r6523)
-
Warning message if memory is too low to display images
-
Peppe, a) I cannot reproduce the problem. Can you test again with 6620+. In 6619, I let a println which could eventually throw a NPE. Also in 6619, line 432 is an empty line (?) b) We probably must handle memory limitations in a more elegant way, but it is not easy because the current code may let you load more image than what can be rendered. Rendering uses more or less memory depending on wether raster is visible and on the zoom level. I'll try to get a yellow warning when the image cache is emptied...
-
Maybe. I think at least NPE was a bug left in a recent commit I did. For other remarks, I really must repeat the process step by step.
-
I just made a fix as if it was a bug : floating values was not recognized because of a conversion to int which , I think, was not necessary. I also changed a piece of code to make it faster. Peppe, the change is quite small. Please, have a look and check if I have respected the original intention. I don't mind warning the user that there are too many different values in the image if it is the case, but it's a bit more work and somewhat subjective.
-
Fix #510 + acceleration
-
Remove a System.out.println which could cause NPE
-
I try to reproduce the problem this morning, but after I get a NPE in roughly similar conditions, I now try to describe the problem precisely, step by step... and the problem vanished. I'm quite sure there are some conditions producing weird results or NPE, but it may not be normal conditions. Sorry for the noise, it will need more tests before I can describe the problem in a useful way.
-
Georeferenced RasterImage : useless dialog to create a worlfile
-
CropWarp raster plugin can't overload existing file
-
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> Hi Peppe,Thank you for the detailed answer.Indeed, I was not trying to do something useful, just checking if I did not introduce a new bug in RasterImageLayer.I perfectly understand that applying this tool to a raster containing floating point values is not the normal use case. With such images, it would probably need an additional parameter to define intervals and include all pixels belonging to a same interval in the same polygon.I...
-
Create Polygon From a Raster bug
-
Continue simplification of RasterImageLayer and fix problem with RasterSymbology
-
GeoImage and RasterImageLayer : why JAI
-
Cleanup of RasterImageLayer and some related classes
-
Thanks Peppe, Please, check it is solved in 6602
-
fix #508 : java2XML with setInteriorBorder/hasInteriorBorder property
-
Nice addition. I still let the FR open as I still miss a dedicated editor with a better interface (1 line / attribute) and able to edit any selected feature, not only those just created.
-
Jukka, Should be fixed in r6601, please, have a test.
-
fix #382 : deleting warping vectors was not possible with incremental mode
-
Peppe, it appears that in commit 6437, you reverted the fix I did in commit 6399 to fix this bug. Do you remember why you reverted the change I did in clone() method. Thanks
-
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> envoyé : 13 octobre 2020 à 12:22de : ede <edso@users.sourceforge.net>à : "[jump-pilot:bugs] " <507@bugs.jump-pilot.p.re.sourceforge.net>objet : [jump-pilot:bugs] Re: #507 GeoImage and high zoom levelOn 10/12/2020 19:27, michael michaud wrote:There are two problems in GeoImage.paint when using very high level of zoom : - the image to display is computed with jai transformations like scaling, subsampling or cropping which use float...
-
Keep double parameters as long as possible (does not solve the pb described in #507)
-
Dataset charset not visible
1 >
