I have recently imported some OSM data in my PostgreSQL/PostGIS database thanks to Osmosis tool and I’m disappointed to see that GeoServer cannot handle PostGIS hstore field natively.
So I’m asking if there is an alternative way to handle hstore key/value pairs in WFS or even in WMS with SLD other than manipulating the database in order to add columns for keys that I’m interested in? May be I have missed some Osmosis configuration parameters which allow importing some tags in separate fields?
Is there any performance issue with hstore requests which can indicate a deliberate choice of non-implementing such a feature? Otherwise are changes planned to handle hstore fields?
On Thu, Feb 6, 2014 at 5:24 PM, Jule M <jule.thales@anonymised.com> wrote:
Hi,
I have recently imported some OSM data in my PostgreSQL/PostGIS database
thanks to Osmosis tool and I'm disappointed to see that GeoServer cannot
handle PostGIS hstore field natively.
So I'm asking if there is an alternative way to handle hstore key/value
pairs in WFS or even in WMS with SLD other than manipulating the database
in order to add columns for keys that I'm interested in? May be I have
missed some Osmosis configuration parameters which allow importing some
tags in separate fields?
Is there any performance issue with hstore requests which can indicate a
deliberate choice of non-implementing such a feature? Otherwise are changes
planned to handle hstore fields?
In seven years working in GeoServer I've hardly ever seen a deliberate
choice not to implement something.
But I've seen countless things that we would have liked to add, and that we
did not have the resources (developer spare time,
or funding to use working hours) to do.
This is one of them. The source code is there, if you want to implement it
yourself and donate the changes
back I can show you where they would have to be implemented. And the home
page has a link to commercial
support, with companies that would implement this for you, under the
provisioning of adequate funding for it.
Okay, may be my poor English give you the feeling that I was criticizing current GeoServer work but that was not my point at all. Definitively not. I just wanted to know if I missed something or not, there is not so much pages referenced around GeoServer and hstore topic.
Actually I have no time to contribute, but if the opportunity to implement this myself come, I will ask you back for more infos.
On Thu, Feb 6, 2014 at 5:24 PM, Jule M <jule.thales@…84…> wrote:
Hi,
I have recently imported some OSM data in my PostgreSQL/PostGIS database thanks to Osmosis tool and I’m disappointed to see that GeoServer cannot handle PostGIS hstore field natively.
So I’m asking if there is an alternative way to handle hstore key/value pairs in WFS or even in WMS with SLD other than manipulating the database in order to add columns for keys that I’m interested in? May be I have missed some Osmosis configuration parameters which allow importing some tags in separate fields?
Is there any performance issue with hstore requests which can indicate a deliberate choice of non-implementing such a feature? Otherwise are changes planned to handle hstore fields?
In seven years working in GeoServer I’ve hardly ever seen a deliberate choice not to implement something.
But I’ve seen countless things that we would have liked to add, and that we did not have the resources (developer spare time,
or funding to use working hours) to do.
This is one of them. The source code is there, if you want to implement it yourself and donate the changes
back I can show you where they would have to be implemented. And the home page has a link to commercial
support, with companies that would implement this for you, under the provisioning of adequate funding for it.
