Latest Contributions by CodyBenkelman

‎05-31-2018

This is typically a problem with the UnixTimeStamp data. Since you said the same happened with the tutorial data, it is possible you did this: 1) open metadata csv file in MS Excel 2) save file 3) try multiplexer If you do the above without adding step 1.a.) BE SURE TO SET THE TIMESTAMP FIELD FORMAT FORMAT TO "NUMBER" then MS Excel converts the data to scientific notation and effectively corrupts your UnixTimeStamp. another possibility is if your UnixTimeStamp records are milliseconds vs. microseconds. It needs to be a 16 digit number (but this should not have been a problem with the tutorial data). If that does not work please upload your metadata file. (I don't need the video) Cody

‎05-31-2018

This could be your answer. The PNG format tiles are not compressed. We recommend using "mixed JPGPNG" format, which uses JPG for all tiles *except* those that have pixels labeled as transparent. Using any compression method (JPG, ECW, MrSID, others), if a pixel is 0, the compression may change that to a 1 or a 2 (still very dark black). If 0 is supposed to be treated as transparent, the compressed nonzero values will no longer treated as NoData in ArcGIS (a.k.a. transparent). For those (typically few) tiles with NoData values, they'll be written as PNG, but the majority will be JPG. Try reprocessing a SUBSET (not the entire dataset!) and use format = JPGPNG. If you have a lot of NoData pixels within the interior of your dataset, this may require further discussion.

‎05-17-2018

With the Image Analyst extension in ArcGIS Pro 2.1 (or later), non-orthorectified and suitably overlapping images with appropriate metadata can be viewed in stereo! This stereoscopic viewing experience can enable 3D feature extraction. See more information at http://esriurl.com/stereo. If your organization has a collection of images and you’d like to use the stereo viewing capability in ArcGIS Pro, where do you start? The key questions are: What type of sensor collected the data, and What orientation data do you have along with the images? In order to display images as stereo pairs, ArcGIS must have detailed information about the location of the sensor (x,y,z) as well as its orientation – and this is unique information for every image. Information about the sensor (typically called a camera model or sensor model) is also required. There are a few conceptually simple cases, although each has important details to follow within its own workflow and documentation. If you have two overlapping satellite images, you can go directly to stereo viewing. If you have a collection of satellite images, you can build a mosaic dataset and ingest the images using the specific raster type for that satellite, run the Build Stereo Model geoprocessing tool, then proceed to the stereo view. The raster type for the satellite reads the required orientation data. If your imagery came from a professional aerial camera system: If you have an output project file from aerotriangulation (AT) software (e.g. Match-AT or ISAT), ArcGIS includes raster types which ingest the orientation data for you, so this is similar to the satellite case: build a mosaic dataset with the proper raster type, Build Stereo Model, and proceed to stereo viewing. If you have a project file from AT software not currently supported, Python raster types are under development for additional sensors e.g. for the Vexcel Ultracam. For more information, watch for announcements on GeoNet or on http://esriurl.com/ImageryWorkflows. Alternatively, if you have a table of camera and frame orientation values, see the next bullet. If you have a table of data values representing the exterior orientation as well as a camera model (interior orientation), you will build a mosaic dataset and ingest the images using the “Frame camera” raster type. This document (http://esriurl.com/FrameCameraBestPractices) provides a workflow for how to prepare the necessary camera & frame data, then configure the mosaic dataset. The workflow references ArcGIS Help documentation (http://esriurl.com/FrameSchema) to provide further details that may be necessary. If you have scanned film but without the results of AT software, refer to the FrameCameraBestPractices. With ArcGIS Pro 2.1, some values may have to be estimated, and the positional accuracy may not be optimum. ArcGIS Pro 2.2 (and later versions) support fiducial measurement. If your imagery was captured using a drone, you will need to use photogrammetric software to generate the camera model and orientation data. If you process your drone imagery using Ortho Mapping in ArcGIS Pro Advanced (see http://esriurl.com/OrthoMappingHelp), after the Adjust step is completed, the Image Collection mosaic dataset will be ready for viewing in stereo (after Build Stereo Model). If you are using Drone2Map, please see this item ArcGIS Online http://esriurl.com/D2Mmanagement to download a geoprocessing tool which can ingest the images into a mosaic dataset. For those interested in trying an example, a downloadable sample is available in this item on ArcGIS Online: http://esriurl.com/FrameCameraSample.

‎04-02-2018

Rebecca see Export Mosaic Dataset Paths—Data Management toolbox | ArcGIS Desktop and note you can run this from Catalog by right clicking on the MD I haven't re-read the whole thread above but if there are still outstanding issues from the original list of questions, can you summarize and let us know? Thx Cody

‎02-23-2018

Leo Web AppBuilder does not publish, so I don't understand what you are trying to do. and no, it also does not reproject. However if you have an image service published (through image server) from a mosaic dataset, web appbuilder can request any (known) projection, and the server will reproject on the fly. Can you start a new thread and explain more completely what you have, and what you're trying to do? Also let us know what version of ArcGIS Desktop (ArcMap? ArcGIS Pro?) you are using Cody B

‎02-17-2018

Cameron the *.ovr file is a reduced resolution view ("overview" or "pyramid") of an original file - you may want to double check in the folder (if you got it?) to see if there's a *.tif or other file with the same basename. The *.ovr file will be smaller in size but not the full resolution of the original - not sure if that matters (but I wonder why you were given the *.ovr instead of the original). But that is somewhat academic, hoping to inform you. For a quick answer to your immediate need: try making a copy and changing the extension to *.tif. The *.ovr format is fundamentally tiff inside and this may simply work, although I expect the *.ovr will contain multiple resolutions within it, and I don't know for certain if Autocad will handle it properly. If the above does not work and you have ArcGIS, try reading the *.ovr --> renamed .tif by loading it into the map. If it appears black, apply a stretch to see if you have good elevation values. Let us know if any of these instructions are too sparse. also let us know if you have ArcMap or ArcGIS Pro, and what version. Sorry I won't be any help with AutoCAD. Cody B.

‎02-08-2018

John There's a GP tool from long ago that will create mosaic files on disk from multiple inputs, but that's not a Mosaic Dataset which is our modern database structure for accessing and processing imagery on the fly, without duplicating data in derived image products. If you aren't familiar, see What is a mosaic dataset?—Help | ArcGIS for Desktop Note the Mosaic Dataset is for data that already includes georeferencing information, or adequate camera/satellite model and image metadata for on-the-fly orthorectification. For raw single frame drone images, a photogrammetric workflow for processing (to create orthomosaics, DSMs, point clouds & more) is available in http://esri.com/drone2map which is a standalone app (does not require ArcGIS). It is sold at a price that is very competitive to similar tools in the marketplace (with numerous points of direct interface with ArcGIS & ArcGIS Online). Or, if you have a current license for ArcGIS Desktop, ArcGIS Pro 2.1 includes a drone camera workflow in the Ortho Mapping tools (built into Pro, no add-on cost). There is a workflow for centralized data management of massive numbers of Drone2Map projects in the imagery workflows. See the free script at http://esriurl.com/D2Mmanagement For drones capturing video, we have the Full Motion Video add-in for working with geotagged video, in both map space or with GIS features projected into the video. http://esri.com/fmv. (Note this isn't just for drones - it was originally created for professional/military grade video systems but can support drone video through a postflight geoprocessing tool called the "Video Multiplexer") ArcGIS has quite a bit to offer for drone imagery, and more is coming. Cody

‎02-07-2018

John this makes sense. I'd encourage you to try doing all of this in ArcGIS Pro. (If you don't have Pro now, you can get a trial copy) It may be possible that a change in your workflow could output 16 bit integers from Pix4D, but if you have 70 surveys you don't want to have to reprocess all of those through Pix4D. You should not need to convert to 16bit. If you creating a mosaic dataset of all the imagery, you can treat it as one logical collection. The mosaic dataset can also combine any desired bands into a multispectral view (e.g. 4,1,2 for color IR, 4 & 1 for NDVI, 5 & 1 for red-edge-NDVI, etc.), and this is done instantly via a function, not a process you need to run and create more output files. For the classification, you or colleagues can use advanced classification tools and wizard in the Image Analyst Extension or Spatial Analyst. (also available as a free trial for ArcGIS Pro). This can use any bit depth, or you can apply an arithmetic function prior to classification to convert (on the fly) to 16 bit. If you really need to proceed with converting to 16bit, then you can use OptimizeRasters. Download from http://esriurl.com/OptimizeRasters and use following command c:\Image_Mgmt_Workflows\OptimizeRasters\OptimizeRasters.py -config=Imagery_to_TIF_float2int.xml -input=c:\tmp\Q\inputdirectory -output=c:\tmp\Q\outputdirectory (See http://s3.amazonaws.com/ImageManagementWorkflowsTeam/OptimizeRasters/Imagery_to_TIF_float2int.xml )

