Latest Contributions by forestknutsen1

Great. We don't want two data sets if we don't need them. I will review the webinar. ... View more

1) I just put them into gdb for the projection processing as I have run into weird and unknown problems in the past when working with the tifs (this may still not be a problem. Last time I did this we still had a mixed environment 9.3 and 10.1. Now we have almost retired all of the 9.3 stuff) 2) The data must be projected for use in web maps. In the past we had a map service of a raster dataset that reprojected on the fly, but it was fuzzy when viewed at small scales. Now maybe a image service off of a mosaic dataset would not have this problem, but I understand that we would need an image server extension for ArcGIS server. The current plan is to have a cached map service on the hard drive of server in the same projection as the web mapping application. 3) This is a problem for all of our 2015 and 2012 ortho images. Sadly, I can not share any part of the data as it is confidential; however, I will try and find something that I can share with you that has the same behavior. ... View more

Both are LZ77 ... View more

I am sorry that I mixed your comments up Gabriel and Chris. Gabriel, the extra rows and columns are not in no data (well a few of them are for sure but not 1000s of them). No data in magenta. ... View more

Gabriel Upchurch: Interesting.  It appears there has been a considerable addition of rows and columns.  The proportional difference in rows and columns is almost identical to the proportional difference in file sizes.  I would symbolize your NoData cells to see if that is where all the extra rows and columns are hiding. For sure the extra size has to be coming from the increase in rows and columns. But why is this happing? I would think that it would have more or less the same number of rows and columns as the original because: Which is the cell size that the tool selected. ... View more

Thanks for the info; however, both images are 8 bit. ... View more

Thank you for the feedback Jake. Am I right in thinking that the speed of the cached map service should be the same regardless of the underlying data it was made from, raster dataset vs. mosaic dataset? The main reason to use the mosaic dataset would be the faster creation time of the dataset and the faster caching time of said data set. ... View more

Rebecca Strauch, GISP: Forest, that [is] what I'm hoping. We have a lot of server/network upgrades going on, but in my research so far, I think all that will work. I'll probably be duplicating/distributing the mosaic/fgdb  to multiple locations (Large state...not great network connectivity ) but it is all theory for me right now ( and still waiting for delivery of some new data).  Great, that is what we are thinking as well. One fgdb at the main office and one more for the remote part of the state. I am going to give this part a go once we get this summers orthos in. Thanks for the input. Thanks for the EDN link. At first look our agreement with esri does most likely include the image extension, but I will have to follow up a little to know for sure... ... View more

Thanks for the feedback Rebecca. Wow, 8 weeks to 7 days is huge. So, for people in your office are you just planing on having a the mosaic dataset in a fgdb on a network drive That they will hit with a layer file? ... View more

Hi Grant, We have quite a bit of code for metadata processing. In part driven by misbehaving ArcGIS metadata tools. This one is a metadata exporter but we also have some import stuff and a batch exporter. This code exports metadata based on a schema document for a feature class or table but will not work inside feature data sets. The XML that is generated from this I have found will import with the metadata importer tool as expected. ''' Exports metadata based on a schema workspace document 3/3/2015 ''' import arcpy import tempfile import os import xml.etree.ElementTree as ET import codecs import shutil input_path = arcpy.GetParameterAsText(0) output_path = arcpy.GetParameterAsText(1) xml_file_out = 'out.xml' temp_dir = tempfile.mkdtemp() export_option = "SCHEMA_ONLY" storage_type = "BINARY" export_metadata = "METADATA" arcpy.AddMessage('xml export starting.....') arcpy.ExportXMLWorkspaceDocument_management(input_path, os.path.join(temp_dir, xml_file_out)) arcpy.AddMessage('parsing xml.....') tree = ET.parse(os.path.join(temp_dir, xml_file_out)) root = tree.getroot() def data_type_finder(de):     de_type = str(de.attrib)     index_start = de_type.find('esri:')     de_type = de_type[index_start + 5:-2]     return de_type def catalog_path_finder(de):     de_catalog_path = de.find('CatalogPath').text     de_catalog_path = de_catalog_path[15:]     index = de_catalog_path.find('/')     if index != -1:         sub_string_end = de_catalog_path[index + 4:]         sub_string_start = de_catalog_path[:index]         de_catalog_path = sub_string_start + "/" + sub_string_end     de_catalog_path = de_catalog_path[3:]     return de_catalog_path def metadata_finder(de):     de_metadata = de.find('Metadata')     temp = de_metadata.find('XmlDoc')     if temp is not None:         metadata_temp = temp.text     else:         metadata_temp = ''     return metadata_temp arcpy.AddMessage('writing metadata xml.....') for data_element in root.iter('DataElement'):     data_element_type = data_type_finder(data_element)     metadata = metadata_finder(data_element)     catalog_path = catalog_path_finder(data_element)     output_file = codecs.open(os.path.join(output_path, catalog_path + '.xml'), 'w', 'utf-8')     output_file.write(metadata)     output_file.close()     break shutil.rmtree(temp_dir) Hope it helps a little. ... View more

This is a little off topic but, you might give PyCharm a try at some point. I switched from PyScripter about a year ago. Python IDE &amp Django IDE for Web developers : JetBrains PyCharm ... View more