|
POST
|
Hi Simon, I guess what you want to do can be achieved with a combination of 1) Remap Function To be able to add a Attributed/Labeled Classification, you need to make your data display "integer classes" - basically the "numbered Count of classes" I mimicked your values in the first few classes above. You could also use a table for this. Please read the Function help about upper- and lower Boundaries, ... Make sure to properly define NoData! Once you have done that, your now unique classes can be "labeled" and "colored" using the 2) AttributeTable function Now here is where ArcMap and Pro do make a big difference: In ArcMap you need an attribute table comparable to what used to be a RAT (Raster attribute table) in old times (see help). This is ArcMap: As I remember it being tricky to create a proper AttributeTable for ArcMap. Here what it needs to look like: Keep in mind: All fields should be there exactly like this The "Value" field is link to the output classes of the Remap function The "ClassName" will be your visible label In "Red", "Green" and "Blue" you have to define your symbol colors The values in the Count field dont matter at all! I attached this sample one (in a zipped fGDB) that you can copy and modify. In Pro things have improved A LOT: You can either use a table, or just type in your definition in a UI like this (one of my datasets - 4 steepness classes in an elevation dataset😞 Doing things right, you will get something like this (the result of the above AttributeTable settings in ArcGIS Pro TOC): So - again from my usecase and from Pro RasterFunction Editor - the whole process chain MIGHT look like this: All this is way more comfortable in Pro - check it out! I also recommend you to do this: 3) Dont forget to set the Source type of any raster where you apply AttributeTable to "Thematic" .. naturally only if you dont use many different function chains or this is to be the default. Regards Guenter
... View more
02-07-2019
01:42 AM
|
2
|
2
|
3880
|
|
POST
|
Pleasure, but later I ralized it might not be the answer you were looking for: I answered to "download data" - whereas if you ask for the simple "screen export" function in ArcGIS Pro/ArcMap ... there is no way of disabling this: It basically takes the image already delivered to the client and saves it as a "picture" ... and this cant be disabled. So I hope the first question was what you really needed Guenter
... View more
02-07-2019
12:55 AM
|
0
|
2
|
2404
|
|
POST
|
Hi, I assume this is the same answer I gave a day ago to another question: Have you properly set the MosaicDataset Property "SourceType"? Your description indicates that your desktop tries to stretch the data. You can avoid that by setting the source type property from its (assumed) default of "Generic" to "Processed". This will let ArcGIS assume the data is like you want it to be and when adding to the TOC no Stretching will be applied. Guenter
... View more
02-05-2019
05:52 AM
|
1
|
2
|
1672
|
|
POST
|
Hi Wan, sure you can disable download of data. You can do this starting with the MosaicDataset you created. In the "Defaults" section of each Mosaic, there is if you set this to 0, you disabled Download on the Mosaic Level. On the Service Level, the same capability can be set to "limit" what you might have set on the MosaicLevel. The "Service Properties" in the "Imaging" section have a Operation list to allow/disable. Download is one of them: So even if you allow download on the MosaicDataset level (say so local users using the MosaicDataset have access to the files behind it), you can disable the capability on the service level. Hope that helps! Guenter
... View more
01-25-2019
04:12 AM
|
2
|
4
|
2404
|
|
POST
|
Sorry Cara, now that you mention again, I see the word DEM in your original post - no Colormaps for DEMs 🙂 Have you re-calculated the statistics for the resulting raster after you merged them? And please also make sure to set the property for the raster type to elevastion so the stretching applied is min-max by default. Guenter
... View more
10-05-2018
10:14 PM
|
0
|
2
|
5138
|
|
POST
|
Cara, I assume by reading your rasters have colormaps - so individual values assigned to individual colors/labels. By what you write, the different rasters dont have identical colormaps, though. When you turn 3 rasters into one, there can only be ONE colormap. Thats what the "mosaic_colormap_mode Property of the tool is meant to control. If you didnt set it at all, the first colormap coming up in any file will be used for the output. Try "match" for a better result, if you have more than one colormap. But this has limits: If within many colormaps the same value is assigned to different classes, this will fail (say water is 8 in one dataset and in another forest is 8). Best would be to analyze this in advanced. When needed, a mosaic dataset can be created that first "homogenizes" your datasets using a raster function on each raster, then assigns the AttributeTable you want to the result ... and then you can still export 🙂 Let me know if you need assistance - but then I#d need the data Guenter
... View more
10-05-2018
12:42 AM
|
1
|
4
|
5138
|
|
POST
|
I am/we are happy to assist - but need more information. Best what you use as frame- and camera table, input data, ... Guenter
... View more
09-24-2018
03:39 AM
|
0
|
6
|
4690
|
|
POST
|
Dan, my answer is probably misleading: Everything IS in there As part of the OrthoMapping Workflows As tools in the GP environment (Raster type frame camera, calculate tie points, build block adjustment, ... ) As configurable tools (calling GP tools) in MDCS (Also as OrthoMaker in Server/Image Server lately - this is for Drone data only) The part people sometimes need assistance with is to figure out how to get their data into the Frame and Camera tables, especially if they do not get full calibration report, specs, ... so it is more about workflows and some additional know/how - experience. As Cody states above, some of this is going to be wrapped up and published to ease the use in MDCS. Guenter
... View more
09-19-2018
05:48 AM
|
1
|
1
|
2021
|
|
POST
|
Carsten, let us know if you run into any problems setting this up. We have done that often and can assist. We also have MDCS scripts that assist. Guenter
... View more
09-19-2018
05:34 AM
|
0
|
3
|
2021
|
|
POST
|
Carsten, sure this can be done with scripting, python. There are two ways for you to do it. The 'hook-in' is the same in both cases: The 'Add rasters to mosaic dataset tool' has the Raster Type as a parameter. This Raster Type can be any raster type coming from a *.art file. To create the art-File, you follow excactly the workflow you describe above for a manual add, but then - in the General Tab of the Raster Type Properties - save your settings (including your camera table) into a seperate art-File, which now will be your custom raster type: Specify this in your script - and there you go. If you look for a very convenient, powerful and flexible way of defining and running workflows like these in the future, please check out (this is option 2) MDCS (GitHub - Esri/mdcs-py: MDCS is an acronym for Mosaic Dataset Configuration Script and is the entry point to a collection… ). A great framework for mosaic dataset related tasks. Are you in Europe? I'd be glad to discuss this with you - we have many samples and good workflow recommendations here at Esri. Regards Guenter
... View more
09-13-2018
08:01 AM
|
1
|
6
|
2021
|
|
POST
|
Valid question, Have no details there. And no complete answer. Data structures are completely different in the stores we can access – maybe someone else will comment here
... View more
06-29-2018
05:59 AM
|
1
|
3
|
3905
|
|
POST
|
Enrico, the ImageService has all information to use time - as you clearly state - but it prevents users to enable time slider functionality by not having "use time" activated in the Service properties to avoid "un-aware" use that might result in senseless processing and searches blocking other users from proper access. The new Imagery Apps now work with another method and selector. Try to use for example the new: There you can easily configure the layer to give you a dropdown of available dates for a selected area ... Regards Guenter
... View more
06-29-2018
02:59 AM
|
2
|
8
|
3905
|
|
POST
|
Hi Blake, sounds like you are very much following the right track already. What are you searching for: Performance on the existing data? Have you checked Optimize Rasters? Workflow verification, improvements or automation? Are you aware of ArcGIS Imagery Workflows | ArcGIS and MDCS: ? Have you thought about Stereo as a use now possible with ImageAnalyst and your data? see: Introduction to stereo mapping—ArcGIS Pro | ArcGIS Desktop The new Imagery WebApps released in April?: see here Hope this helps Guenter
... View more
06-25-2018
03:02 AM
|
1
|
0
|
1286
|
|
POST
|
Blake, your way to go is what you describe you already do 🙂 Is the question about the workflows to keep this as easy as possible?, make different interesting products from the data without duplicating it?. If not already done, have a look at the published Imagery Workflows: ArcGIS Imagery Workflows | ArcGIS They give you best practice advise, scenarios, ... and will introduce you to the powerful Mosaic Dataset Configuration Scripts framework (MDCS) By the way: From now on, If you have your Area flown, make sure you get ALL the original imagery with its overlap - use these Stereo Mapping workflows described by Cody Benkelman, and be able to see your data in Stereo with ArcGIS Pro and the Imagery Extension!
... View more
06-25-2018
02:51 AM
|
0
|
0
|
1286
|
|
POST
|
Andreas, what strikes me most in your question is the plan to serve out a NetCDF based Mosaic (plus additional Layers) to a service. Though NetCDF is supported as an input, be aware that the intention of NetCDF is not to be accessed in parallel by potentially many users. Access to NetCDF is basically meant to be on a single user base. In addition the indexing of Rasters in NetCDF is not optimized and will always repeat the "query" you defined to access slices in the dataset. Be aware of that. A service created with the intention to be most performing and server-optimized for sure would not use NetCDF as the input format. Another conceptual issue in your statement "add to my map" ... and then "serve out as Image Service". Image Services are created from MosaicDatasets, not from MapDocuments. You can set up a Mosaic with many NetCDFs or one NetCDF multiple times and then differing settings - and then make sure that via Definition query, RasterFunction, ByAttribute Mosaicing, ... you can dynamically "switch" what is displayed ... When loading it into a map document or when using it as a layer in a WebMap. Best to go back to Esri Germany (Ralph) with that task! Best regards Guenter
... View more
04-26-2018
09:19 AM
|
1
|
2
|
2007
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 09-14-2023 12:12 AM | |
| 2 | 04-27-2020 01:37 AM | |
| 1 | 08-03-2021 04:43 AM | |
| 2 | 02-07-2019 01:42 AM | |
| 1 | 10-05-2018 12:42 AM |
| Online Status |
Offline
|
| Date Last Visited |
12-04-2025
05:09 AM
|