|
IDEA
|
I wasn’t precise enough… Technically it can produce 3D output and it does produce 3D output. However the Z values of the vertices is fulfilled with zeros (at least in case of multipatch and multipoint inputs). Which is not exactly 3D any more if the input features are several thousand feet above the reference surface. But yes, technically it is 3D. So it is already offered, but it’s never implemented and never going to be implemented. (Reading about something in a manual is helpful, but not enough. Someone have to try it in the reality)
... View more
09-18-2017
01:16 PM
|
0
|
1
|
2899
|
|
IDEA
|
Now—at least in case of multipatch inputs—the result is planar. I’d like to see results like points created by arcpy.PointGeometry.centroid and/or arcpy.PointGeometry.trueCentroid.
... View more
09-16-2017
08:30 AM
|
2
|
10
|
3172
|
|
POST
|
I heard several times on the UC in San Diego to avoid display drivers installed by the update service of the Windows 8.1/10 and use instead the “original” ones supplied by the card manufacturer. My question is quite simple: “Why?”.
... View more
09-08-2017
08:42 AM
|
0
|
1
|
907
|
|
POST
|
I think the triangulation method in ArcGIS Pro was replaced by a different one which can’t handle the true vertical polygons. In this case every second triangle has a different winding and that’s why the face culling removes them alternately. The true vertical polygons were always problematic and not fully supported—especially in arcpy and ArcSDE. I can’t provide you a solution, just a workaround: run a “Layer 3D To Feature Class” against your shapefile in ArcScene. It would result a multipatch feature class which rendered always correctly—even in ArcGIS Pro. If you can try to make triangulated or ring-based multipatch surfaces from your cross-section data. Ákos Halmai
... View more
03-29-2017
09:20 AM
|
0
|
0
|
2157
|
|
POST
|
Hi Martina, Your model is probably not georeferenced, and “sitting” somewhere around the origin of the coordinate system, which is usually below the ground, so the model must be covered by the elevation surface. Go to the Table of Contents, double click on the “Scene” on the top of the panel. This would trigger to pop a new window up, called “Map Properties”. On the left side of this window select “Elevation Surface” from the list. On the right panel of the window enable “Allow navigation below ground”. Open up the drop down list on the bottom of this panel called “Elevation surfaces”. There would be only one elevation surface with the following location: http://elevation3d.arcgis.com/arcgis/services/WorldElevation3D/Terrain3D/ImageServer (which is the default). Remove this elevation surface with the red ‘×’ on the right side. Press “OK”, select your model layer, right click on them and select “Zoom to Layer” and voila… Be sure that your layer is in the “3D Layers” group. Ákos Halmai
... View more
02-24-2017
08:52 AM
|
2
|
0
|
4371
|
|
POST
|
I got a building model in kmz with a collada model inside. It was exported from a CAD software called ArchiCAD. Importing a collada via “Import 3D files” results a single (multipart) feature per model. I’d like to make a better visualization in a local scene with the help of the range tool (remove rooftop, slabs etc. in an animated way), but to achieve this I need multiple features—logically or geometrically separated from each other. That’s why I tried the “Multipart to Singlepart”. This tool produced me always a geometrically correct (or at least acceptable) result. However the textures are gone—because the “Multipart to Singlepart” has a no information how to separate logical groups in the model so the textures should be recreated or at least remapped, so the “Multipart to Singlepart” have to follow the rules are mentioned in the help. So this experiment is over, I have to import the model as BIM IFC and every problem would be resolved immediately.
... View more
02-19-2017
09:48 AM
|
1
|
0
|
2135
|
|
POST
|
Explode tool from Editor is not working (multipatch is not supported), Multipart to Singlepart GP drops the textures immediately.
... View more
02-18-2017
09:56 AM
|
0
|
3
|
3409
|
|
POST
|
Simple drones provide usually yaw, pitch and roll values for preliminary orientation. But ArcGIS Pro is waiting for omega, phi and kappa (which is more common in professional photogrammetry). Ákos Halmai
... View more
01-30-2017
11:31 AM
|
0
|
1
|
5081
|
|
POST
|
It is „Cruiserweight” version of Drone2Map. It supports drone, satellite, scanned and digital aerial imagery. It can produce DSM, DTM, ortho, colored and classified point cloud (for example buildings). The images are stored in a mosaic dataset and every processing step is available as a geoprocess. So you can run a whole photogrammetric process from python or Model Builder. These geoprocesses are also available in ArcMap.
... View more
01-28-2017
02:49 AM
|
1
|
1
|
1127
|
|
POST
|
If I’d like enter the optical parameters for a new ortho mapping workspace and I’d like to define the plain coordinates of the principal point of the measuring camera there is no indication for the unit or origin. Actually the adjustment report of an existing ortho mapping workspace helped me a lot: it says “… Position of the Principal Point is referenced to the physical center of the image plain. …”. And there is a table before this statement indicating the coordinates of the principal point is measured in millimeters. It would be quite helpful to indicate these information on the wizard’s GUI. But the real problem arises after that. If the position of the principal point is measured from the physical center of the image plain (center of the sensor) than the coordinates could be either positive or negative. But I can’t enter negative values at all. Same problem at the Konrady (or Brown-Conrady -- as the adjustment report says?) constants. Maybe I misunderstood something (?). Ákos Halmai
... View more
01-27-2017
11:07 AM
|
0
|
1
|
4037
|
|
POST
|
Now, it’s working properly in ArcGIS Pro 1.4 alpha 4. Thanks! It’s a big help for us.
... View more
12-12-2016
04:21 AM
|
0
|
0
|
2329
|
|
POST
|
There’s a variable called inRing, defined as a new List of IPointCollection, where the List is coming from the .NET’s Generic namespace. If you define such a list there is nothing inside, it is an empty container with zero instances in it. It’s not like a predefined array with exact number items. It’s totally empty. First, you should add an object (witch implements the IPointCollection interface) to the list with the inRing.Add method. This would be the 0th item in the list. After that you can add a point. However your solution seems complicated. Applying the IEnumVertex interface on the internal rings is probably easier. Ákos Halmai
... View more
10-06-2016
03:14 AM
|
1
|
1
|
1196
|
|
POST
|
No matter! The “Intersect 3d Line with Surface” is still there…
... View more
10-03-2016
01:40 AM
|
0
|
0
|
1940
|
|
POST
|
There is a “Display” tab on the general “Options” window of ArcGIS Pro 1.3.1. and there are three antialiasing related setting: “Antialiasing mode”; “Text antialiasing mode” and “Enable hardware antialiasing”. The first two can be {None | Normal | Fast | Best}. If I change the first two to “None” (there is no antialiasing), then the third option “Enable hardware antialiasing shouldn’t have effect. But it has, especially on thin lines (typical antialiasing), at least in local scenes. I think I misunderstood something. These option are working separately and the first two is only for software antialiasing?
... View more
10-03-2016
01:33 AM
|
0
|
1
|
2639
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 12-10-2025 02:51 AM | |
| 1 | 08-01-2023 12:17 PM | |
| 1 | 08-01-2023 12:48 PM | |
| 4 | 07-12-2023 01:15 PM | |
| 6 | 08-21-2020 02:18 AM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|