|
POST
|
Ben, Those are good questions, and I think doing an accuracy assessment of the variation in the years of Landscan would be a great thing to have, and could probably stand up as its own publication. I'm not aware of any specific group which has done this, and in the past when I've worked with Landscan we've made some rather crude assumptions when looking at the data over time. I don't think this has been done before, in part because the Landscan data has a cost, and is less frequently used in analyses than its free counterparts like CIESIN's gridded population datasets. I haven't done time-effects models, but I imagine that with some careful modeling this could be done meaningfully. You may want to look more into the existing literature published by users of Landscan to see if others have tried similar approaches. If you're only interested in particular parts of the world, you may be able to incorporate census data to predict expected differences and account for the error in Landscan. Overall, it sounds like a great project, but I'm not aware of anyone who's done this already. cheers, Shaun
... View more
03-28-2014
10:01 AM
|
0
|
0
|
651
|
|
POST
|
It looks like it might be a 3D localization file produced by TOPCON's TopSURV, as it's documented in their manual. Probably your best bet is to try using the tools they provide and see if it can be converted to something useable outside their software. It may also be a text file, but I'm not sure what the values represent -- probably they can help in interpreting what it contains and how it can be applied in a GIS context. cheers, Shaun
... View more
03-28-2014
09:49 AM
|
0
|
0
|
2857
|
|
POST
|
Most of the tools for creating contours assume you have an elevation dataset, like a raster or a TIN, which the contour lines can be derived from. It is possible to interpolate between the existing contours you have, but fairly tricky to do. The approach Mark mentions above is probably your best bet. Right now, you have contours which are at different heights, so each line contains the height (or depth) of the values along it. If you convert those lines into points, you can interpolate a surface, and make a "fake" DEM which includes the data that you do have (from the contours). Then, you can use that new raster DEM to create contours at the resolution of your choosing. Note that these will be interpolated, and may not be accurate. So, taking your contours, this would look something like: Data Management Tools > Features > Feature Vertices to Points Spatial Analyst Tools > Interpolation > IDW (there are many other approaches to interpolation, IDW is perhaps the simplest). Spatial Analyst Tools > Surface > Contour cheers, Shaun
... View more
03-28-2014
09:24 AM
|
1
|
0
|
3147
|
|
POST
|
Have you tried the Surface Volume tool in 3D analyst?
... View more
03-28-2014
09:02 AM
|
0
|
0
|
594
|
|
POST
|
Hello Joe, Yes, you can perform a Viewshed analysis which should do what you're looking for. cheers, Shaun
... View more
03-28-2014
08:51 AM
|
0
|
0
|
804
|
|
POST
|
I don't believe that Hawthorne has yet released a version of GME compatible with ArcGIS 10.2 -- the site shows 10.1 as the latest version supported. Jake Wall has a package explcitly for movement ecology, ArcMET, and it does support MCP, but I'm not sure if it's yet available for 10.2 either -- you might want to check with him. Generally, the third party extensions from the scientific community aren't lock-step with the latest releases, as it can take a while to have enough new users on the platform to justify the time required to build a release for that version. cheers, Shaun
... View more
03-28-2014
08:36 AM
|
0
|
0
|
1296
|
|
POST
|
James, Assuming 32bit values, you're still only looking at something like 268MB (236*552*540*4 bytes) of data, which should fit into memory without a problem. Doing that for both your rasters and points would be a good place to start as Curtis mentions, as your sampling has to iterate over all points and rasters which isn't particularly fast. Another option that would take more work is to stack the rasters using multidimensional arrays, such as with NumPy or NetCDF. Then, you can pull out the values of all 540 rasters by sampling a single vector (all rasters at one point) which should greatly improve performance. cheers, Shaun
... View more
03-06-2014
10:09 AM
|
0
|
0
|
1263
|
|
POST
|
Rosita, In my own toolboxes, I have these lines: local_path = os.path.abspath(os.path.dirname(__file__))
sys.path.insert(0, local_path) That will get the path of the current file (in this case, the .pyt) and prepend it to Python's system path. cheers, Shaun
... View more
03-05-2014
08:14 AM
|
0
|
0
|
1294
|