![]() Not realizing that this was happening caused me to create a set of files that were wrong because I saved them to a new file, with a new projection. Honestly, for software as far along as QGIS, it should be able to recognize a projection if it is already defined. I have seen this bug brought up before, and it has either been fixed, or closed, or some workaround was created that basically creates a new projection file specifically for QGIS. When loaded, the shapefile appears the coordinate space of a dataset in meters, not in Lat/Lon? as it should, given the defined projection. I then loaded in a shapefile with a defined projection of Albers Equal Area, NAD 83, from the California Teale Data Center. I specified the projection to be WGS 84, and enabled on the fly reprojection of layers. ![]() When you look at the properties for that layer, it shows the default lat/lon WGS 84 projection. QGIS will not recognize the projection that is defined for that shapefile. I am continually running into an error where I will load a shapefile with an existing, defined projection, into QGIS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |