On Tue, Dec 10, 2013 at 7:00 AM, Paolo Cavallini cavall...@faunalia.it wrote:
Hi Luca,
you really need to use full topology for this.
ST_SimplifyPreserveTopology simply prevents topological errors, it
does not guarantee sharing of nodes etc.
Good luck.
Exactly.
So, two ways to go with
On a more high level:
I'm guessing you are using the recursive cte to walk trough a graph.
There are ways to accelerate this, but at the cost of increase of memory
usage and duplication of data.
It depends a lot on you graph properties (has it a lots of nodes,
connectivity, centralness, etc)
(of
OK, so after making the changes suggested by Tommaso the query runs almost 50%
faster! Here’s the new query
WITH RECURSIVE flow(gid, geom) AS (
SELECT e.gid, e.geom FROM electric_line e, fuses f WHERE
ST_DWithin(e.geom,f.geom, 0.01) AND f.gid=15
UNION ALL
SELECT n.gid, n.geom
FROM
I have a table of multilines that the query below slows down considerably after
upgrading to postgis 2.1.0.
I am running the following Postgis.
POSTGIS=2.0.3 r11128 GEOS=3.4.2-CAPI-1.8.2 r3921 PROJ=Rel. 4.8.0, 6 March
2012 GDAL=GDAL 1.10.1, released 2013/08/26 LIBXML=2.7.3 LIBJSON=UNKNOWN
I asked this years ago, and I think Paul was less than pleased with me
(:-), but:
Has anyone, in the ensuing years looked at encoding radar data into a
postGIS database? We've a little idea that might benefit one project, and
getting the radar data into a good geospatial format would be
Steve,
That did the trick in a big way. I will make ANALYZE a step in my upgrade
process from now on.
My new query after the ANALYZE.
--select
flow_type,feat_type,encode(ST_AsBinary(ST_Force2D(the_geom),'NDR'),'h
ex') as geom,gid from basemap.water24k_line where the_geom
If you transform it to rasters PostGIS Raster can handle them already.
Now, about the new datatype, I'll let the experts discuss :P.
Cheers
On Tue, Dec 10, 2013 at 2:52 PM, Gerry Creager - NOAA Affiliate
gerry.crea...@noaa.gov wrote:
I asked this years ago, and I think Paul was less than
Gerry,
Seems like the biggest hangup would be in adding the data to the DB fast
enough. How many points, per revolution, and what is the frequency of a
revolution (stationary Radar, correct, although as I think about it, it could
be mobile if needed, just need to add in the radar location to
Hi, I'm running a postgres 9.1/postgis 1.5 platform on an AWS EC2 machine. I
want to move to the new AWS RDS postgresql set-up so I need a couple of steps
cleared up on transferring as it involves upgrading to postgis 2 at the same
time.
So far I've dumped the existing DB using:
pg_dump -Fc
Paul,
Cool! And yes, anytime you load a database or table like from shp2pgsql
you should analyze it to update the database statistics other wise the
planner has no information about what indexes to use. This might be a
good practice after adding a new index or making lots of changes to an
Raster is always a possibility, but we lose some data therein. If I use
what we refer to as Level III data, then it's certainly a potential. I'm
sorta thinking of using Level II data which comprise
azimuth/range/elevation and one of: reflectivity, radial velocity or
spectrum width (standard
I'm glad this might work out for you.
I'm not familiar with the products you guys generate or store, but you can
even store rasters with more then one band, keeping all the data in a
single place, but different bands.
On Tue, Dec 10, 2013 at 3:15 PM, Gerry Creager - NOAA Affiliate
If your radar return is well discretized in time (I'd say max 10^6
points/sec),
pointcloud could do the trick (you can have any number of attributes per
point).
Else, you would have to cut the data into pieces.
Cheers,
Rémi-C
2013/12/10 George Silva georger.si...@gmail.com
I'm glad this might
Might also be a nice thing for us to add to the end of the load process :/
On Tue, Dec 10, 2013 at 12:09 PM, Stephen Woodbridge
wood...@swoodbridge.com wrote:
Paul,
Cool! And yes, anytime you load a database or table like from shp2pgsql you
should analyze it to update the database statistics
You might have to put the password into the environment to avoid the
prompt screwing up the pipe...
export PGPASSWORD=yourpassword
(Im' assuming you've already tested psql connectivity and ensured you
can in fact connect via psql)
P.
On Tue, Dec 10, 2013 at 12:05 PM, Paul Caroline Lewis
srsDimension has inconsistent values, could that be it? (error message
seems pretty small :)
On Tue, Dec 10, 2013 at 12:36 PM, Dave Potts dave.po...@pinan.co.uk wrote:
Hi List,
I am trying to load some gml data, most of the time it works, but some of
the records fail with constructs such as
Bob
At least preliminarily, I can post-process, so speed of db adds isn't too
troubling. Maintaining accurate representation of the bin-volume data is,
however, important.
Typical rotation is 1-3 RPM, and a complete volume scan takes ~11 min in
clear air (where you best see biologicals if so
On Tue, Dec 10, 2013 at 05:05:16PM +, Paul Caroline Lewis wrote:
perl utils/postgis_restore.pl /some_location/db.backup | psql -h
aws-auth-stuff.aws-region.rds.amazonaws.com -p 5432 -U user database 2
errors.txt
All this does is ask for the DB password and once entered just returns to
Bob, all:
I agree. I'll have to spend some time with pointcloud but it DOES look very
promising.
Another application? Lidar. Pointed at the sky, not at the ground (we use
'em to determine cloud layers [ceiling] and sky cover at airports for
aviation data...).
Thanks, all!
gerry
On Tue, Dec
I can connect fine using psql and a select version(); responds
with--
PostgreSQL 9.3.1 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.6.3
20120306 (Red Hat 4.6.3-2), 64-bitI have
Did you install PostGIS and topology extensions in your new DB BEFORE
doing your command?
CREATE EXTENSION postgis;
CREATE EXTENSION topology;
Run also legacy.sql in your new DB to ensure compliance with the old
PostGIS functions if you use PostGIS with an old application. The script
On 10/12/13 17:00, Paolo Cavallini wrote:
Hi Luca,
you really need to use full topology for this.
ST_SimplifyPreserveTopology simply prevents topological errors, it
does not guarantee sharing of nodes etc.
Thanks for your answer Paolo, but our issue is how prevent simplification when it
On 10/12/13 18:10, Hugues François wrote:
Hello,
You should also have a look at some functions made by Nicolas Ribot :
http://trac.osgeo.org/postgis/wiki/UsersWikiSimplifyPreserveTopology
Looking at them I did a while ago, but I don't think they can help for this
specific issue.
Regards,
23 matches
Mail list logo
