Hi,
David Carmean wrote:
> Not a wizard, but "tenacious" (or OCD, take your pick). It's beginning to
> seem like PostGIS has the tools to accomplish what I need.
> Have already managed to have it find closed ways and create polygon
> geometries
> for them. I'll update y'all on my progress whe
On Mon, Dec 21, 2009 at 8:40 PM, Anthony wrote:
> On Mon, Dec 21, 2009 at 4:13 PM, Marcus Wolschon wrote:
>
>> What exactly do you mean with converting closed ways into polygons?
>> Closed ways ARE already polygons.
>>
>
> A closed way tagged barrier=fence is a polygon?
>
Or, for a more clear ex
On Tue, Dec 22, 2009 at 12:42:49AM +0100, Frederik Ramm wrote:
[snip]
> This is probably going to be easier than trying to build proper
> multipolygons from data imported by osmosis, unless you are a real SQL
> wizard.
Not a wizard, but "tenacious" (or OCD, take your pick). It's beginning to
> Aye. Part of my problem is that I haven't been able to build osm2pgsql
> under Cygwin/Vista64, and thus can't add the above patch. Vista64 is the
> only environment I currently possess to run this under; hopefully within
> a few weeks I can build a Linux server with adequate storage and CPU.
Ma
On Mon, Dec 21, 2009 at 4:13 PM, Marcus Wolschon wrote:
> What exactly do you mean with converting closed ways into polygons?
> Closed ways ARE already polygons.
>
A closed way tagged barrier=fence is a polygon?
___
osmosis-dev mailing list
osmosis-dev@
On Tue, Dec 22, 2009 at 12:42:49AM +0100, Frederik Ramm wrote:
> Hi,
>
> Lennard wrote:
> > David Carmean wrote:
> >
> >> I found that osm2pgsql omitted several attributes that I require. Also,
> >> the
> >> schema created by osmosis is more suitable to my needs.
> >
> > If these attributes
Hi,
David Carmean wrote:
> If nothing else it appears that I could write a query using PostGIS functions
> that will do what I want:
>
> http://postgis.refractions.net/documentation/manual-1.3/ch06.html#IsClosed
Be advised that multipolygons may consist of any number of outer and
inner way
Hi,
Lennard wrote:
> David Carmean wrote:
>
>> I found that osm2pgsql omitted several attributes that I require. Also, the
>> schema created by osmosis is more suitable to my needs.
>
> If these attributes are the user, uid, version and timestamp, check out
> http://trac.openstreetmap.org/c
David Carmean wrote:
> I found that osm2pgsql omitted several attributes that I require. Also, the
> schema created by osmosis is more suitable to my needs.
If these attributes are the user, uid, version and timestamp, check out
http://trac.openstreetmap.org/changeset/19144
--
Lennard
___
On Mon, Dec 21, 2009 at 10:25:52PM +0100, Frederik Ramm wrote:
> Are you aware of osm2pgsql, a tool which has nothing to do with Osmosis
> but does roughly what you want?
I found that osm2pgsql omitted several attributes that I require. Also, the
schema created by osmosis is more suitable to m
When I import a .osm file into PostGIS, using osmosis (dumping to a
COPY file), all I get are POINT and LINESTRING WKB geometry columns,
but no POLYGON WKB columns . The linstrings from what OSM knows as
Closed Ways do have the first and last points with identical coordinates,
but since they are
Hi,
David Carmean wrote:
> I'm attempting to use OSM data, as imported to PostGIS via Osmosis, as
> layers in a project in some GIS software; I've had some success crafting
> queries to pull highways into a separate table, and am now working on
> hydrologic features. My current roadblock is: h
What exactly do you mean with converting closed ways into polygons?
Closed ways ARE already polygons. What more is there to convert?
Marcus
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/osmosis-dev
I'm attempting to use OSM data, as imported to PostGIS via Osmosis, as
layers in a project in some GIS software; I've had some success crafting
queries to pull highways into a separate table, and am now working on
hydrologic features. My current roadblock is: how/where can I convert
closed OS
14 matches
Mail list logo
