POST
|
I am currently working with some image data which originates from PDF documents (plots), which have been georeferenced using Google Earth as images within kmz files. I have noticed that if I import these kmz layers into ArcGIS, the georeferencing goes way off. Is this something to do with the way the two programs store/deal with georeferencing of images? The issue seems to be related to the rotation of the image; images rotated further from 'up=north' have worse issues, with unrotated images more or less unaffected. Both the rotation and dimensions of the image are affected by this. Original image: Google Earth: Imported in ArcMap: Has anyone else encountered this problem? I can't find anything referencing a possible cause; the images are imported with a WGS84 GCS, and forcing this to change doesn't affect it by enough (or in the right manner) to explain it. It's not too difficult to fix the georeferencing, but I would rather import them correctly in the first place! Cheers Murray
... View more
03-14-2018
08:59 AM
|
0
|
0
|
612
|
POST
|
Erin - thanks for the info; I'll have a look into the geoprocessing option next time I get a chance. Javier - thanks for the reference; I have read through that, and the STA threading methods it explains still seem very slow compared to single-threaded... I'll read through it more thoroughly though and see if there's anything I haven't tried. Cheers Murray
... View more
11-10-2014
02:20 AM
|
0
|
1
|
859
|
POST
|
I'm currently working on an Add-in for ArcMap 10.0. As part of this, I need to interrogate a geodatabase containing point feature classes, to see which of these points lie within an input polygon, and sum various attributes associated these relevant points. As the geodatabase is very large, this can take a fair while (~few minutes). Obviously making ArcMap hang while this calculation is taking place is not ideal, so I'd like to have the geodatabase access & interrogation take place in a background thread. Unfortunately, this seems to increase the calculation time by a factor of ~5-10 - seemingly because all the calls to COM components are getting held up somewhere. I've tried a number of methods to speed things up, but with no success (BackgroundWorkers, Threads with the STAThread attribute, Control.BeginInvoke methods...); with the exact same code, it takes several times longer in a background/non-UI thread. Does anyone have any advice on how to make ArcObjects access work with any degree of speed when not run in the UI thread? Any insight would be much appreciated; I have run out of ideas!
... View more
11-07-2014
11:14 AM
|
0
|
4
|
4038
|
Online Status |
Offline
|
Date Last Visited |
04-23-2023
07:29 PM
|