Mario,
Actually Mark L just fixed the bug in trunk (and he is patching the fix into
1.4 and I believe 1.3 as well). So it will be fully functional in PostGIS 1.4
probably due out next week and 1.3 about a month later.
st_curvetoline has always worked with curve polygons (with either
circular
This might help
http://trac.osgeo.org/postgis/wiki/UsersWikiplpgsqlfunctions
upgis_lineshift(centerline geometry, dist double precision)
Though its simplified in the sense it bases on start and end points of
the linestring to do the shift.
To do true shifting when you have very curvy lines or
Mike,
In PostgreSQL 8.4 by the way, what you have will work. For lower
versions I wrap my plpgsql in an sql function wrapper as described here.
http://www.postgresonline.com/journal/index.php?/archives/16-Trojan-SQL-
Function-Hack-A-PL-Lemma-in-Disguise.html
Hope that helps,
Regina
-Orig
Genis,
http://www.spatialreference.org/ref/epsg/23031/
use the PostGIS isnert statement. i susually change the srid to match the EPSG.
Hope that helps,
Regina
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractio
Kai,
I think you are running into floating point issues with intersects and
touches. That is why even intersects doesn't work. Because the
representation of a point on surface approximates a point on the surface
but is not always a point on surface if that makes any sense.
use ST_DWithin instead.
Guy,
You would use the ST_Transform function. I see two Lambert 72 in my
database (31300 and 31370). I assume one of them is right for you, but
if not -- use http://spatialreference.org to find the right one
SELECT * FROM spatial_ref_sys where srtext ilike '%Lambert 72%'
WGS 84 has an SRID of
/5707-MapInfo-Pro-v10-to-Support-Po
stGIS.html
MapInfo v10 will support PostGIS.
James
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Obe,
Regina
Sent: 16 January 2009 14:53
To: PostGIS Users Discu
Nacho,
I believe qix is a quadtree index that is a UMN Mapserver creation and I'm not
sure how many other tools can really use that index. Use the shptree (I forget
the exact name of the commandline tool but I think that is it that is packaged
with UMN Mapserver) to create the qix file.
Hope t
> Mark Cave-Ayland,
> I forget were we planning on making this a switch option in later
versions
> of PostGIS? So that you could bring in polygons with unclosed rings
and fix
> them in the db?
> Well the result of the earlier investigation showed that having a
switch
> will just cause more prob
> I think that if both Oracle Spatial and MS-SQL allow geometries to be
> stored with deformed features (i.e. incomplete rings) then I could be
> persuaded that the ERROR upon insertion should be downgraded to a
> WARNING instead. Would anyone like to check this behaviour and report
back?
Mar
No that is really ancient. Where did you get that from though its only in
english?
try using this one instead --
http://www.enterprisedb.com/products/pgdownload.do#windows (the application
stack builder will have options to install PostGIS). So just follow the wizard
steps.
Alternatively if
I'm sure there is a very good reason you are using the antiquated 8.0.3.
Just curious what is that reason?
I'm guessing you forgot to install plpgsql language in your database.
createlang plpgsql SIG
then run the .sql files.
Hope that helps,
Regina
-Original Message-
From: postgis-
b
Result is empty geometry. After removing both IsClosed conditions
geometry will appear. Why ? Where can be mistake ?
Ivan
On Tue, Mar 24, 2009 at 1:24 PM, Obe, Regina wrote:
> Ivan,
>
> Oops more of a variant. I see you have invalid polygons as well not
> just rings. Hmm try this
Steve,
Just to add my 2 cents. I've been running 8.3 on 2 production systems
for about 6-8 months now. Aside from the index issue Mark already
mentioned, and also a bbox issue (with cached bboxes not always being
recalculated -- hmm I think this is fixed in 8.3.6 -- though I'll need
to verify)
) b
$BODY$
LANGUAGE 'sql' IMMUTABLE;
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Obe,
Regina
Sent: Tuesday, March 24, 2009 8:14 AM
To: PostGIS Users Discussion
Subject: RE: [pos
Ivan,
I think a variant of Simon's script would work for you except instead of
keeping rings with a large enough hole, keep rings that are closed and
have enough points
http://www.spatialdbadvisor.com/postgis_tips_tricks/92/filtering-rings-i
n-polygon-postgis
so something like
CREATE OR REPLACE
ST_Boundary
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of
Nicholas I
Sent: Wednesday, March 18, 2009 2:44 AM
To: postgis-users@postgis.refractions.net
Subject: [postgis-users] polygon to lin
Kevin had sent an email early morning that it was down and he was
working on bringing it back up. That's the last I heard of it.
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of
nicklas.a...@j
proposed postgis book?
Cheers
Mark
On Tue, Mar 10, 2009 at 12:16 PM, Obe, Regina
wrote:
Mark,
I'm a bit confused, for your second query, are those points
suppose to represent user input and in long lat? They don't look like
long lat. If they are meant to b
Mark,
I'm a bit confused, for your second query, are those points suppose to
represent user input and in long lat? They don't look like long lat.
If they are meant to be long lat, then your args are just backwards.
The basic idea I think you want to do is
1) Take user input which I presume
EEHab,
Do you need to return the values or just insert them?
If you don't need them returned it is much easier and efficient to just
return boolean true, or if you need to return the values,
do as Alex suggested (change to RETURNS setof integer and use a RETURN
NEXT syntax).
There are easie
Devrim,
I think if you are just going from 1.3.1 to 1.3.5 running the
lwpostgis_upgrade.sql
should be all you need to do. I don't think any aggregate functions were
changed between those 2 which is usually the thing that doesn't come over with
minor versions.
Hope that helps,
Regina
I use OGR2OGR for that.
http://www.bostongis.com/PrinterFriendly.aspx?content_name=ogr_cheatshee
t
There is a section further down on importing personal geo database.
I've been successful importing 1 million record table, but have never
tried a bigger set so not sure how much you can get away w
Behalf Of Obe,
Regina
Sent: Thursday, February 19, 2009 10:29 AM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] Re: maximum distance between a POINT and
POLYGON
It hasn't been implemented. Well it was a long long time ago, but the
logic was incorrect so it was turned off.
We pl
It hasn't been implemented. Well it was a long long time ago, but the
logic was incorrect so it was turned off.
We plan to bring it back probably in a 1.4.something or 1.5
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis
Use the -W latin1 switch in shp2pgsql and see if that fixes it.
the latin1 should be the encoding of your file, but latin1 always seems
to work for my datasets anyway.
Hope that helps,
Regina
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-
ssage-
From: Obe, Regina
Sent: Thursday, February 12, 2009 11:07 AM
To: 'PostGIS Users Discussion'
Subject: RE: [postgis-users] points from st_distance
Well distance actually is not implemented in GEOS. PostGIS uses its own
algorithm for that as I recall.
-Original Message
Well distance actually is not implemented in GEOS. PostGIS uses its own
algorithm for that as I recall.
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of
Stephen Woodbridge
Sent: Thursday, February 1
o.unipd.it/cirgeo/francescopirotti.htm
-- Original Message --
To: PostGIS Users Discussion (postgis-users@postgis.refractions.net)
From: Obe, Regina (robe@cityofboston.gov)
Subject: RE: [postgis-users] 3D Topology
Date: 2/1/2009 5:16:10
Depends what you are trying to do. P
Mark,
Lets say your table is called sometable and is in 4326 projection, then
it would look something like
SELECT ebas.ebaname, distance(ebas.the_geom, pt.the_geom) as
Distance_Metres
FROM ebas
INNER JOIN
(SELECT gid, ST_Transform(the_geom, 32662) As the_geom
FROM sometable WHERE gid = 1)
You should be able to use 8.2 and above. I've been testing on 8.3 and
8,4.
(I think we may have scrapped support for 8.1 in 1.4 but can't remember)
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Beh
Bruce,
Have you taken a look at PortableGIS? It has a USB version of
PostgreSQL with a bunch of other popular Open Source GIS tools.
Might be ideal for what you are doing.
Though I think its only windows version.
http://www.archaeogeek.com/blog/portable-gis/
hope that helps,
Regina
-Or
] On Behalf Of Obe,
Regina
Sent: Wednesday, January 28, 2009 7:14 AM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] forced conversion of linestring
tomulitlinestringwhen using shp2pgsql utility ?
Roman,
If you have mixed linestrings and multilinestrings, I would just bring
in the data
Roman,
If you have mixed linestrings and multilinestrings, I would just bring
in the data without the -S option as you were into a temp table.
Then what you do is create a new table using the create structure of
your original (minus the geometry field).
If you use PgAdmin, you can use the gen
If all your linestrings are actually linestrings, then you can use the
shp2pgsql
-S option
The -S will force into single mode and if it can't, then it will throw
an error.
If you actually have multilinestrings, then what I do is bring it into a
temp table as linestrings and use ST_Dump
http://p
-boun...@postgis.refractions.net on behalf of Maria Arias de
Reyna
Sent: Tue 1/20/2009 10:01 AM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] lspostgis.sql shows errors
El Martes 20 Enero 2009 13:13, Obe, Regina escribió:
> Strange. Is it the same error as you got before?
>
> W
Strange. Is it the same error as you got before?
What does
SELECT * FROM pg_settings WHERE name = 'search_path'
return.
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Maria Arias
de Reyna
Se
WMS calls.
Thanks,
Regina
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Obe,
Regina
Sent: Friday, January 16, 2009 9:00 AM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] Mapinfo
Oh ye
Oh yes I forgot the WMS WFS route. In older versions of MapInfo I think
like MapInfo 7 - I was able to use a WMS UMN mapserver connection.
In later versions of Map Info I think they introduced WFS, but I have
yet to try that out.
-Original Message-
From: postgis-users-boun...@postgis
Behalf Of Obe,
Regina
Sent: Thursday, January 15, 2009 3:00 PM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] Re: st_union exception
3.0.3 is the latest stable
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun
3.0.3 is the latest stable
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Mark
Mitchell
Sent: Thursday, January 15, 2009 2:38 PM
To: postgis-users@postgis.refractions.net
Subject: [postgis-users] R
Oliver,
Disregard my last comment - I see you did try plain &&. So as expected it is
faster
than ST_Intersects and given your geometries are so large, this is not
surprising. Yes it && should be slower than doing a btree search too.
I think Paul is on to something. for those large geometrie
What happens if you leave out ST_Intersects and just use
&& instead of doing ST_Intersects?
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of
Oliver Snowden
Sent: Friday, January 09, 2009 10:22 AM
> If this is the case, it seems Oliver is almost certainly being bitten
by
> the && operator RECHECK :(
Will looking at it
" Join Filter: ((selected_geography.the_geom && geography.the_geom)
> AND _st_intersects(selected_geography.the_geom, geography.the_geom))"
It doesn't even appear to
> -- EXPLAIN ANALYZE STEP 4 (intersect Asia continent over all other
geographies)
> -- 81 rows, ~13000ms - a large increase in query time.
> EXPLAIN ANALYZE SELECT geolink.report_id, geography.gid
> FROM gdors_geolink geolink, gdors_geography geography, gdors_geography
> selected_geography
> WHERE
> i) PostgreSQL 8.3 has a new costing model which we have seen in some
> cases causes evaluation of the more expensive _st_intersects()
function
> above the && operator. As yet we don't really have a system that we
can
> use to verify this properly :(
> However, if you still have your origina
sers] Help with spatial query
Dear Regina,
Thank you so much for the quick response.
best regards,
surya
- Original Message -
From: "Obe, Regina"
To: "PostGIS Users Discussion"
Sent: Thursday, January 08, 2009 2:22 AM
Subject: RE: [postgis-users] Help with spa
Surya,
Not sure if these answer your question
1) If you want to list all 500 districts for a given watershed
regardless of if any of it lies in watershed, then you would do
SELECT d.district_name, w.ws_name,
CASE WHEN ST_Intersects(w.the_geom, d.the_geom)
THEN
ST_Are
P Adj,
The GRANT SELECT, INSERT, UPDATE, DELETE ON public.Geometry_columns TO
username;
simply gives the designated user rights to read, add, delete, update the
geometry_columns table which is the table that holds meta data about
each geometry column in the database.
http://postgis.refractions
By buffering, you mean draw a buffer around a geometry or count things
in a buffer.
Look at
1) ST_Buffer for drawing a buffer --
http://postgis.refractions.net/documentation/manual-svn/ST_Buffer.html
2) ST_DWithin for finding out all geometries that fall in a buffer --
http://postgis.refractio
Depends what you are trying to do. PostGIS has very primitive support for 3D.
1) 3D volumetric objects are not supported
2) 3D non-volume are supported partly -- e.g. a 2D polygon in 3 d space, a
line, point in 3d space.
3) Spatial relationships however only really consider the spatial component
What I was thinking of was this.
CREATE OR REPLACE FUNCTION upgis_filter_rings(geometry,float) RETURNS geometry
AS
$$ SELECT ST_BuildArea(ST_Collect(a.geom)) as final_geom
FROM ST_DumpRings($1) AS a
WHERE a.path[1] = 0 OR
(a.path[1] > 0 AND ST_Area(a.geom) > $2)
You wouldn't use that for tagging. That is used if you want to prevent
people from adding invalid geometries into your table. If you have
already got invalid geometries it will just fail since you have already
violated the rule you are trying to establish.
To add a field
ALTER TABLE mytable ADD
I think the newsgroup is probably better even if it creates a bit of traffic.
Its probably good traffic for future reference for others anyway.
Thanks,
Regina
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net
Try
SELECT c2.name As county, c1.name As city
FROM OKCounties c2 LEFT JOIN OK_Cities c1
ON (st_within(c1.the_geom,c2.the_geom)= true AND c1.feature='County
Seat')
WHERE c1.Name IS NULL
Order by c2.Name asc;
From: postgis-users-boun...@postgis.refraction
Andreas,
I think you have unearthed one of the cruel lessons of floating point math.
Best described in Isaac Kunen's blog.
http://blogs.msdn.com/isaac/archive/2008/08/07/the-imprecise-nature-of-geometry.aspx
So we see it is not unique to PostGIS.
Hope that helps,
Regina
-Original Messag
nd use the
method you suggested on them.
/Nicklas
2008-12-29 Obe Regina wrote:
>
Why wouldn't you use a nearest neighbor calculation as demonstrated here (using
DISTINCT ON)?
>
>
http://postgis.refractions.net/documentation/manual-svn/ST_DWithin.html
>
>
Keep in mi
Why wouldn't you use a nearest neighbor calculation as demonstrated here (using
DISTINCT ON)?
http://postgis.refractions.net/documentation/manual-svn/ST_DWithin.html
Keep in mind ST_DWithin and ST_Distance don't care about whether a geometry is
a line or polygon or point or collection or wha
Anything you can do in PgAdmin you can do with a pass-thru query in MS
Access.
Take a look at this article which demonstrates making a TSearch query
with a pass-thru MS Access query.
http://www.postgresonline.com/journal/index.php?/archives/24-Using-MS-Ac
cess-with-PostgreSQL.html
You would d
Gus
>
> - Original Message -
> From: Obe, Regina
> To: PostGIS Users Discussion
> Sent: Thursday, December 18, 2008 5:08 PM
> Subject: RE: [postgis-users] pgsql2shp cuts varchar fields
> Not absolutely sure, but I think its a limit in the spec. I think fields >
>
Don,
Did you do a
make install
before you did the
make check
I think the docs were confusing in that regard, but I thought we fixed that.
The error you have below sounds like you probably compiled fine, but didn't
install the binary.
-Original Message-
From: postgis-users-boun...@
Not absolutely sure, but I think its a limit in the spec. I think fields > 254
are considered to be memo fields in the dbf world and so would be put in a .dbt.
Its been a while since I've done any DBase or Foxpro programming so my memory
could be wrong.
I've never actually seen .dbt files incl
Venkat,
This really isn't a PostGIS question.
But if you look here -- it tells you how to do it
http://npgsql.projects.postgresql.org/docs/manual/UserManual.html
(There are 2 ways -- you can store it as a bytea or as an LO) -- refer
to the parts of this manual
Working with binary data and
That's the problem with the wiki or my inability to use it. Try
stripping every where you see ?
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of
lisek lichu
Sent: Wednesday, December 17, 2
Look here
http://postgis.refractions.net/support/wiki/index.php?plpgsqlfunctions
I think the upgis_lineshift function does what you want.
So to create a parallel line to right of your center line do
SELECT upgis_lineshift(line.the_geom,x) As right_line,
upgis_lineshift(line.the_geom,-x) As l
Andrew,
Not sure I understand your question. Are you saying your street segments are
cut such that they only connect at junctions. Kind of like tiger tlids.
And given each intersection, you are trying to find continguous segments from
the intersection?
e.g.
---
Greg,
I noticed you have 3.0.2 here. Better bring that up to 3.0.3. I forget
what the distinctions are between the 2 aside from fixing some compile
issues that probably doesn't affect NETBSD, but you never know.
PostgreSQL 8.1.15 on i386--netbsdelf, compiled by GCC gcc (GCC) 4.1.3
20080202
te all the table with ST_GeomFromText() ??
Fred
On Wed, Dec 10, 2008 at 12:41 PM, Obe, Regina <[EMAIL PROTECTED]> wrote:
Fred and Ghislain,
Thanks - yes that's because of the rounding that happens in
ST_GeomFromText -- the ST_GeomFromText is rounding the
.
--
-- PostgreSQL database dump complete
--
Le 9 déc. 08 à 13:04, Obe, Regina a écrit :
Ghislain,
The only time I have seen this kind of behavior is when
centroid returns an e
ct b.id_parc, z.niv from bd_dispo_finalc as b, ZS2c as z
> otm-# where z.niv=1 and intersects(centroid(b.the_geom),z.the_geom)
> and b.the_geom && z.the_geom and isvalid(b.the_geom) and isvalid
> (z.the_geom);
> ERROR: Relate Operation called with a LWGEOMCOLLECTION type. This
> is
Many of the GEOS relation functions do not work with collections.
You must have a geometry collection in there somewhere or its a bug.
Also which relation function were you trying?
To figure out the type of your geometries, run
SELECT *
FROM sometable
WHERE GeometryType(the_geom) = 'GEOMETRYCOLL
What does ST_Intersects + ST_Relate give you and timing.
That's the one I was interested in if that is faster than
&& + ST_Relate
In theory those 2 should give you the same answer.
-Original Message-
From: [EMAIL PROTECTED] on behalf of William Kyngesburye
Sent: Fri 12/5/2008 5:34 PM
st regards,
Pedro Doria Meunier
Obe, Regina wrote:
>> By the way, are the Google Mercator and WGS84 systems equivalent
>>
>
> No they aren't. I think Google is a mercator meter projection (not
good
> for measurement though but more or less good for presentation) and
t
> By the way, are the Google Mercator and WGS84 systems equivalent
No they aren't. I think Google is a mercator meter projection (not good
for measurement though but more or less good for presentation) and they
use WGS84 datum when accepting data. I think it actually has an
official SRID (coul
s
hi!
2008/11/24 Obe, Regina <[EMAIL PROTECTED]>:
> I'm curious why you want to do this?
our databases holds a lot of
linestrings with more than 5000 points. these linestrings are
processed by external tools.
a few of this (crappy) tools can only handle linestrings with 500 or
l
, obviously this isn't in PostGIS right now.
Obe, Regina wrote:
>
> Evidentally its this thing
> http://ubicomp.algoritmi.uminho.pt/local/concavehull.html
>
> So I guess basically you take the boundary and you get rid of points
> that have points sitting to the right/left/top/or bot
Are scratch that thought. That's not right either.
-Original Message-
From: [EMAIL PROTECTED] on behalf of Obe, Regina
Sent: Mon 11/24/2008 2:16 PM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] Get concave hull from an array of
longitudeinlatitude points
Evidentall
Evidentally its this thing
http://ubicomp.algoritmi.uminho.pt/local/concavehull.html
So I guess basically you take the boundary and you get rid of points
that have points sitting to the right/left/top/or bottom of it and then
you form a polygon from the remaining points.
Well at least that is wha
Richard,
I'm curious why you want to do this?
The answer is I think NO, but someone correct me if I am wrong. I think
the tolerance argument of ST_Simplify is the max distance allowed
between any 2 closest points of the original and simplified. Though
that's a bit vague to me.
Also I would rec
How about ST_Boundary?
http://postgis.refractions.net/documentation/manual-svn/ST_Boundary.html
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Travis Kirstine
Sent: Friday, November 21, 2008 10:18 AM
To: PostGIS Users Discussion
Subject: [postgis-users] r
Yah its worth a note. Guess that should be done for ST_Transform too.
Any other functions require Proj?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Cave-Ayland
Sent: Wednesday, November 19, 2008 11:12 AM
To: PostGIS Users Discussion
Subject: Re:
nstalled.
Thanks,
Regina
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Cave-Ayland
Sent: Wednesday, November 19, 2008 7:15 AM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] PostGIS 1.3.4 RC3 released
Obe, Regina wrote:
> Mark,
>
> Does t
Dylan,
ST_AsKML(geometry) works for me fine in 1.3.3 and 1.3.4. Are you sure you ran
the lwpostgis_upgrade.sql file last time you upgraded your db.
I recall ST_AsKML... throwing an error if you didn't upgrade the procs. You
can tell by running
SELECT postgis_full_version()
If it says somet
Mark,
Does this count toward your goal or were you looking more for 8.1?
I installed a fresh PostgreSQL 8.3.5, Geos 3.0.3 RC1, PostGIS 1.3.4SVN
on a Red Hat Enterprise Linux 4 and it passed all regression tests and I
was able to reload my data back. Hmm on hindsight, I guess I should
have also t
Nicholas,
Try instead
SELECT r.name
FROM (SELECT ST_Boundary(the_geom) As b_geom
FROM state WHERE name ~* 'Nana') As s
INNER JOIN road r ON ST_DWithin(s.b_geom, r.the_geom, 0.001)
1) Buffer is a relatively slow operation in PostGIS. Faster to do a
distance within check.
2) As I a
GIS Day in Boston is Wednesday Nov 19, 2008.
If any of you happen to be in town, feel free to stop by.
Details are here
http://www.cityofboston.gov/maps/
I'll be giving a small little presentation on Abandoned Property Survey
which uses Mapserver, MassGIS webservices, PostGIS back-end, OpenLaye
Stan,
This looks good. I would add a couple of suggestions
1) ST_Equals doesn't include an && check. I know it seems like an
oversight to me and I think Kevin even mentioned it and possibly fixed
it. Might be changed in 1.4 (and maybe 1.3.4)
2) With the self-join you have you lose the penalty
I think I may have figured out the problem. I tried the file. It doesn't load
into a UTF-8 encoded database. You need to use the -W switch if you have a
UTF-8 encoded database.
Try
shp2pgsql -g the_geom -s 32648 -I -W "latin1" LopGiaoThong LopGiaoThong | psql
-U postgres -d postgi
I suspect Vinh's problem is not only with the SRID. PostGIS to my knowledge
doesn't do any validation of SRID when loading except to check its -1 or the
SRID is in the spatial_ref_sys (I don't think it even does that much where SRID
is concerned). Given that, there should never be a problem
One tiny problem.
Okay I tried upgrading my PostgreSQL 8.3 on my OpenSUSE 10.3 (which by
the way given my extreme laziness - I installed by installing the Linux
8.3 one click install binary I had installed a whil back from
http://www.postgresql.org/download/linux and is running on port 5433
instea
Willy,
Those functions all rely on the new GEOS (3+). So since you are running
the old GEOS on Ubuntu those don't get installed. That's the expected
behavior. You should upgrade your GEOS on ubuntu if you want to use
those.
Hope that helps,
Regina
From: [EMAI
> Kevin Neufeld wrote:
> > Hmmm. No, rerunning autogen didn't solve it. I thought maybe it
was a
> > Fedora Core 3 issue, but if it works on the rackmount (which is also
> > FC3), then I don't know. My server setup must be amiss.
> >
> > -- Kevin
> AFAIK the only part of the build system th
Wow you have one of those things lying around? I'm more impressed you
have one and doubly impressed it works. Great going Mark.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Cave-Ayland
Sent: Thursday, November 13, 2008 9:27 AM
To: PostGIS Users D
Damn typo
3) should be
UPDATE sometable SET new_column = ST_Transform(old_column, new_srid);
-Original Message-
From: [EMAIL PROTECTED] on behalf of Obe, Regina
Sent: Tue 11/11/2008 10:09 AM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] Coordinates transform
Yes. Use
vinh nguyenquang,
Where did you get this data from? According to the .prj it is in 4326 (WGS 84
degree) like
others have mentioned, but if you actually look at the data, there is no
way it is in degrees since it has points like
484344.9842453949 1480036.13293874
So there is no way that is 4326
Yes. Use ST_Transform.
Basic approach is
1) bring your data in with right SRID
2) Use AddGeometrycolumn to add a new column
http://postgis.refractions.net/documentation/manual-svn/AddGeometryColumn.html
to add a new column with new srid you want to use
3) Update the new column with
UPDATE ne
Anton,
I didn't even know PgRouting had a list. I'll have to join that one.
Personally I don't mind getting PgRouting questions on PostGIS list, mostly
because
the traffic on PostGIS is not that high enough yet and its kind of educational
to learn about
related projects that you don't know mu
Dara,
I just noticed your confusion, and its PostGIS fault. psql uses
uppercase U to denote user, and pgsql2shp uses lowercase u to denote
user.
Very confusing I know. Just noticed it. That must be immensely
frustrating.
From: [EMAIL PROTECTED]
[mailto:
The U should be lower case u.
pgsql2shp -f "/path/to/streets" -h myserver -u apguser -P apgpassword
mygisdb ma.streets
This cheatsheet might help
http://www.bostongis.com/pgsql2shp_shp2pgsql_quickguide.bqg?outputformat
=PDF
Hope that helps,
Regina
From: [E
load NAD27-83
correction file)
Though I suspect that's just a configuration error on my box when I
setup proj4.
Hope that helps,
Regina
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Obe,
Regina
Sent: Friday, October 31, 2008 8:12 AM
To: Pos
1 - 100 of 520 matches
Mail list logo
