1 respuesta
- 210
Bursa-Wolfe parameters are necessary for proper reprojection. GIS software does not require them because they are not necessary as long as the original projection is used. In k.LAB, the software requires full GIS compliance because it contains GIS algorithms that include reprojection, rasterization and the like.
In order to find the Bursa-Wolfe parameters, you can find the projection definition on web sites such as http://www.epsg-registry.org/ and correct it in your GIS software, or use utilities such as GDAL/OGR to rewrite the projection. Otherwise, you can launch k.LAB in debug mode by adding the line
thinklab.client.debug = on
in your .tl/thinklab.properties file. The next time you launch k.LAB, the engine will show a command window in which you can type commands. After the system has initialized, type
inspect -rn projection EPSG:3004
(substitute your projection of interest) and the system will respond with the WKT definition (on a single line for compliance with most GIS formats) that you can paste into a .prj file or feed to your GIS software. The projections in k.LAB contain the Bursa-Wolfe parameters; the ones used in many GIS softwares often do not.
The command can be used also to ensure that the projection is recognized by k.LAB. If you only want to inspect the projection you may want to omit the -rn parameter, so that the projection's WKT definition will be printed with more readable formatting.
- bram.vanmoorter
I am sorry, but I get the same error message, even after I have used the specification according to the epsg-registry website in the .prj file. Moreover, I don't seem to be able to find the command window after adding "thinklab.client.debug = on" to my thinklab.properties file. It is the first thinklab.properties file under the .tl folder without any content by default, right?
- Ferdinando Villa
You need to restart the engine before you can see the command window. Safest course of action is stop engine, exit k.LAB, restart everything. If the <HOME>/.tl/thinklab.properties contains that line, you should see a small window named "Thinklab console" where you can type commands.
- Ferdinando Villa
The Bursa-Wolfe parameters are those named PARAMETER in the WKT that follows. If your projection does not have them, kLAB cannot use it. PROJCS["Monte Mario / Italy zone 2", GEOGCS["Monte Mario", DATUM["Monte Mario", SPHEROID["International 1924", 6378388.0, 297.0, AUTHORITY["EPSG","7022"]], TOWGS84[-104.1, -49.1, -9.9, 0.971, -2.917, 0.714, -11.68], AUTHORITY["EPSG","6265"]], PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]], UNIT["degree", 0.017453292519943295], AXIS["Geodetic longitude", EAST], AXIS["Geodetic latitude", NORTH], AUTHORITY["EPSG","4265"]], PROJECTION["Transverse_Mercator", AUTHORITY["EPSG","9807"]], PARAMETER["central_meridian", 15.0], PARAMETER["latitude_of_origin", 0.0], PARAMETER["scale_factor", 0.9996], PARAMETER["false_easting", 2520000.0], PARAMETER["false_northing", 0.0], UNIT["m", 1.0], AXIS["Easting", EAST], AXIS["Northing", NORTH], AUTHORITY["EPSG","3004"]]
- bram.vanmoorter
For some reason kLAB restart didn't do it, or I had missed the little window that opens in parallel to kLAB's main window (I was erroneously looking inside kLAB's main window among the different panels). In any case, a system restart certainly did the trick (but I suspect this is not necessary, and I just had missed it on the first run). Using the BWparams from kLAB I get it to work nicely. Thanks! It is intriguing that copy-paste the parameters in WKT from http://www.epsg-registry.org/ didn't do it. The differences seem minor. Wouldn't it be possible to just provide the EPSG code?
Añada su comentario...
After annotating a GIS file that works perfectly in my favorite software, k.LAB gives me an error saying that Bursa-Wolfe parameters are missing every time I try to use it.