The underlying code the parses the address string into fields is
parse_address(string)
stdaddr=# select * from parse_address('16 Berry Lane, schenectady, ny
12302');
num | street | street2 | address1|city | state |
zip | zipplus | country
-++-+-
I have installed the adress_standardizer (version 1.0) into a fresh install
of postgresql 9.3.1 with postgis 2.1.0 and I am finding an issue with the
address normalizer.
If I give the following valid address, it works...
db=# select internal, location, stateabbrev from pagc_normalize_address('16
Hi Brent,
I'm putting this back on the list so people can see our continued discussion.
I'm confused by what ST_Dump() does in this example. Could you explain a
little more what it is doing?
I agree with you and Paul that windowing might be my best approach. I'm
looking at how I might accomp
Hey,
here is a draft for a page about using QGIS with PostGIS
Anybody can edit it .
http://trac.osgeo.org/postgis/wiki/UsersWikiQGIS
Cheers,
Rémi-C
2013/10/29 Rémi Cura
> Exactly, it works !
> Same problem for images though ? Shall I create a proxy ticket to host
> images about using QGIS?
>
Exactly, it works !
Same problem for images though ? Shall I create a proxy ticket to host
images about using QGIS?
Cheers,
Rémi-C
2013/10/29 Sandro Santilli
> On Mon, Oct 28, 2013 at 02:38:54PM +0100, Rémi Cura wrote:
>
> > I'm a wiki noob, can you provide me a link to create a new page (logg
Hey Sandro,
I disagree,
None of the points returned are "truly" on the line (coordinates should be
fraction, like in CGAL), but close enough to be considered on the line.
It's an hypothesis implictly hard written in all the spatial testing
function because they work up to a certain precision (prob
On Tue, Oct 29, 2013 at 12:52:28PM +0100, Rémi Cura wrote:
> The problem is there is no function ST_Snap( a point to a line), only
> ST_Snap (a line to a point) !
>
> I don't know why because snapping a line to a point is way more difficult.!
Snapping a point to a line can be _impossible_.
Not al
On Mon, Oct 28, 2013 at 02:38:54PM +0100, Rémi Cura wrote:
> I'm a wiki noob, can you provide me a link to create a new page (logged
> with my osgeo loggin, I couldn't find the button to add a new page)
> http://trac.osgeo.org/postgis/wiki/UsersWikiMain
I think you just write a CamelCase title in
I use St_intersects only to test the ST_ClosestPoint.
ST_Dwithin(ST_ClosestPoint(line,pt), line,0.001) return true
2013/10/29 Rémi Cura
> Do you really need st_intersects?
>
> Can you use ST_Dwithin(point, line, your_precision) instead?
>
> Cheers,
>
> Rémi-C
>
>
> 2013/10/29 franco base
>
>>
The problem is there is no function ST_Snap( a point to a line), only
ST_Snap (a line to a point) !
I don't know why because snapping a line to a point is way more difficult.!
Cheers,
Rémi-C
2013/10/29 Rémi Cura
> Do you really need st_intersects?
>
> Can you use ST_Dwithin(point, line, your
Do you really need st_intersects?
Can you use ST_Dwithin(point, line, your_precision) instead?
Cheers,
Rémi-C
2013/10/29 franco base
> Thanks Remi
> You are very clear now.
>
> Meanwhile I make some test and I think there is a bug somewhere.
> I use the ST_ClosestPoint example documenation
>
Thanks Remi
You are very clear now.
Meanwhile I make some test and I think there is a bug somewhere.
I use the ST_ClosestPoint example documenation
SELECT ST_AsText(ST_ClosestPoint(pt,line)) AS cp_pt_line,
ST_AsText(ST_ClosestPoint(line,pt)) As cp_line_pt,
ST
Hey sorry for being unclear.
I put you a pseudo code and some explanation :
- first you work with real world data (observation, measure), which are
of a given precision (showing the uncertainty of the measure).
If your data are real world observation ,they may be precise up to the
cen
Hi there,
I hope someone can assist in pointing a PostGIS newbie in the right direction.
Using the following explicit Maven dependency:
org.postgis
postgis-jdbc
1.3.3
Where transitive dependencies on postgis-stubs (1.3.3) and
postgresql-8.3-603.jdbc4.jar are also pulled in.
Executin
Ayway
St_split and St_snap don't work
SELECT line,
point,
st_contains (st_snap (geom_line, geom_point,0.001), geom_point),
st_geometrytype ((st_dump(ST_split(st_snap (geom_line, geom_point,0.001),
geom_point))).geom),
(st_dump(ST_split(st_snap (geom_line, geom_point,0.001), geom_point))).geom
as s
Hi.
Yes the cause can be that every function has his own "tolerance"
SELECT line,geom_line,point,geom_point,
ST_ClosestPoint(geom_line,geom_point), - return geometry=geom_point
ST_distance (geom_line,geom_point), return 0
ST_contains(geom_line,geom_point) return false
"line";"geom_l
Thanks Remi,
I am looking at a SpatialLite solution now. Many thanks for your inputs.
The WMS approach is a little advanced at the moment so we will stick to the
data sharing approach.
Regards,
Wesley
On Tue, Oct 29, 2013 at 10:40 AM, Rémi Cura wrote:
>
> We don't know much about your organis
We don't know much about your organisation,
you may went to send all your data for each review, this is similar to
sending shapefile, and to sending a one file sqlite database.
On the other hand you can simply give access to your data trough internet
to your reviewers (and only them). This way the
Dear Rémi-C and Bo Victor,
Many thanks for your responses. It seems my idea will not work as I
thought. Perhaps I should look for alternative methods to share my data. My
main aim is to reduce the clutter of sharing shapefiles and making it
easier for the auditor to access and use our data. Perhap
19 matches
Mail list logo