‎02-06-2018

John It always helps if you can give us a complete story. e.g. You did what many do NOT do (told us the version are you using), but what are your overall objectives? What is the data? Why are you converting thousands of files? At risk of changing the subject, I am concerned any time I see questions about "processing large # of images" and "creating a lot of outputs". That's especially true in a case like this, where you're starting with floating point data (where I presume the pixel value is some absolute measurement - I would have guessed orthometric height although your range above "0.0241 to 0.0674" sounds odd) and converting for some reason, to generate files with 16 bit values that now do NOT represent the true data values but must have some legend or lookup table if users ever need to determine the (approximate) original values... Are the end users for these 16 bit files using some other software? Have you considered putting all into one single mosaic dataset and applying a raster function to rescale from F32 to U16? Your project might be completely done in an hour... Cody B.

‎02-05-2018

Robert If you start at http://esriurl.com/imageryworkflows and then look for this link "Check out our ArcGIS Online Group for more tools" in that Group you will find a workflow for Historical aerial photos (direct link http://www.arcgis.com/home/item.html?id=d1b4e3afeda7405fb34578207f0ad256 ). The photo index is a valuable input, to provide ArcGIS with an approximate position for the camera location to capture each image. By following that workflow and inputting the metadata from the photo index into the "Frames Table" you should be able to position each image on the ground, but note the accuracy will depend on whether you have other metadata e.g. for the camera model. Quoting from the documentation of the Historical Imagery workflow: This workflow uses the Mosaic Dataset within ArcGIS (and the Frame Camera Raster Type) to manage and rectify scanned images (on-the-fly) to approximately georeference them. The Mosaic Dataset will reference the scanned image files in their original format and apply approximate orientation parameters to perform the image georeferencing. If desired, the user has the option to refine the orientation parameters as required to achieve better accuracy, but be aware the resulting product should not be considered an orthorectified image unless full aerotriangulation is applied, and an accurate DEM is used. Cody B

‎12-13-2017

Rebecca We are working on a reply, but before this thread gets any longer, can you clarify if there is any relationship between the 3 imagery folders, and again between the 2 DEM folders? Also, is everything in one single folder truly one single collection, or (for example) does the RGB folder include images captured at two different times, and/or two different resolutions? I thought you had 4500 files total, and all 5 folders were distinct and unrelated, but your last reply says "about 4500 each" so unless that number is just a coincidence, I'm wondering if these files are all one big project. If the RGB, CIR, and PAN folders are three versions of imagery from the same project, and your Ellipsoidal and Orthometric DEMs are two versions of the same data, I would likely recommend you take a step back. We may not be at the proper starting point. Cody B.

‎11-03-2017

Sean My expectation regarding identifying the mining areas is that you're going to need to digitize manually (as Dan suggests), but it IS possible that you MIGHT have luck with our segmentation tools to train it to find the appropriate symbology ("texture") - although best case I think you'll still have manual cleanup to do, and that may take just as long as manual tracing of the mining regions. I don't believe you'll have any luck with standard classification tools which focus on spectral content, not texture. (could you upload a screenshot of one of the areas showing "mining" and "non mining" so we can advise further?) However, I want to redirect you with regard to the mosaicking. Please read about the mosaic dataset. You do not need to convert from SID to TIFF, and you should be able to create mosaics in minutes, not days. (they may not be perfect in the first 5 minutes, e.g. you will still have the collars to deal with, but if you can define a table of the easting & northing or lat/long of the collar on each file, that can be imported into the mosaic dataset to clip and hide the collar). This will be a "dynamic" mosaic you can use in ArcGIS to test the segmentation or manual digitizing. Cody B

