Blair,
If I understood correctly you dont intend to store geometries in HStore but
in the standard geometry PostGIS enabled column.
Storing key/value pairs in hstore should not bring any issues. You can
also index such hstore field for quick searches.
In order to properly get / set data in Hstore
Hi Ben
Try instead of "public.CLEANEDCAMDENGPS" --> public."CLEANEDCAMDENGPS"
notice the "".
I strongly suggest to lowercase all your table and column names.
Hope this helped.
Ricardo
2011/5/30 Ben Madin
> James,
>
> The error message has two possibilities:
>
> ERROR: relation "public.
It got fixed by reinstalling pg9 and postgis 1.5.2.
Steve, dont see why by setting the search path would work.
Thanks.
Ricardo
On Fri, Oct 8, 2010 at 5:47 PM, Stephen Woodbridge
wrote:
> On 10/8/2010 4:16 PM, Ricardo Bayley wrote:
>
>> Hi Paul,
>>
>> It returns what
Hi Paul,
It returns what it should, one record of type geometry.
This is why I dont understand why the function is saying that geomtry type
does not exist.
Odd right ?
On Fri, Oct 8, 2010 at 4:41 PM, Paul Ramsey wrote:
> SELECT 'POINT(0 0)'::geometry;
__
Hi fellows,
I had a ver nice reverse geocode function on my postgis 1.5.1 box.
When I install it to my new 1.5.2 postgis installation I get this
ERROR: no existe el tipo «geometry»
Which in english means type does not exist ?? huh ?? How, why ??
This is a piece of my function code
*CREAT
I hope to be testing it next week
On Wed, Aug 18, 2010 at 4:41 AM, Paragon Corporation wrote:
> BTW - If any windows users want to try the trunk version (PostGIS 2.0) --
> we have experimental binaries (fairly recent as of last week)
>
> Here
> http://www.postgis.org/download/windows/experiment
--------------
> *From:* postgis-users-boun...@postgis.refractions.net [mailto:
> postgis-users-boun...@postgis.refractions.net] *On Behalf Of *Ricardo
> Bayley
> *Sent:* Wednesday, August 18, 2010 12:06 AM
> *To:* postgis-users@postgis.refractions.net
> *Subject:*
Hi,
I am calculation the PointOnSurface for a table of polygons. I get this
error message
NOTICE: TopologyException: found non-noded intersection between LINESTRING
(857703 1.04022e+006, 857648 1.04019e+006) and LINESTRING (857536
1.04019e+006, 857870 1.04019e+006) at 857648 1.04019e+006
ERRO
very nice explanation Mike
On Thu, Aug 12, 2010 at 11:39 AM, Mike Toews wrote:
> Hi,
>
> Your coordinates may be flipped. Was it 59N 18E? If so, use x,y
> notation: 'POINT(18 59)', which results in 'POINT(18.6
> 58.99905)', which is close enough.
>
> Also keep in mind that yo
ex on the tsvector.
> But normally this is not critical.
>
> We use the trigger approach for our search engine on
> http://mapmatters.org . The hardest thing there was and still is to
> optimize the way how data are combined and weighted for the tsvector (
> so how you feed the &
Hi fellows,
I am creating a search engine for my spatial data.
And I am thinking of the best approach.
My idea is to have a full text search (tsvector) coulmn for every table.
Instead of performing a search on every table, I have thought of a few
options
1. "Merge" all tables into one, regardles
I havent tried it much, but I know QGIS has this option.
The OGR module does this. It is very good.
Hope it works for you
On Sat, Jul 24, 2010 at 4:26 PM, Mike Toews wrote:
> Ok ok, I've finally tamed ogr2ogr to a working state. When configuring
> GDAL, use "--with-spatialite=/usr/local" (for
Hi fellows,
I was wondering if any of you have a good approach to do Address Geocoding
within postgis.
Any ideas, considerations, thoughts ??
thanks in advanced.
Warm regards,
Ricardo
___
postgis-users mailing list
postgis-users@postgis.refractions.
13 matches
Mail list logo
