I work in North Carolina. All the county GIS sites use EPSG2264 - NAD83/North Carolina (ftUS). When I create the Qfield file, in Qfield on my collection device I get an error stating I need https://cdn.proj.org/us_noaa_nchpgn.tif. I have downloaded the file and added it as a layer. I have also connected to the file with HTTPS. However, on the collection devise it still states I need the geotiff file despite the fact that the file is there. The us_noaa_nchpgn.tif file’s crs is NAR83(EPSG 4269) to NAD83(HARN)(EPSG 4152) converted from nchogn.gsb. How do I make this work? I have tried numerious solutions I have found on the internet to no avail.
Did you create the project in QField or QGIS? It sounds like maybe you need to set the layer as “offline editing” or maybe “copy” if you are using a downloaded .tiff that you want to copy when transfering to a mobile device via wire.
To set a layer to be copied, at least when creeating the project on QGIS first, you have to edit the “Packaging Action” for that layer by going to Project Properties > QField > QFieldCloud Packaging / Cable Packaging (depending if you are using QFieldCloud or not). Check the following image to get an idea on where to find this:
In this case, “Observaciones (Lineas)” is a local vector layer for my project, in your case it would probably be called “us_noaa_nchpgn” or something like that.
Thank you cuprico for replying. Just this morning I got the project opened in Qfield without the warnings. I created a new project, added the Geotiff which set the project CRS. I added the EPSG2264 state plane shp file to the Qgis project, then did a “save layer as…” but set the crs to EPSG 4269, and then added that new layer. I have not made it to the field to test out in the world, but the project did not give any errors. I had been trying to transform the CRS of the GeoTiff (EPSG 4269) to the shape file (EPSG2264) which kept throwing the error.
ok, good to hear!
It still sounds weird to me that QGIS/QField would have problem with a particular crs, maybe it can’t properly read the CRS from that particular file (a likely problem with .shp files). That might explain why it works when you remake the file with the “save layer as..” function.