Latest Contributions by ÁkosHalmai

At the beginning of the "New Reality Mapping Workspace", you have to select the scenario, which can be Aerial or Drone. On the drone side, better support needed for orientation data: 1. If you add an image, perspective center is listed, no orientation data is displayed. The user is unable to decide, whether there is no orientation data in the image or just not loaded. Here three extra columns, like yaw, pitch, and roll would be beneficial. 2. At the "Import GPS file" it is possible to load orientation. However, the only accepted format is OPK, which is rarely used in the drone world: Yaw, Pitch, Roll is much more supported, and users are not prepared to do calculations on the local tangential plane. A switch between OKP and YPR would be nice. And if the user loads orientation data, at the Adjust, the Use orientation from metadata should be selected automatically 3. There is an assumption that the location info is loaded from EXIF, but most of the drone manufacturers support XMP metadata, with better and bigger resolution of location, location accuracy and orientation readings. Best regards, Ákos Halmai ... View more

The Adjustment Report is a nice feature to summarize the processing steps, expected quality and the basic settings, however it could be improved especially at the "Camera Calibration" section: 1. Distortion parameters are not labelled. We get six numbers, probably four K constants and two P constants. Which one is which the first four are the K-s (K₁; K₂; K₃; K₄)? Followed by the P-s? It is also interesting, that we have just three K-s at the user interface, but four is printed. It would be nice to have them like this: K₁: 0.0001... etc. 2. At the pixel size the unit is "um" which meant to be micrometers. Here, there is no reason to use the ASCII only, it would be better to see "µm" instead. (Micro sign in UTF-8). It should be also synchronized with the user interface at camera properties at the beginning, where the UI says "microns".   Best regards, Ákos Halmai  ... View more

In the Options on the general tab, there is check box, called "Use GPU with CUDA compute capabilities...". It would be nice to see the available GPUs to rule out driver and other issues. It would be even better to be able to select & deselect certain GPUs, to include or exclude from calculations. If there is no available GPU, a big yellow warning would be great too. Best regards, Ákos Halmai   ... View more

I have a lot aerial imagery, where the X; Y; Z & OPK was recorded in PCS EPSG 23700 and VCS EPSG 5787. Today it is impossible to process these images, while it runs perfectly in ArcGIS Pro's Reality mapping workspace. It says the coordinate system transformation is unavailable to WGS84/EGM2008. Yes, it is true, but who needs it it if every data and the GCPs are referenced in the given coordinate system? I suppose, the the problem is coming from the Globe or from the footprint generation, but in this case you can ask for a DEM (like in Reality mapping workspace in Pro). Thank you & Best regards, Ákos Halmai ... View more

This new, project tree on the left is great, however If I create for example a reconstruction I run it, then I have to create another one, it is impossible to remove the first, unnecessary one. No delete button, no right click & delete. Same with the alignments: if I create two or three alignments with different settings, I run them and finally I choose the best one, it is impossible to remove the others.  Similar to the Geometries: If I add a RoI it is impossible to remove it, once added. Thank you & Best regards, Ákos Halmai   ... View more

I see this app is a customized ArcGIS Pro, so please put the Light UI mode back. If you deal with imagery it is usually beneficial to have Dark mode, but in case of presentation & education the dark is nightmare on low contrast projector. Sometimes the office is full with light, even with correct screen positions, in this case it is strenuous to use a dark app. Dark apps are great in dark environments. A lighter/customizable basemap, and/or with lighter symbology would be also great! Check out the following print screen. Do you see the camera symbols, symbolized by Camera Position Residuals X? They are there, but simply too dark to draw some attention. Thank you & Best regards, Ákos Halmai   ... View more

Please, add [DebuggerDisplay()] attribute to the major struct & and classes like: Coordinate2D & Coordinate3D to see the actual value instead of "{ArcGIS.Core.Geometry.Coordinate2D}" and  "{ArcGIS.Core.Geometry.Coordinate3D}". If it is empty, just print "Empty" otherwise the coordinates like "18.46; 46.18". MapPoint: same as above, with wkid, like "18.46; 46.18; 4326". Polyline & Polygon: use Length, Length & Area (if not empty). GeographicTransformationListEntry: every entry has its own name. This could be the natural DebuggerDisplay for it, like "Hungarian_1972_To_WGS_1984_2", or maybe "Hungarian_1972_To_WGS_1984_2; 4327 → 4326" (two wkids at the end). CoordinateSystemListEntry: same as above, just use the Name property. SpatialReference: the name would be more natural. This will improve the development experience a lot. ... View more