Latest Contributions by forestknutsen1

Melita I just noticed this in the projection tool help. An additional example of the improper use of the GRS80?  ... View more

Just connect to it with ArcCatalog without any special connection. Arc can read an mdb that was not created with arc as a personal geodatabase.  ... View more

You could run an intersect with points as the output... If you get a point at least part of the city is on the coast. How Intersect works—Help | ArcGIS Desktop  Intersect—Help | ArcGIS Desktop  ... View more

By task to you mean a windows task? Made with the task scheduler? If that is the case... I don't know how to get the message to pop up. What we do is create a log file (just a text file) someplace and then write any messages to that. ... View more

Thanks, Melita for all the feedback. It is appreciated. The intermediate software makes sense. But I still think it is very sloppy. Thanks for the context on GRS80. ... View more

The shift from WGS84(G1150) to NAD83(CORS96) is about 4ft in Alaska. So, it could be significant depending on the resolution of that data, as Melita pointed out. http://www.spatial-ed.com/images/documents/Datums/JOEL_CUSICK_Datums_and_Transformations_GPS_Software_2013.pptx  ... View more

Sorry Melita, looks like you may have responded to the same question on a different forum (I did wait a few day before I created a second post). I should have closed this one. However... I am still a little bothered by this. I don't get why anyone would collect elevation data on a nonexistent datum over a large area. Have you seen this problem before? I guess some technician could have messed up someplace in the processing. The project has been passed around a little -- so, contacting the original vendor for the data may be difficult. Also, I was concerned when I read the Wikipedia page for GRS80 (I know it could be wrong). "GRS 80, or Geodetic Reference System 1980, is a geodetic reference system consisting of a global reference ellipsoid and a gravity field model." I was thinking that a geodetic reference system went beyond just an ellipsoid to include a coordinate system. They also talk about a gravity field model, which makes me think geoid. If it is just an ellipsoid it can not have a geoid as well.... All adding to my confusion. Can you please provide me with a definition of "geodetic reference system"? Thanks! Forest ... View more

http://tech2mine.maps.arcgis.com/apps/Solutions/s2.html?appid=ef12074d67f648a7825cc7ed160d68fa  Yes. Looks like Sweden falls within a few UTM zones. With most of it zone 33.  Unfortunately, I don't know anything about the drone you are using. You will definitely need to know the system of the source rasters from the drone. I would think that the output system would be in the documentation some place. What happens if you just display one of the images in arc? Is that working ok? ... View more

What format are the source rasters in? tif? What coordinate system are the source rasters it? What system you select for the mosaic depends in part on what you want to do with it. If it is a small area and just want to look at it in Arc and you are in the US I would go for the state plane system of the image area... What is the error message? ... View more

Sure, I edited the code post ... View more

Rebecca's suggestion is the right way to go. But just FYI you can also build your csv from scratch if you like (or if the out of the box tool does not have the function you need). The bellow code makes a tsv (tab separated values) report for MTRS. import arcpy import os arcpy.env.overwriteOutput = True # in feature class or table in_path = r"xxxxx" # out tsv file out_path = r"xxxxx" # tsv write function - the input is a list of all elements for one row in the tsv def tsv_write(tsv_row):     # write each element in list to tsv     for item in tsv_row:         tsv.write(item + "\t")     # end tsv row i.e. new line     tsv.write("\n") # create search cursor for input feature class search_cursor = arcpy.da.SearchCursor(in_path, ["field_1",                                                 "field_2",                                                 "field_3"]) # open/create tsv output file tsv = open(out_path, "w") # setup some variables to be used in loop meridian_last = None township_last = None township_list = [] first_row_flag = True section_list = [] # loop over input feature class table row by row for row in search_cursor:     # read in values from row     meridian = row[0]     township = row[1]     section = row[2]     # if it is the first row of the table set township_last to township     if first_row_flag:         township_last = township         first_row_flag = False     # if the township is the same as the last township then "roll up" the sections for it, i.e. the same township but a different section     if township == township_last:         section_list.append(int(section))     else:         # sort the sections so that they are in ascending order         section_list.sort()         section_str = ""         # build a string from section list with commas between         for sec in section_list:             section_str = section_str + str(sec) + ", "         # remove hanging comma and space from sections string         section_str = section_str[:-2]         print [township_last, section_str]         # write township and rolled up section string         tsv_write([township_last, section_str])         # restart section list         section_list = []         section_list.append(int(section))     # write headers each time township is in a new meridian     if meridian != meridian_last:         print meridian         tsv_write([meridian])         print ["Township, Range", "Sections"]         tsv_write(["Township, Range", "Sections"])     # reset meridian_last and township_last     meridian_last = meridian     township_last = township # output the last township in the table to the tsv section_list.sort() section_str = "" for sec in section_list:     section_str = section_str + str(sec) + ", " section_str = section_str[:-2] print [township_last, section_str] tsv_write([township_last, section_str]) # close the tsv tsv.close()‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Anyone have any thoughts on this? ... View more

Hahaha - I did not notice that part of the dialog! It is working now. Thanks for the help! ... View more

I would try saving a csv out of excel (if you don't have commas in your data) -- save as in excel. Then try using that csv as the input to arc. ... View more

Thanks for the reply Parshant. I did a test with a subset of the data. I still get the same error when I switch from an arithmetic function to a unit conversion function to change meters to feet.  I did get the mosaic to mostly work. The pixel depth error does not appear to be causing problems that I can see... ... View more