|
POST
|
I have an area I would like to map. The extent of the area is approximately: -147 to -141 and 69.5 N to 70.5 N (North East Alaska). It falls right between two state plane zones and also between two UTM zones. For now, I just took the Alaska Albers projection and changed the central meridian to -144 and set the standard parallels to 69.6 and 69.8. So, I am wondering if this is the best choice. Should try and tweak a UTM zone? Or maybe a Lambert projection? I am just trying to pick something that will minimize distortion and be focused on the area of interest. Thanks, Forest
... View more
02-05-2018
01:45 PM
|
0
|
3
|
1356
|
|
POST
|
Thanks for taking the time to reply Abdullah. I too noticed the table name change in the dialog. Unfortunately changing it does not affect the query error behavior. \ It is also weird because the fully qualified name for the transformer fields should be ARCFM8.Transformer.{field name}. And not ARCFM8.Transformer_Transformer_FM.{field name}. Even very simple queries fail...
... View more
12-04-2017
10:46 AM
|
0
|
0
|
975
|
|
POST
|
I have a query that is failing after a join. I have greatly simplified the query to try and pin down the problem. We are using a SDE source with in Oracle 12c. The cut down query... exists (select * from ARCFM8.Transformer) Working fine before the join.... Not working after the join.... Suggestions?
... View more
12-01-2017
05:34 PM
|
0
|
2
|
1384
|
|
POST
|
This worked well in a test run: http://www.cartotalk.com/index.php?showtopic=5401
... View more
09-22-2017
03:07 PM
|
1
|
0
|
1654
|
|
POST
|
Ya, looks like that has to do with setting up a "default" anno style before you place it. I have also tried selecting a bunch of them (30 or so) and updating them with the Attribute panel; however, only one is updated. Furthermore, the far end of the leader is "reset" (i.e. the length of the leader is reduced to zero). So one must drag the leader back to the feature that the anno is referring to. I fear that even if I do find a way to mass update the annotation I would still need to drag all the leaders back by hand....
... View more
09-22-2017
09:52 AM
|
0
|
0
|
1654
|
|
POST
|
I am working with a "map book" that has a large number of call outs (~3000). We have a request to change the line color and weight for the leaders. The annotation is in a SDE feature class. Is it possible to do this change in bulk? ArcGIS 10.1 Thanks!
... View more
09-21-2017
04:14 PM
|
0
|
5
|
1911
|
|
POST
|
There are a lot of ways to address this. One approach is to open a blank mxd. Then right-click on the data frame ("layers") and open the data frame properties. On the coordinate tab select your state plane zone. Then add your table and display xy data. You can add your imagery to the mxd at this time (if you want the map to be in your state plane zone) and it should reproject fine. It will probably ask you for a transformation. I think NAD83 and WGS84 are very close in that part of the country so, it could be ignored (depending on what you are trying to accomplish). I don't know the right transformation off the top of my head for Georgia.
... View more
06-01-2017
01:47 PM
|
0
|
1
|
2547
|
|
POST
|
Yes, we are on 10.4. And your assumption regarding the roll-up of other fields is right. Thanks again for all your input. I got a lot out of your code examples.
... View more
05-31-2017
04:56 PM
|
0
|
0
|
1731
|
|
POST
|
Thanks, Bixby! That is so much better than the way I was doing it. I have one more question: how do you suggest creating the default dict dynamically when the number of input keys is not known? For example, the user may want to roll up just mtrs, mtrs and owner, mtrs, owner, and mapbook page, etc.
... View more
05-30-2017
11:43 AM
|
0
|
8
|
3689
|
|
POST
|
Joshua Bixby wrote: How would the results of the output change if if the fourth line in the original table was removed? The output would be the same. I think of it in this way. I have a facility polygon layer that is intersected with an MTRS polygon and then also with a land ownership polygon. This cuts the facility polygon into many pieces. Then for each facility, we want to report its MTRS and land ownership. But we only want to list the facility once in the final table. Joshua Bixby wrote: If a single record for Facility X has either Private or Federal, does Private or Federal show up in the output table regardless of how many of the other types of ownership are present? Not sure if I understand your question... But with that said. If Facility X has a row that reports it is on Federal then Federal should be included in the output no matter what other land ownership types are in other rows.
... View more
05-24-2017
02:51 PM
|
0
|
10
|
3689
|
|
POST
|
Because I went too fast when making the mockup. Sorry for the confusion. I fixed it up.
... View more
05-24-2017
01:48 PM
|
0
|
0
|
3689
|
|
POST
|
I did try. They show up fine in the edit space but once it is posted the borders disappear
... View more
05-24-2017
12:57 PM
|
0
|
14
|
3689
|
|
POST
|
I need to make a script tool that will consolidate attributes from many rows into to one across a number of columns. The tool will need to be able to let the user select the field "key" field as well as the fields that will be consolidated. I made a quick mockup table as my input table (it has been processed with spatial sort so that parts of the key features that are spatially adjacent to each other are also in adjacent rows in the table). Mockup table. It has land ownership and PLSS (Public Land Survey System) MTRS (meridian township range section) information. Key_Feature Owner MTR SECTION MTRS MER Facility 1 Private U009N008E 33 U009N008E33 U Facility 1 Federal U009N008E 33 U009N008E33 U Facility 1 Private U009N008E 34 U009N008E34 U Facility 1 Federal U009N008E 34 U009N008E34 U Facility 1 Private U008N008E 4 U008N008E04 U Facility 2 Private U008N008E 3 U008N008E03 U The output should look like this. Key_Feature MTRS Owner Facility 1 U, T09N, R08E: 33, 34 U, T08N, R08E: 4 Federal, Private Facility 2 U, T08N, R08E: 3 Private The question: I would like input on the best method to get the result. And if there are any out of the box Arc tools that I could leverage... My first pass at this was to use arcpy.da.SearchCursor and iterate over the input table and check to see if the current row's key feature is the same as the previous row's key feature. If so, then add it to a string variable. When the key features do not match write the string variable and other fields to the output file. The MTRS roll up is a little more complex because sections needs to rolled up for each unique MTR associated with the key feature. It feels a little wired because you are always looking back in rows as you iterate over the table. So, I used a number of temp_last variables for key features, MTRS, etc. I was thinking that it would be better to read the whole table into a list of lists and then use that to generate the output. That way I could use indexing to look at the next and last rows without having to use the temp_last variables. The below code I made for a similar one off. import arcpy
import os
arcpy.env.overwriteOutput = True
in_path = r"xxxx"
out_path ="xxxx"
def tsv_write(tsv_row):
for item in tsv_row:
tsv.write(item + "\t")
tsv.write("\n")
def rollup(rollup_list):
rollup_list = set(rollup_list)
rollup_list = list(rollup_list)
rollup_list.sort()
rollup_str = ""
for sec in rollup_list:
rollup_str = rollup_str + str(sec) + ", "
rollup_str = rollup_str[:-2]
return rollup_str
def from_to_fix(x):
x = round(x, 1)
x = str(x)
return x
search_cursor = arcpy.da.SearchCursor(in_path, ["Main_LandOwnership_MTRS_Mbook_Meridian",
"Main_LandOwnership_MTRS_Mbook_Town_Range",
"Main_LandOwnership_MTRS_Mbook_SECTION",
"Main_LandOwnership_MTRS_Mbook_F_MP",
"Main_LandOwnership_MTRS_Mbook_T_MP",
"Main_LandOwnership_MTRS_Mbook_Index_Order",
"Main_LandOwnership_MTRS_Mbook_ROW_Designation"])
tsv = open(out_path, "w")
meridian_last = None
township_last = None
f_mile_last = None
t_mile_last = None
owner_last = None
township_list = []
township_section_list = []
first_row_flag = True
township_append_flag = True
section_list = []
index_order_list = []
for row in search_cursor:
meridian = row[0]
township = row[1]
section = row[2]
f_mile = row[3]
t_mile = row[4]
index_order = row[5]
owner = row[6]
if first_row_flag:
township_last = township
f_mile_last = f_mile
t_mile_last = t_mile
owner_last = owner
first_row_flag = False
if township == township_last:
township_append_flag = True
section_list.append(int(section))
else:
township_append_flag = False
section_rollup = rollup(section_list)
township_section_list.append(township_last + ": " + section_rollup)
section_list = []
section_list.append(int(section))
if f_mile == f_mile_last:
index_order_list.append(int(index_order))
else:
index_order_rollup = rollup(index_order_list)
write_flag = True
for trs in township_section_list:
if write_flag:
write_flag = False
print [from_to_fix(f_mile_last), from_to_fix(t_mile_last), trs, owner_last, index_order_rollup]
tsv_write([from_to_fix(f_mile_last), from_to_fix(t_mile_last), trs, owner_last, index_order_rollup])
else:
print ["", "", trs, "", ""]
tsv_write(["", "", trs, "", ""])
township_section_list = []
index_order_list = []
index_order_list.append(index_order)
if meridian != meridian_last:
print meridian
tsv_write([meridian])
print ["From MP", "To MP", "MTRS", "Ownership", "Map Book Sheet"]
tsv_write(["From MP", "To MP", "MTRS", "Ownership", "Map Book Sheet"])
meridian_last = meridian
township_last = township
f_mile_last = f_mile
t_mile_last = t_mile
owner_last = owner
if not township_append_flag:
township_section_list.append(township_last + ": " + str(int(section)))
index_order_rollup = rollup(index_order_list)
write_flag = True
for trs in township_section_list:
if write_flag:
write_flag = False
print [from_to_fix(f_mile_last), from_to_fix(t_mile_last), trs, owner_last, index_order_rollup]
tsv_write([from_to_fix(f_mile_last), from_to_fix(t_mile_last), trs, owner, index_order_rollup])
else:
print ["", "", trs, "", ""]
tsv_write(["", "", trs, "", ""])
township_section_list = []
index_order_list = []
index_order_list.append(index_order)
tsv.close()
Thanks for any input! Forest
... View more
05-24-2017
11:30 AM
|
0
|
16
|
6343
|
|
POST
|
Thanks, Melita. So, in 10.4 and older, we are getting WGS84 (G873)?
... View more
05-23-2017
04:45 PM
|
0
|
1
|
4969
|
|
POST
|
I am wondering about WGS84 as we move through time. My understanding is that any given spot on the earth's surface latitude and longitude will change over time in this system. There are two sources of change: 1) NGA (National Geospatial-Intelligence Agency) will periodically shift the center of the WGS84 ellipsoid to better align with their current best guess for the center of the earth's mass (I think they are using a geoid to find the center of mass). At which time the will release a new version of the WGS84 and note the GPS weeks in the name, e.g. WGS84 (G1150). 2) WGS84 is not locked to any land mass but to the stars. So, as the tectonic plates drift around on the earth's mantle a location on the earth's surfaces can change over time. Does that sound right? So, when I select WGS84 as my GCS what version of WGS84 am I getting? WGS84 (G873) WGS84 (G1150) WGS84 (G1674) WGS84 (G1762) Something else? Thanks! Forest
... View more
05-02-2017
02:11 PM
|
4
|
7
|
7158
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-04-2024 05:39 PM | |
| 1 | 07-30-2024 09:05 AM | |
| 1 | 07-08-2024 05:32 PM | |
| 1 | 03-20-2024 10:27 AM | |
| 6 | 03-13-2024 03:38 PM |
| Online Status |
Offline
|
| Date Last Visited |
11-12-2025
11:02 AM
|