On 2/16/2012 6:00 PM, Jochen Topf wrote:
Generic key names can be confusing, especially when one OSM object is used for
multiple things. Say there is a way tagged as railway and at the same time this
way is part of an area tagged as a generating station. Does power_source mean
the type of
On Fri, Feb 17, 2012 at 07:44:41AM +, Jukka Rahkonen wrote:
Frederik Ramm frederik at remote.org writes:
Hi,
On 02/16/2012 07:25 PM, Graham Jones wrote:
This reminded me of a question I have been meaning to ask for quite a
while - is a database generated by osm2pgsql with an
- is a database generated by osm2pgsql with an hstore expected to perform
similarly to one without?
It performs at the same speed for me.
Of course you're not supposed to use hstore for every tag, but just
for those on highest zoom levels, where spatial indexes are used
mostly, not indexes for
Komяpa writes:
- is a database generated by osm2pgsql with an hstore expected to perform
similarly to one without?
It performs at the same speed for me.
Of course you're not supposed to use hstore for every tag, but just
for those on highest zoom levels, where spatial indexes are used
Thanks - I will give it another try - I have got a computer running Ubuntu
11.10, which has Postgres 9.1.2. I will create a second database with an
hstore and see how it compares.
Graham.
On 17 February 2012 11:36, Stephan Knauss o...@stephans-server.de wrote:
Komяpa writes:
- is a
Jochen Topf jochen at remote.org writes:
Much too slow. Requiring joins on every query is not a good idea. And having
the right indexes is important. You can't just index everything and hope it
would do the right thing. (The most important index btw is the geometry index
not the attribute
On Fri, Feb 17, 2012 at 02:02:26PM +, Jukka Rahkonen wrote:
Jochen Topf jochen at remote.org writes:
Much too slow. Requiring joins on every query is not a good idea. And having
the right indexes is important. You can't just index everything and hope it
would do the right thing.
On 16 February 2012 16:25, Frederik Ramm frede...@remote.org wrote:
Hi,
On 02/16/2012 03:05 PM, Kay Drangmeister wrote:
Isn't there a hstore in the rendering-db?
No.
This reminded me of a question I have been meaning to ask for quite a
while - is a database generated by osm2pgsql with
Hi,
On 02/16/2012 07:25 PM, Graham Jones wrote:
This reminded me of a question I have been meaning to ask for quite a
while - is a database generated by osm2pgsql with an hstore expected to
perform similarly to one without?
I never ran one with hstore when I think of what this must mean for
On 16 February 2012 18:51, Frederik Ramm frede...@remote.org wrote:
On 02/16/2012 07:25 PM, Graham Jones wrote:
This reminded me of a question I have been meaning to ask for quite a
while - is a database generated by osm2pgsql with an hstore expected to
perform similarly to one without?
I
On 16-2-2012 19:25, Graham Jones wrote:
grumble Why create a key generator:power_source rather than just use
power_source. power_source is much more generic so you could re-cycle
it for things like district heating, but generator:power_source is only
ever going to be used for generating
On Thu, Feb 16, 2012 at 06:25:30PM +, Graham Jones wrote:
grumble Why create a key generator:power_source rather than just use
power_source. power_source is much more generic so you could re-cycle it
for things like district heating, but generator:power_source is only ever
going to be
2012/2/17 Jochen Topf joc...@remote.org:
On Thu, Feb 16, 2012 at 06:25:30PM +, Graham Jones wrote:
Generic key names can be confusing, especially when one OSM object is used for
multiple things.
+1.
E.g. an object tagged barrier=fence, height=2, landuse=forest. In this
example you could
Frederik Ramm frederik at remote.org writes:
Hi,
On 02/16/2012 07:25 PM, Graham Jones wrote:
This reminded me of a question I have been meaning to ask for quite a
while - is a database generated by osm2pgsql with an hstore expected to
perform similarly to one without?
I never ran
14 matches
Mail list logo
