Sven Geggus li...@fuchsschwanzdomain.de wrote:
Currently the patch has not been tested in conjunction with
incemental database updates.
OK, in the meantime I can confirm, that incemental database updates
work fine. I just fixed a problem with polygons (SVN r20565). When
using hstores we need a
Sven Geggus lists at fuchsschwanzdomain.de writes:
Hello,
I just commited a patch for osm2pgsl for optional generation of a
hstore column (hstore new).
Hi,
Sounds great. I had been thinkin about splitting geometries and tags to a pairs
of tables (one with columns geometry and osm_id,
Very cool. Now we just need to find a way to use it. I thought about
it earlier but I didn't see a way to make mapnik use it so left it.
Have a nice day,
On Sun, Mar 14, 2010 at 4:47 PM, Sven Geggus
li...@fuchsschwanzdomain.de wrote:
Hello,
I just commited a patch for osm2pgsl for optional
Sven Geggus wrote:
Now we would just need something like this:
select way,(tags-'man_made') as man_made FROM planet_osm_point where
((tags-'man_made') is not NULL);
What am I getting wrong here?
Nothing. This will work. Mapnik just expects the name used in a filter
to correspond with a
Lennard l...@xs4all.nl wrote:
Very cool this. What's the speed to access the hstore column, compared
to the generic columns we now have?
I did not yet try to measure this.
On the one hand, this has the potential to greatly increase the size of
the db, as you will now get all kinds of tags
5 matches
Mail list logo