‎10-31-2017

Sean My apologies. When I inserted those links, I edited the visible text but didn't realize the hyperlinks were still going to an internal AGOL organization. Please try them again - they should be accessible to anyone with an ArcGIS Online account. No, maps are not suitable input to classification. Image classification is intended for imagery, not the thematic representation you'd find in a map. I've never heard of anyone attempting it, but I'm confident you won't get results that make any sense. Separate from the issue of mosaicking maps and removing the collars, or accessing image services, perhaps we can help you better if you explain your objectives, and ideas on how you're planning to approach the problem. Cody B.

‎10-29-2017

Sean have you looked at the historical USGS topo maps available as free services through ArcGIS Online? (ArcGIS Online subscription required) http://www.arcgis.com/home/item.html?id=40109482569c4bcc873dfa7fec7c167e There are tens of thousands of maps mosaicked and ready to use, at different scales and from different dates... http://www.arcgis.com/home/item.html?id=40109482569c4bcc873dfa7fec7c167e http://www.arcgis.com/home/item.html?id=be337c042cd4476e9ba29d4c0e26b5fb many more If you really need to create your own mosaic, I'd use a Mosaic Dataset, and define the seamline for each map using the extents of the map area (inside the "collar"), then mosaic method = seamlines will hide all the collars. This will be a dynamic mosaic, allowing you to expose the collar of any selected map if desired. If you really need to output a new file, my first question is "Are you sure?", but you can export or cache the dynamic mosaic to persist a static image. http://esriurl.com/ImageManagement --> look for the Scanned Maps workflow.

‎09-19-2017

Peter Agreed with Dan, you should be using the full 16 bit range, not scaling to 8 bit. The simple difference ratio equation you show NDVI = (IR-R)/(IR+R) IS the equation for NDVI. It does not have any requirement to be 8 bit (0-255) so you should use the full range of values available in the data. Second, unless this is purely an exercise for you to learn more Python, why start from scratch? ArcGIS can immediately calculate NDVI for you - let us know which version you have (ArcGIS Pro 2.0.1? ArcMap?) and we can advise for how to do it. Note the NDVI tools within ArcGIS may automatically apply a color ramp, but you'll presumably want the "scientific" version which outputs the raw floating point values. NOTE - this will give you pixel values from -1.0 to +1.0, and you'll presumably need to rescale/convert those for VIEWING the data - but if you're attempting any quantitative analysis, you'll want to do that work with the floating point values for best accuracy

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by CodyBenkelman

Re: Problem with Full Motion Video ArcGIS. Empty output file.

Re: Image Service File Size is Very Large

Preparing imagery for stereo viewing in ArcGIS

Re: Mosaics and Image Server services….source vs derived vs reference…Advice requested

Re: File size increase when projecting raster

Re: Struggling to convert a raster file into CAD

Re: Converting 32-bit TIFF to 16-bit erroneous values

Re: Converting 32-bit TIFF to 16-bit erroneous values

Re: Converting 32-bit TIFF to 16-bit erroneous values

Re: What is PhotoIndex and what does it for and how do I use it ?

Re: Mosaics and Image Server services….source vs derived vs reference…Advice requested

Re: Easy way to remove collars from GeoTIFF of USGS Topo?

Re: Easy way to remove collars from GeoTIFF of USGS Topo?

Re: Easy way to remove collars from GeoTIFF of USGS Topo?

Re: Calculating NDVI from Landsat 8 USGS Tiles

Be one of the first to test and shape the future o...

Drone2Map v2026.1 has been released!

How to Migrate Oriented Imagery Catalogs to Orient...

New Release of ArcGIS Online - Are you looking for...

Oriented imagery classic will be retired soon!

Esri Forestry Group (EFG)

User Community for Geospatial Authorities (UCG)

UCG-WG2 Remote Sensing and GeoAI

Elevation Data

Drones, UAVs, UAS, and RPAs