Latest Contributions by JohnSobetzer

I just took a canopy heights raster tif with classified symbology imported from a layer file in Pro and exported it to jp2 with both Use  renderer and forced RGB options checked.  The new raster came into Pro with the appropriate colored symbology although with just a bit of a color shift.  I then opened that exported jp2 in QGIS and it came in looking like the original CHM as symbolized; no color shift.  I usually use QGIS to create my rendered rasters exported to tif which has no RGB setting but apparently forces RGB on its own.  I noticed Pro showed the same slight color shift with a rendered tif export from QGIS, but there was no such color shift for either when viewed in QGIS.  So the Pro approach works fine as far as I could tell. ... View more

Did you try it with the force RGB option?  ... View more

You can export the raster with the use renderer option.  The force RGB might or might not also add to that.  See https://desktop.arcgis.com/en/arcmap/10.3/manage-data/raster-and-images/exporting-a-raster-in-arcmap.htm ... View more

I get the same error trying to read a geopackage file created by another person in QGIS 3x.  ArcMap 10.6.1 will give me a longer more detailed error message, and then show me the table but not the polygons.  QGIS can use it fine, and convert it to a shapefile that ArcGIS can read. ... View more

I am resurrecting this old post to see if anyone found a workaround for the limitation on the use of hyphens in an output shapefile when certain geoprocessing tools are used.  I have an ArcMap  project where selected features get exported to new shapefiles with dates using hyphens.  It works fine and the result fits in with the naming format of hundreds of shapefiles.  In ArcGIS Pro it doesn't work because Pro uses the Copy Features tool to do the same thing, and while it can read a shapefile with hyphens in its name as input, it cannot export to a shapefile with hyphens in its name.  Same thing for the Feature to Polygon tool.  This is not a big deal since I have the ArcMap project and can make a QGIS project from it, but it is just one more way Pro seems to delight in screwing up simple conversion of ArcMap projects to Pro projects. ... View more

ESRI tech support just indicated to me this is a known defect to be remedied in 2.3. ... View more

I whole heartedly agree with Jim's comment.   I have to use ArcCatalog to look at sizes and dates, so I generally try to avoid using the Catalog View.  The lack of size and date info is one thing I've always hated about the Catalog pane in Pro or ArcMap as well.  The popup when using the Catalog pane is a distraction that doesn't provide any useful information to me when I have the hierarchy tree.  Too bad the popup isn't customizable to show data I want to see.  The popup when using Catalog View in Pro provides a path which is a help but that's only because Catalog View doesn't show a hierarchy at least as far as I've been able to discover.  ... View more