On Tue, May 6, 2008 at 10:25 AM, SteveC [EMAIL PROTECTED] wrote:
is there anything else that should be put in 0.6? Probably a good idea
to talk about it now.
As project is getting older there are many relatively old GPS tracks in the db.
Older tracks are probably already mapped, or out of
Extrapolating your reasoning, we should end implementing the 12 entities
defined in OGC's Simple Features, and every piece of OSM software should
know
I'm proposing three primitive geometry datatypes, namely: point (syn. node),
polyline (syn. linestring, way) and area (syn. surface, polygon),
Brett Henderson wrote:
Being fairly intimate with the issues involved in trying to split files
into bboxes and polygons I'd love to see a polygon concept. Currently
it is almost impossible to split osm files into tiles suitable for
devices such as a garmin. I've created a pgsql schema
Sebastian Spaeth wrote:
Brett Henderson wrote:
Being fairly intimate with the issues involved in trying to split files
into bboxes and polygons I'd love to see a polygon concept. Currently
it is almost impossible to split osm files into tiles suitable for
devices such as a garmin.
On Wed, May 07, 2008 at 08:47:29AM +0200, Stefan Baebler wrote:
I propose to introduce the ability to limit the age of trackpoints
downloaded into the client by introducing an extra parameter age,
eg:
GET
/api/0.6/trackpoints?bbox=left,bottom,right,topage=ageInDayspage=pageNumber
+1!
is there anything else that should be put in 0.6? Probably a good idea
to talk about it now.
There is something I have in mind since a long time.
Whats about creating a tag_key, tag_value and tags table?
tag_key could be something like:
tag_key_id(int), tag_key(varchar)
tag_value could be
On Wed, May 7, 2008 at 10:10 AM, Raphael Studer [EMAIL PROTECTED] wrote:
is there anything else that should be put in 0.6? Probably a good idea
to talk about it now.
There is something I have in mind since a long time.
Whats about creating a tag_key, tag_value and tags table?
On Wed, May 7, 2008 at 10:44 AM, Brett Henderson [EMAIL PROTECTED] wrote:
Actually my problem was much simpler. I was just looking for a way of
taking a big bounding box (ie. a box around Australia) and splitting it
into smaller tiles (let's say 10km square for arguments sake). The
You also have to realise just how many tags there are.
On nodes and ways there are close to 1 billion tags, comprising of
about 50 million distinct key-value pairs (this was the last time I
counted which was a while back).
So while you'd save on space, the table join to get the tags
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Studer schrieb:
| The api change would be a good time to clean out most of the typos.
| with the node_tags, way_tags and relation_tags table (sorry i've completly
| forgotten these above), they are allready separated.
Hello Raphael,
how do
| The api change would be a good time to clean out most of the typos.
| with the node_tags, way_tags and relation_tags table (sorry i've completly
| forgotten these above), they are allready separated.
how do you suppose to do that?
map_features and proposed_tags are not all the valid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, you have a way to searcg for them and to download, correct and
upload them.
Why are you waiting for an API-change? You can start right now.
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with
Well, you have a way to searcg for them and to download, correct and
upload them.
Why are you waiting for an API-change? You can start right now.
The only reason not doing it atm is a lack of a tool doing this easy.
A change on the api as i proposed, would be a verry good reason
correcting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Stubbs schrieb:
On Wed, May 7, 2008 at 8:17 AM, bvh [EMAIL PROTECTED] wrote:
On Wed, May 07, 2008 at 08:47:29AM +0200, Stefan Baebler wrote:
I propose to introduce the ability to limit the age of trackpoints
downloaded into the client by
Cool, would you like to share your tool with us?
http://lists.openstreetmap.org/pipermail/dev/2008-January/008393.html
See this reply. :) read the thread :)
I guess the problem is the automatic.
If it's a human who's giving the definitiv ok for changing a tag, than it
could be widely
On Wed, 7 May 2008, Raphael Studer wrote:
Cool, would you like to share your tool with us?
http://lists.openstreetmap.org/pipermail/dev/2008-January/008393.html
See this reply. :) read the thread :)
I guess the problem is the automatic.
If it's a human who's giving the definitiv
On Wed, May 07, 2008 at 07:41:12PM +0530, Subhodip Biswas wrote:
hi !
My ISP is somehow blocking svn over http (i.e he is blocking webDAV)
. Since I can use svn using svn protocol ,can JOSM be allowed to
transfer over svn protocol apart from its http one .
I will be highly helped if this
Dirk-Lüder Kreie wrote:
I propose to introduce the ability to limit the age of trackpoints
downloaded into the client by introducing an extra parameter age,
eg:
GET
/api/0.6/trackpoints?bbox=left,bottom,right,topage=ageInDayspage=pageNumber
+1! Although it might be easier on
On Thu, May 8, 2008 at 1:01 AM, Andrew McCarthy [EMAIL PROTECTED] wrote:
On Wed, May 07, 2008 at 07:41:12PM +0530, Subhodip Biswas wrote:
hi !
My ISP is somehow blocking svn over http (i.e he is blocking webDAV)
. Since I can use svn using svn protocol ,can JOSM be allowed to
19 matches
Mail list logo
