POST
|
This is a question that bugs me and I cant seem to find any good answers. Does it matter where the central meridian/longitude of origin is placed when using Lambert Conformal Conic? I have heard yes and no, but have not found WHY? It seems like it is best practice to have the central meridian, well, central, but could you just have it at the western most extent of the AOI instead of having a false easting? Thanks.
... View more
07-19-2013
11:55 AM
|
0
|
2
|
790
|
POST
|
When you create a python tool, you reference a .py file. The tool has to reference that script to run. So if you want to pick up the tool and take it somewhere else, you have to move the script as well and relink. It seems like it would make sense to be able to store that script in the toolbox somehow. Can you? What good is a tool box if it cant hold all your tools?
... View more
07-19-2013
07:16 AM
|
0
|
1
|
358
|
POST
|
Thanks for the help. What would the syntax of this code look like if i were to make it a python script to import as a script tool with input and output parameters? Thanks.
... View more
06-25-2013
10:58 AM
|
0
|
0
|
526
|
POST
|
Perfect, guys. Thanks also for the other tips. I kept my expression more complex than it needed to be so I could keep everything straight and in case I wanted to scale within a range not quite as simple as the 0-1 I have now. But for the code I will def. construct it the way you laid it out.
... View more
06-13-2013
02:28 PM
|
0
|
0
|
526
|
POST
|
I am trying to move from raster calculator to the python window for my spatial analysis and moving from ERDAS Model Maker altogether. I am already struggling on only my first task. Here I am just trying to 'scale' my raster from 0-1 import arcpy from arcpy import env from arcpy.sa import * #Get Max and Min gridMaxResult = arcpy.GetRasterProperties_management("RASTER1", "MAXIMUM") gridMinResult = arcpy.GetRasterProperties_management("RASTER1", "MINIMUM") #Assign output gridMax = gridMaxResult.getOutput(0) gridMin = gridMinResult.getOutput(0) #Rescale or 'normalize' OutRas = (((Raster("RASTER1") - gridMin) * (1 - 0)) / (gridMax - gridMin)) + 0 OutRas.save("NormalizedRas") I get: Runtime error <type 'exceptions.RuntimeError'>: ERROR 000732: Input Raster: Dataset 0 does not exist or is not supported It is reading the variable correctly (gridMin is equal to 0) but it seems like it doesnt know it is a number. Any advice would help me with this problem and my syntax going forward. Thanks
... View more
06-11-2013
07:43 AM
|
0
|
5
|
3364
|
POST
|
Note that you can use the calculate statistics geoprocessing to to calc the stats and exclude a values such as -32767, however, if you like to use stretch using statistics from current extent (in order to see more detail) then you are out of luck as ArcGIS goes back to including those nodata (-32767) values again in the statistics. Very Frustrating.
... View more
04-08-2013
07:34 AM
|
0
|
0
|
726
|
POST
|
You can make it no color in the symbology, but how do you remove it from the statistics? Elevation grids are usually stretched, but when you have such an outlier that is included in the statistics you will usually just get black and white image.
... View more
02-19-2013
05:00 AM
|
0
|
0
|
726
|
POST
|
Changing the font may be a work-around, but I do not think it solves the problem. We are having a similar issue. The annotation text is rotating with the DDP, but we dont want it to rotate (stream label so we want to follow the stream). This is map annotation. Is there a setting somewhere that tells the DDP what to rotate and what not to rotate?
... View more
07-02-2012
10:08 AM
|
0
|
0
|
501
|
POST
|
I have batch geo-processing that I have to rerun sometimes multiple times with the exact or very similar variables. I love being able to rerun the tools in the results window; however, I lose those results after a month, plus it can be hard to find the specific result I want to run when i do a lot of other geo-processing. Is there a way to save out these processes to be run later? I have dragged & dropped the results into a model to be rerun later, and that works to some extent, but i get some weird issues especially with the batch geo-processing.
... View more
06-13-2012
09:44 AM
|
0
|
2
|
365
|
POST
|
It is projected and buffer is in the same units. It is a very large dataset so I had it in a model that clipped it first then buffered. I took the intermediate clipped results and buffered them separately and it seems to have worked. But i seem to remember it failed once before even when I did it this way. Anyhow, I got the result I wanted and dont have time isoloate the root problem. Thanks for you input.
... View more
01-18-2011
06:27 AM
|
0
|
0
|
273
|
POST
|
I am buffering a large polyline dataset (streets). Very often when I run the buffer I get large polygons that are created as if the buffer was large enough between the two lines to create one polygon. The buffer, however, is less than the distance it would take to close off the polygon. The picture will make more sense. The red is the original polyline. Notice the large closed off polygons. It seems like there are times when it runs without this issue. Any thoughts?
... View more
01-17-2011
04:35 PM
|
0
|
5
|
577
|
POST
|
Note that terrains also use TINs. There could be several variables that are causing the differences that you are seeing including the terrain pyramid level or interpolation method you are using when going terrain to raster. There are no major flaws in a normal TIN or a Terrain so you should probably evaluate the two final datasets instead of the tools or methods. You might want to get benchmarks and find out which dataset has the higher absolute accuracy and then make up your mind. You could compare the datasets at difference steps in your process to find out when the differences are introduced. Finally, you might also do some sample volume calculations to see if the differences are acceptable for your application. And yes we have had luck relying on terrain, but in the workflow you described there are several processing steps with several variables so you never know when error might get introduced.
... View more
08-18-2010
02:48 PM
|
0
|
0
|
420
|
POST
|
I am not sure I understand what you are exactly trying to do, but a spatial join is a good way to aggregate and summarize point data within polygons. By default you can run some basic statistics (Sum, min, max, etc) on all numeric fields when you join the points to the polygons. If you want to select only certain fields to summarize you can spatial join the polygon to the points then run summary statistics on the census track name field that was joined over. You can do both of these via geo-processing so you can stick them in a model and just have it be one step.
... View more
08-18-2010
02:23 PM
|
0
|
0
|
140
|
POST
|
When creating large terrain over many areas, it is not always feasible to have a single elevation data source. For flood studies in particular, you could have lidar, ground surveys and perhaps even USGS DEM. All of these can be incorporated into an ESRI terrain, but there is usually overlap. You can using geoprocessing to eliminate the overlaps (erase, clip, etc.), but this can be time consuming and difficult (especially with lidar multipoints). Is there any way in within the ESRI terrain to eliminate the overlaps by perhaps prioritizing features within the dataset. A water resources example: Build terrain in the channel based on survey mass points (this would either be defined by the data extent or a user defined extent mask), build terrain outside that area using the lidar mass points (maybe the floodplain extent), then use the USGS DEM for the terrain outside of the first two for the remainder of the watershed. I havent found any prioritization or extent options in ESRI terrain. Is it available or are there any easy workflows that could accomplish the same goals?
... View more
08-18-2010
02:03 PM
|
0
|
1
|
271
|
Title | Kudos | Posted |
---|---|---|
1 | 04-24-2023 09:05 PM | |
5 | 04-28-2023 11:46 AM | |
1 | 03-29-2017 10:25 AM | |
1 | 07-28-2016 08:23 AM | |
4 | 04-13-2015 10:16 AM |
Online Status |
Offline
|
Date Last Visited |
02-28-2024
12:14 AM
|