You cannot rely on a point computed by ST_Intersection returning
ST_Intersects = true. Instead you need to test using a small
distance tolerance, using ST_DWithin.
On Fri, Apr 24, 2020 at 7:55 AM David Campbell
wrote:
> Thanks for getting back to me.
>
> I see you have the problem solved as tru
On 4/25/2020 7:19 PM, Shaozhong SHI wrote:
Hi, Steve,
Many thanks. Please send me the link to parse_address() and
standardize_address().
If you already have postGIS installed then
create extension address_standardizer;
# \df parse_address
List of functions
Schema | Name | Result
Hi, Steve,
Many thanks. Please send me the link to parse_address() and
standardize_address().
I need to find these first before test-running.
Regards,
Shao
On Sat, 25 Apr 2020 at 21:20, Stephen Woodbridge <
stephenwoodbridg...@gmail.com> wrote:
> Shao,
>
> '^( *Building *[0-9]+)?[- 0-9]*'
>
Shao,
'^( *Building *[0-9]+)?[- 0-9]*'
or something like that should do it. But I think you will find that a
more robust solution is to use parse_address() and/or
standardize_address() as they will recognize a lot of other address
constructs, like "apt 3a" for for example.
parse_address() t
Is there a way to left trim including the building and number?
Building 3 21-1 Great Avenue, a city, a country, this planet.
How to take way those things which are too local to an address?
Regards,
Shao
On Sat, 25 Apr 2020 at 01:48, Shaozhong SHI wrote:
> I find this is a simpl
Good morning everyone,
I need support about ST_InvDistWeight4ma.
Is it possible to do IDW to full band into the RASTER with only 8 pixels
with value?
I tried with:
UPDATE ch07.idwlpa SET rast=st_mapalgebra (rast,2,
'st_InvDistWeight4ma(double precision
[][][],integer[][
Thanks to everyone.
Steve W, at the moment, I will be interested in exploring SQL regexp to
handle addresses. It will be useful, if we can also deal with minor human
errors in the addresses.
Regards,
Shao
On Sat, 25 Apr 2020 at 05:09, Stephen Woodbridge <
stephenwoodbridg...@gmail.com> wrote:
