Skip to main content

Problems exporting the Identify Results to CSV, XLSX, & SHP

Comments

16 comments

  • Permanently deleted user
    I have the exact same issue and repoted to Latitude earlier. They told me this is related to the bug GVH-5598. Parcel number is the most important field in our data, so this is a major issue for us. Hopefully they will fix this soon.
    0
  • Permanently deleted user
    Ditto
    0
  • Carmen Durham
    I have the same problem, but with a twist and why just the PIN?  I don't think it has to do with length of field.  My longer fields work okay.

     

    Anyway - we have some parcels with PINs that begin with letters, while most begin with a number.  If the selection set includes some parcels that begin with a letter, then the PIN exports/displays in Excel without issue.  Even the parcels that begin with a number will display fine (as long as there are parcels that begin with letters included).

     

    If the selection set has only parcels beginning with a number, then the export has nothing in the PIN field.

     

    (Interestingly, I often have issues bringing in .csv files into EXCEL that have a PIN exported from ArcGIS desktop.  It wants to convert to scientific notation for some reason.)

     

     
    0
  • Matt Taylor
    Is there someplace I can view bugs and promote them??  This is an issue for us.
    0
  • Carmen Durham
    that was exactly my next question - how to look up a bug by id.
    0
  • Nico Burgerhart
    Integer fields in a shapefile have a limit of 9 characters. Seehttp://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=Geoprocessing_considerations_for_shapefile_output > Attribute limitations

     

     
    0
  • Nico Burgerhart
    I guess the contents of the first record define the datatype of the output columns.
    0
  • Nico Burgerhart
    Check the release notes for bug numbers of solved bugs; but you'll not find all bug numbers in it.
    0
  • Permanently deleted user
    I can confirm this is fixed for GVH 2.5.2 which is due to be released at the end of October.  The issue is related to strings that contain only numbers being treated as numbers.  There is no method currently to look up bug numbers, the bug numbers will appear in the release notes as being fixed once the fix is released.

     

    Regards,

     

    Wayne Richard

     

    Latitude Geographics Group Ltd.

     

    Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

     

    Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com

     

    Developers of Geocortex web-based mapping software | www.geocortex.com

     

    An Esri Platinum Business Partner
    0
  • Bill Everingham
    We aren't getting any of the csv files when exporting the records from data linked tables. The feature table exports, but none of the others. There is a bug/improvement... GVH-7745

     

     
    0
  • Ethan Granger
    This is still a problem in GVH 2.5.1 and there is no GVH 2.5.2.  What is the status?
    0
  • Permanently deleted user
    Version 2.5.2 has passed QA and is in the process of being released, you should see it in the support center this week.  Please watch for the announcement on the support center.

     

    FYI, version 2.5.2 does not include GVH-7745 as it was too recent to make it into the release.

     

    Wayne Richard

     

    Latitude Geographics Group Ltd.

     

    Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

     

    Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com

     

    Developers of Geocortex web-based mapping software | www.geocortex.com

     

    An Esri Platinum Business Partner
    0
  • Ethan Granger
    I've upgraded to HTML5 2.5.2 and now I can't export to CSV/XLSX at all! Progress bar appears saying "Exporting to CSV" and then disappears. Nothing is downloaded, nothing is in my downloads folder.
    0
  • Ethan Granger
    Update to my previous post, it appears to be a problem when more than one layer is identified and exported.
    0
  • Permanently deleted user
    I just tried this in 2.5.2. I have turned on the parcel layer and address points layer and another one. Then identified some features from all three, then exported to Excel & CSV. In my case it worked well. The good news is I now see the parcel numbers in the spreadsheet!
    0
  • Ethan Granger
    The problem seems intermittant, but 90% the export fails. I've not yet noticed a pattern, but when the progress bar is on the screen for a longer period of time, it is clear the export won't work.
    0

Please sign in to leave a comment.