...@postgis.refractions.net] *On Behalf Of
*Don
*Sent:* Tuesday, April 12, 2011 3:08 AM
*To:* PostGIS Users Discussion
*Subject:* Re: [postgis-users] Linux geocoder script ?
My database is encoded as
geocoder | drh | UTF8 | C | en_US.UTF-8 | .
All my shp2pgsql statements have
-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] *On Behalf Of *Don
*Sent:* Tuesday, April 12, 2011 3:08 AM
*To:* PostGIS Users Discussion
*Subject:* Re: [postgis-users] Linux geocoder script ?
My database is encoded as
geocoder | drh | UTF8 | C
...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Don
Sent: Wednesday, April 13, 2011 5:40 AM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] Linux geocoder script ?
Here is the version:
RELEASE: 2.0 USE_GEOS=1 USE_PROJ=1 USE_STATS=1 (r$Id
ilto:postgis-users-boun...@postgis.refractions.net]
On Behalf Of Don
Sent: Tuesday, April 12, 2011 3:08 AM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] "Linux" geocoder script
?
My database i
My database is encoded as
geocoder | drh | UTF8 | C | en_US.UTF-8 | .
All my shp2pgsql statements have the -W option like this.
${loader} -a -s 4269 -g the_geom -W latin1 $z
${staging_schema}.${state_abbrev}_${table_name} | $PGBIN/psql -d
$PGDATABASE;
Here is the bug that
Hello,
To convert you data without W flag of shp2pgsql (who seem be the
problem), you can use SET CLIENT_ENCODING TO 'latin1' at the begin
of the sql file. This will convert all string type column only
(e.g. varchar, text, char).
Or more simply, try this.
I have got the tiger2010 geodecoder to work on my Opensuse system.
geocoder=#
geocoder=# SELECT g.rating,
geocoder-# ST_X(geomout) As lon,
geocoder-# ST_Y(geomout) As lat, (addy).*
geocoder-# FROM geocode('1731 New Hampshire Avenue Northwest,
Washington, DC 20010') As g;
rating
Hello,
This is not a shp2pgsql bug. You get this error when you try to insert
string data in PostgreSQL from another encoding that the one of your
database Ex: Your data is formatted in Latin1 (ISO-8859-1) and you
insert them in a UTF-8 database. To fix the error message, you need to
convert
On Sat, Mar 26, 2011 at 07:05:48PM -0400, Paragon Corporation wrote:
Sorry to bring the whole money thing, but I feel people tend to lose sight
of that, that most of the PostGIS development team contributes back stuff
they were getting paid to work on and also work in general that has no
On 27-3-2011 11:14, Sandro Santilli wrote:
On Sat, Mar 26, 2011 at 07:05:48PM -0400, Paragon Corporation wrote:
Sorry to bring the whole money thing, but I feel people tend to lose sight
of that, that most of the PostGIS development team contributes back stuff
they were getting paid to work
On 27-3-2011 11:14, Sandro Santilli wrote:
On Sat, Mar 26, 2011 at 07:05:48PM -0400, Paragon Corporation wrote:
Sorry to bring the whole money thing, but I feel people tend to lose
sight of that, that most of the PostGIS development team contributes
back stuff they were getting paid to
fork forkandwait at gmail.com writes:
One of these days hopefully soon, I'll dust off my OpenSUSE VM and
build PostGIS 2.0 and test Tiger geocoder on it.
Turns out we might have to test this and get it to work on Linux sooner than
later since we have a prospective client running on Linux
Paragon Corporation lr at pcorp.us writes:
You might want to also look at the script in the legacy_import folder of
tiger_2010.
That was a script set up by Steve Frost for 2008 when he reworked the tiger
geocoder to work with the new shp format. We couldn't use that because the
client we
On 3/26/2011 1:39 PM, fork wrote:
Paragon Corporationlrat pcorp.us writes:
You might want to also look at the script in the legacy_import folder of
tiger_2010.
That was a script set up by Steve Frost for 2008 when he reworked the tiger
geocoder to work with the new shp format. We
Fork,
(One pendantic note -- sh or bash are *Unix* centric, not linux --
they are the standard on Freebsd, etc).
Yap you already said that more than once.
We changed the loader name to sh and also fixed some obvious typos we have.
We did have someone on linux test our older ones and he was
Fork,
Forgot to mention:
We did also move some variables to the top for easier setting.
Unfortunately I don't think we can do that for the state names and codes as
you are trying to do because then we'd have to make the loader tables
portion be intelligent about the vaious OS variable
fork forkandwait at gmail.com writes:
Paragon Corporation lr at pcorp.us writes:
One of these days hopefully soon, I'll dust off my OpenSUSE VM and build
PostGIS 2.0 and test Tiger geocoder on it.
fork forkandwait at gmail.com writes:
One of these days hopefully soon, I'll dust off
I have got the geocoder loaded (thanks Regina), but I am a little bit baffled by
the output of the Linux script.
Is it supposed to be bash or sh? Really there is no linux script...
Also, there is an error on the documentation page, unless I am mistaken:
TMPDIR=/gisdata/temp/
should be
I had the same problem on my Linux install last week. Basically, I had
to edit the bash script line-by-line to get it to work on my Fedora
box. I plan on submitting my corrections/improvements when I find the
time this week.
I'm impressed with the functionality of the geocoder and appreciate
all
Daniel Ball danpelota at gmail.com writes:
I had the same problem on my Linux install last week. Basically, I had
to edit the bash script line-by-line to get it to work on my Fedora
box. I plan on submitting my corrections/improvements when I find the
time this week.
Cool, in the sense that
] On Behalf Of fork
Sent: Tuesday, March 22, 2011 7:14 PM
To: postgis-users@postgis.refractions.net
Subject: [postgis-users] Linux geocoder script ?
I have got the geocoder loaded (thanks Regina), but I am a little bit
baffled by the output of the Linux script.
Is it supposed to be bash or sh? Really
Paragon Corporation lr at pcorp.us writes:
Fork,
Haven't had a chance to test on Linux yet. That's on my todo to fix the
Linux, but sadly haven't gotten to it.
It's all good!
I would think about the loader script pretty hard ... it is pretty far from
usable. I would definitely call it
Subject: Re: [postgis-users] Linux geocoder script ?
Paragon Corporation lr at pcorp.us writes:
Fork,
Haven't had a chance to test on Linux yet. That's on my todo to fix
the Linux, but sadly haven't gotten to it.
It's all good!
I would think about the loader script pretty hard
Paragon Corporation lr at pcorp.us writes:
It shouldn't be too much of a rework. Most of those things are in variables
in the respective tiger tables.
Yeah, storing the necessary pieces seems well thought out and straightforward.
However, the code just isn't shell at all and there are a
24 matches
Mail list logo
