The PostGIS transform function contains logic that intends to substitute a '2nd chance' non-shifted transformation for an unavailable grid-shift transformation e. FROM mytab' to abort and be rolled back where even a single row of table mytab contains a geometry geom that lies outside the bounds of an applicable grid-shift table. Running on Postgres 8. Although this patch works for me, please scrutinize it carefully. This is my first look at PostGIS and proj.
Worse, I code in C very rarely and am especially error-prone when using C pointers and indirection. Thanks so much for PostGIS! It's a tremendous resource that contributes materially to the public good. Download all attachments as:.
Thanks for submitting the patch with your bug report above. I'm also a little surprised by the existing logic to try again without the grid shift information - surely we should simple return NULL in the case where the transformation is invalid?
Also another minor note: if you submit a patch, could you submit in either unified -u or context -c format? It just makes it easier to review on sight without application. I then read cs2cs's relevant code and pretty much plagiarized it for my patch. I have a large table of broadcast radio station locations -- most in CONUS but some in Alaska and Puerto Rico; aborting processing of the whole table because the transformation of one or two rows will be off by a few hundred meters is very inconvenient, especially because the offending geometry is not identified in the error message and only the first one is found before abort.
My main argument: if proj. In this particular case, the warning is misleading 'failed to load NAD correction file' when the real problem is out-of-bounds input , but at least they're warned once for each offending geometry while still getting a useful result table. If you know how to make that warning actually identify the offending point, that would be a great improvement. Didn't want to press my luck given my very limited C skills.
I'm now attaching a 'diff -u'. We see people being caught out a lot because they've installed the grid shift files on one server and not another and wonder why the results beween 2 servers are different. From a strictness point of view, I would argue that any transformation requested by the user that cannot be achieved using the current installation should throw an ERROR rather than trying to second-guess the user.
At least then it would be very clear that they need to re-install PROJ. The used testcoordinates are from Cologne, germany, but all tested coordinates in Europe give the same problem. If you need more, please ask. Hint: PostGIS was unable to transform the point because either no grid shift files were found, or the point does not lie within the range for which the grid shift is defined. Hallo, a more trivial example osm form open street map, worldcountries has geometries in srid format: this works: select world.
ERROR: transform: couldn't project point 5. Unfortunately, without a database dump of the relevant tables then it is impossible for me to re-create this here. I could give you access to my database if you want to. No special or private tables there. I tried my 1. Slight correction -- I see the one that fails for me is the NAD27 and not the other one that was complained about.
But it would be still interesting to find out if we are all working against the same proj4text. I had the same problem. I upgraded from PostGIS 1. I also used a My database still had all the tables assigned as When executing the statement right after a PG restart it works!
Any following statements after that fail! ERROR: transform: couldn't project point 2. There are many different ways to modify your system's environment variables, so I can't really explain how to do this. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Learn more. PostGIS 2. HINT: PostGIS was unable to transform the point because either no grid shift files were found, or the point does not lie within the range for which the grid shift is defined.
Even after a bit of google-foo, I still can't figure out how to install the correction file I can do And I can do other transformations just fine I tried to and I read somewhere to check to make sure PROJ is installed and it is:.
If you build PROJ. Furthermore, the grid shift files need to be unzipped in the correct directory before. They can't be installed after. To get started, I wrote a guide for this on the postgres wiki. With pgrmps. Similarly, Ubuntu has a proj-data apt package, which may or not be automatically selected as a dependency. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams?
0コメント