ambre
Subject: Re: [postgis-users] Traverse set distance along a multiline?
To: postgis-users@postgis.refractions.net
Date: Wednesday, December 29, 2010, 5:00 AM
Just want to again say thanks for all the help on this.
After projecting from 4269 to 3081, I reanalyzed everything and checked my
p
in January. if I have the time.
Cheers,
Brent
--- On Tue, 12/28/10, Ben Madin wrote:
From: Ben Madin
Subject: Re: [postgis-users] Traverse set distance along a multiline becoming
multiple storage columns?
To: "PostGIS Users Discussion"
Cc: "Brent Wood"
Date: Tuesday, December
Just want to again say thanks for all the help on this.
After projecting from 4269 to 3081, I reanalyzed everything and checked my
points sample again. All my points at major intersections and state borders
were <= 1 mile off! That's good enough for me.
Now my next two problems (which I need to r
just another column in spatially
> enabled database. If you really don't need to keep the original column, you
> can always drop it from the table after creating the 3081 version.
>
> Having a second table also works, but I figured I'd mention this
> alternative.
>
> C
e. If you really don't need to keep the original column, you
> can always drop it from the table after creating the 3081 version.
>
> Having a second table also works, but I figured I'd mention this alternative.
>
> Cheers,
>
> Brent Wood
>
> --- On Tue, 12/28/10,
can always
drop it from the table after creating the 3081 version.
Having a second table also works, but I figured I'd mention this alternative.
Cheers,
Brent Wood
--- On Tue, 12/28/10, Aren Cambre wrote:
From: Aren Cambre
Subject: Re: [postgis-users] Traverse set distance along a mul
Thank you. Now my shp2pgsql conversion results in a PostGIS table with an
SRID. I then ran this query to reproject the data into a new table:
*INSERT INTO txdot_roadways_3081_transform*
*SELECT [all other fields go here], ST_Transform(the_geom, 3081) as the_geom
*
*FROM txdot_roadways;*
Loading in
Right, use 4269, that's a good NAD83-geographic-coordinates number.
Import with shp2pgsql -s 4269 and go from there.
P
On Mon, Dec 27, 2010 at 3:54 PM, Aren Cambre wrote:
> Brent and Paul,
> Thank you for your help!
> So here's my (new) dilemma--my PostGIS table doesn't appear to have a
> projec
Brent and Paul,
Thank you for your help!
So here's my (new) dilemma--my PostGIS table doesn't appear to have a
projection specified, and I am not clear how to get to one.
I don't think it has a projection because this table's corresponding entry
in the *geometry_columns* table has *-1* for the *
You need to do your analysis in a projected coordinate system, not geographics.
CREATE TABLE my_new_texas_roads AS
SELECT ST_Transform(the_geom, 3081) as the_geom, other_attributes
FROM texas_roads;
EPSG:3081 should be a good coordinate system for working with your Texas data.
http://spatialref
I am trying to determine mile markers along Texas highways. My starting
point is the ShapeFile TxDOT Roadways 2010 at
http://www.tnris.state.tx.us/datadownload/download.jsp. I've used shp2pgsql
to get it into a PostGIS 1.52-enabled Postgres 9.01 database.
I naively thought I could just figure out
11 matches
Mail list logo
