Branch: refs/heads/master
Home: https://github.com/joto/taginfo
Commit: d83a79f970d6d6f4f857c78e8041021780fa4141
https://github.com/joto/taginfo/commit/d83a79f970d6d6f4f857c78e8041021780fa4141
Author: Jochen Topf joc...@topf.org
Date: 2013-02-10 (Sun, 10 Feb 2013)
Changed
Hi Stefan,
So you mean given a tile location like this
http://c.tile.openstreetmap.org/16/34372/22990.png
return a vector tile set of GeoJSON features?
Yes, that is the plan.
What makes me wondering is this: When entering
http://owl.osm.org/api/0.1/changesets/16/34372/22990.geojson
Hello Stefan
I mentioned client side generation of GeoJSON from OSM data as an
alternative to a central GeoJSON API approach (which API is not
available yet; see below).
As always, it depends on the actual use case. When your application has
its own geo database already, it's probably
Hi Martin
2013/2/10 Martin Raifer tyr@gmail.com:
Btw: I think you are mistaken when it comes to Overpass API: it does *not*
return GeoJSON or any GeoJSON like geometry (LineStrings, etc.) [1]. Where
did you see ways as LineStrings as a response from Overpass?
That's what I conclude from
To Martin:
I see now, that GeoJSON is calculated at client-side in Overpass Turbo.
To Pavel:
Nice work. But I'm still not sure if OWL API is a solution to the question here:
The doc says Returns a list of changesets that affect given tile.
But what we are after here is a set of regular GeoJSON
Hello Stefan,
That's what I conclude from [1] i.e. osm-script output=json ...
/osm-script
The format option JSON meets the format described here:
http://wiki.openstreetmap.org/wiki/Xappy.js
This has exactly the same semantics like OSM XML and only different syntax.
However, JSON makes some
Hi Roland
2013/2/10 Roland Olbricht roland.olbri...@gmx.de:
...
What makes me hesitate about GeoJSON is essentially that there is no clear
rule whether an elements becomes a linestring or a polygon. Solving this will
require both a test for validness (e.g. self intersections, but also some
I think many people in the community would be in favor of an area element.
But Show us the code, in particular, how would a transition work?
- Serge
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
On 02/09/2013 04:13 PM, Lynn W. Deffenbaugh (Mr) wrote:
I'm running Osmosis Version 0.34 to pull and apply minutely updates to
my database for use by mod_tile/renderd. These updates began failing
today with the following information:
sudo apt-get install osmosis
Any hints on the command to
On Sun, 2013-02-10 at 17:28 +0100, yvecai wrote:
I've just updated osm2pgsql from source (osm2pgsql SVN version 0.81.0
(64bit id space))
I don't have no negative ids in my DB anymore ???
I'm primarily interested in 'route' relations:
select count(*) from planet_osm_line where route
Oh sure! I completely forgot I once had this exact same issue too !
Thanks for the reminder :-)
On 02/10/2013 06:21 PM, Jon Burgess wrote:
On Sun, 2013-02-10 at 17:28 +0100, yvecai wrote:
I've just updated osm2pgsql from source (osm2pgsql SVN version 0.81.0
(64bit id space))
I don't have no
On 02/10/2013 12:13 PM, Stefan Keller wrote:
To Pavel:
Nice work. But I'm still not sure if OWL API is a solution to the question here:
The doc says Returns a list of changesets that affect given tile.
But what we are after here is a set of regular GeoJSON objects (point,
linestring, polygon).
Serge Wroclawski schrieb am 10.02.2013 17:03:
I think many people in the community would be in favor of an area element.
But Show us the code, in particular, how would a transition work?
please read
http://blog.jochentopf.com/2012-11-26-an-area-datatype-for-osm.html
It has an paragraph named
On Sun, Feb 10, 2013 at 11:03:43AM -0500, Serge Wroclawski wrote:
I think many people in the community would be in favor of an area element.
But Show us the code, in particular, how would a transition work?
Actually the transition is the easy part. Just add support for new area data
type to
On Sun, Feb 10, 2013 at 09:31:16AM -0700, Kai Krueger wrote:
On 02/09/2013 04:13 PM, Lynn W. Deffenbaugh (Mr) wrote:
I'm running Osmosis Version 0.34 to pull and apply minutely
updates to my database for use by mod_tile/renderd. These updates
began failing today with the following information:
Le dimanche 10 février 2013 21:31:28, Jochen Topf a écrit :
Actually the transition is the easy part.
I am uneasy with your use of the work easy ! What will be the harder part !
Just add support in every editors, most data consumer tools and export/api
side, update the api so you don't
Am 10.02.2013 21:57, schrieb sly (sylvain letuffe):
Le dimanche 10 février 2013 21:31:28, Jochen Topf a écrit :
Actually the transition is the easy part.
I am uneasy with your use of the work easy ! What will be the harder part !
Just add support in every editors, most data consumer tools
On 11 February 2013 07:33, Jochen Topf joc...@remote.org wrote:
On Sun, Feb 10, 2013 at 09:31:16AM -0700, Kai Krueger wrote:
On 02/09/2013 04:13 PM, Lynn W. Deffenbaugh (Mr) wrote:
I'm running Osmosis Version 0.34 to pull and apply minutely
updates to my database for use by
Ho Pawel
2013/2/10 Paweł Paprota ppa...@fastmail.fm:
...
In OWL geometry is clipped to tile boundary using the standard
ST_Intersection operation. (...)
So, if an area (say this [ ]) is covered by two tiles it get's clipped:
Is it (1) shown as this [][] (e.g. as two areas)?
Or are (2) the
19 matches
Mail list logo
