Hello,
I have just set up on my blog at the following address
http://ageoguy.blogspot.com/2011/03/autohotkey-openjump-pgadmin3postgis-et.html
A GeoSpatial World
which presents the use of the utility AutoHotKey http://www.autohotkey.com
AutoHotKey
http://old.nabble.com/file/p31122820/AutoHotke
Jorge, we must thank you for these analytical informations about installing
PostGIS Raster!!
Really, it wiil help many beginners, like me!!
Apostolis
___
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mail
Hi Jorge,
This is great. Really helpful for beginners.
I wish I had this when i was started using postgis Raster.
Andreas
2011/3/10 Jorge Arévalo
> I've created this small howto, in order to help people who want to use
> PostGIS Raster in Windows enviroment. I hope it helps:
>
>
> http://gis4f
It has to do with how the ODBC driver tries to update the record. It
creates a where clause for every field in the row. The value it
compares to the geometry field is not valid.
In the psqlODBC driver you can enable the option 'Row Versioning'
which will cause the driver to update with a where cl
I've created this small howto, in order to help people who want to use
PostGIS Raster in Windows enviroment. I hope it helps:
http://gis4free.wordpress.com/2011/03/10/how-to-install-and-configure-postgis-raster-on-windows/
Best regards,
--
Jorge Arévalo
Internet & Mobilty Division, DEIMOS
jorge
On Wed, Mar 9, 2011 at 16:46, Mark Cave-Ayland
wrote:
> On 08/03/11 09:16, Magnus Hagander wrote:
>
>> Since nobody appears to be too interested in producing a quick fix in
>> geos, attached is a patch that puts in an *ugly* workaround in
>> PostGIS, that simply rejects the infinite values higher
Hi All,
I have tried many searches to find a solution to this problem, but
unfortunately I am no further forward.
I have an installation of PostgreSQL and PostGIS (latest stable versions) on
a server, with which QGIS works fine. However, I installed the PostgreSQL
35W ODBC driver on a windo
Hi Ralf,
I have to correct me: it's not vertexes 4 and 8, I am worried about,
it's vertexes 3 (3597943 5323120) and 9 (3606024 5322587) and they are
both vertexes in both input polygons.
But, I thought about your explanation again and I think, I understand
now, what you are talking about: The
Hi Ralf,
sorry, I don't understand. I don't want these two points in the result
polygon of the difference, because they are located in a region that
should be erased by the difference. I don't need them to become more
precise. Or am I misunderstanding what you are saying?
Regards,
Birgit.