-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support QGIS .qpj files #34
Comments
/cc @timlinux - can you help me understand whether a QGIS .qpj is intended for use outside of QGIS? In this case a report came in of data lining up correctly in QGIS but not in the tilemill. The difference is the .qpj leads to a proj4 string like:
while the .prj results in:
In TileMill I can start looking for an preferring .qpj files over .prj files if they exist. But want to make sure you think this is a good idea. Are .qpj files around for the long haul? Will their format change? They basically look like valid OGC WKT right now + extra details. |
@springmeyer Hi. Yeah I think you can reasonably expect the .qpj file to stick around for the long term. You can see the back story for adding .qpj here: http://hub.qgis.org/issues/2123 cc @jef-n in case he has any further comments to make. |
It's what GDAL's OSRExportToWkt() returns and what can fed into OSRImportFromWkt() without hassle. While OGR morphs the WKT into an ESRI WKT format for the .prj and back - and that's not lossless IIRC. |
@springmeyer Review of node-srs issues is part of my getting up to speed on the project. Since we've got a test for this since cb6ce7c I'm closing. |
great, thanks @sgillies - yes, nothing more to do here as node-srs handles without any changes. As far as preferring .qpj over .prj this would be handled by some application calling node-srs and in the case of TileMill that's millstone, so tracking over at tilemill-project/millstone#115 |
Turns out QGIS writes its own projection file - some variant of OGC WKT with extras like
EXTENSION["PROJ4_GRIDS"
. Got a hold of one from a user running QGIS 1.8:The text was updated successfully, but these errors were encountered: