You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to export my data as either a geotiff or a shapefile but when I attempt to export I get a "Georeference information are not available"
I have been following the workflow from the published november SOP. How can I fix this? I can still export the data table and the annotations as a labeled image but when I put that labeled image (png) into Arc it is not properly scaled.
The text was updated successfully, but these errors were encountered:
This is happening because the mosaic provided doesn't have georeferencing information available: when you try to export as a SHP file, without georeferencing, it doesn't know what coordinate system to apply.
One way around this to add georeferencing to your orthomosaic in ArcGIS, and then import it into TagLab; once in TagLab, load up the existing annotations you made, then export those annotations as a SHP.
@Jordan-Pierce Any suggestions on the best way to do that? I tried by uploading my tif to Arcgis pro, went to the georeferencing too and added a single control point to simply move the tif. Then right clicked on my layer -> Data->export raster and I select tif but this gave me the same message
It could be that the orthomosaic wasn't properly georeferenced (I did this literally yesterday as well): when in TagLab, if you go to the Maps Editor tool, you should see if orthomosaic / map is georeferenced (it'll show the information); else it'll be blank.
I am trying to export my data as either a geotiff or a shapefile but when I attempt to export I get a "Georeference information are not available"
I have been following the workflow from the published november SOP. How can I fix this? I can still export the data table and the annotations as a labeled image but when I put that labeled image (png) into Arc it is not properly scaled.
The text was updated successfully, but these errors were encountered: