On Thu, Oct 9, 2008 at 2:58 AM, Stefan de Konink [EMAIL PROTECTED] wrote:
Allowed via the 0.5 API currently: Yes.
Supported by any of the editors: No (AFAIK)
On a hunch, don't expect the 0.6 API to support duplicates.
Then disable *ANY* edits with this borked editor: Potlatch 0.10c and
On Thursday 09 October 2008 16:06:39 Andy Allan wrote:
(I think Grant said this bit, it's lost its context)
Allowed via the 0.5 API currently: Yes.
Supported by any of the editors: No (AFAIK)
I could swear I explicitly read endorsement of duplicate keys on the
documentation somewhere, but
Stefan de Konink wrote:
Then disable *ANY* edits with this borked editor: Potlatch 0.10c and
revert back to a version that did not produce duplicates.
Er, hate to rain on your parade, but if you'd actually have taken
0.1us to look, you'd see that Potlatch 0.10c has already been
Points noted Hugh but in reality it's probably easy enough to find
alternative solutions to these tagging questions. Since duplicate keys in
the current data have essentially been legacy data or input errors of some
sort I suspect the number that exist right now is quite low. That's why I
say it's
MilesTogoe wrote:
ruby and rails have gone thru some changes the past few months - you
most likely need a newer gems package - try downloading the latest
gems source and compiling that - then from the newer gems install the
rails packages
I currently have rubygems 1.2.0. I see the latest
Brett Henderson wrote:
I haven't had much luck either. Does anybody have any suggestions on
where I've gone wrong below.
I installed the following packages.
yum install ruby ruby-devel ruby-irb ruby-libs ruby-rdoc ruby-ri rubygems
ruby-sqlite3
yum install ruby-mysql ruby-postgres
Brett Henderson wrote:
I haven't had much luck either. Does anybody have any suggestions on
where I've gone wrong below.
I suspect my errors have something to do with some missing externals. I
better fix that before making any more noise and wasting anybody's time.
On Thu, Oct 09, 2008 at 04:34:37PM +1000, Hugh Barnes wrote:
Spurred on by this, I tried it in Merkaartor. The UI accepted my input and I
assumed all was good. I just remembered to follow this up and it appears the
data didn't make it. Possibly the last occurrence of the tag in the app was
Brett Henderson wrote:
I currently have rubygems 1.2.0. I see the latest is 1.3.0. I don't
know much about ruby. So should I upgrade to 1.3.0? I'd rather not
install from source unless I have to ...
The version of rubygems you have is largely irrelevant - that is just
the ruby package
On Thursday 09 October 2008 18:56:42 Andy Robinson (blackadder-lists) wrote:
Duplicate keys were perfectly valid
then and indeed I recall we discussed how we might use duplication for
tagging purposes. It was only the lack of support in the editors that
stopped duplication in its tracks.
OK,
On 9 Oct 2008, at 13:53, Brett Henderson wrote:
MilesTogoe wrote:
ruby and rails have gone thru some changes the past few months - you
most likely need a newer gems package - try downloading the latest
gems source and compiling that - then from the newer gems install the
rails packages
I
On 9 Oct 2008, at 13:18, Tom Hughes wrote:
Brett Henderson wrote:
[...]
Do what it says and install 2.0.2 as 2.1.x does not work with our code
at the moment.
Tom,
Would it be safe to assume that for api 0.6 we can move to rails 2.1.1?
If so, I'll work on any problems that might arise
Shaun McDonald wrote:
Would it be safe to assume that for api 0.6 we can move to rails 2.1.1?
Well not until somebody has investigated the problems and found out what
needs to be done to make it work. It's been a while since I worked on it
so I can't remember now what the problems were.
If
On 9 Oct 2008, at 14:24, Shaun McDonald wrote:
[...]
I've fixed the externals issue I had. That was dumb on my part. I
checked out a few hours ago and forgot it failed due to external
sites
being down. I've used TomH's vendor.zip to get the external files.
The api06 branch will
Shaun McDonald wrote:
The api06 branch will check out fine :-)
Especially now that I have added the classic_pagination plugin to svn
directly, rather than having it access an out of date external. I should
probably back port this change ASAP.
http://trac.openstreetmap.org/changeset/11079
especially for you, google invented 'mail goggles':
http://gmailblog.blogspot.com/2008/10/new-in-labs-stop-sending-mail-you-later.html
no seriously: stefan is a nice guy and he made a valid point here.
i am also really amazed this is possible. but imo we should blame the api,
not potlatch.
On Thu, Oct 9, 2008 at 2:31 PM, Stefan de Konink [EMAIL PROTECTED] wrote:
If 0.6 is not supporting it, it should not be possible to enter the data
today. (imho)
lets do a 0.5.5 release with this fix in. hmm, we should include
referential integrity as well, since that can cause similar types of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Matt Amos schreef:
we're working on it and it'll be ready as soon as its ready. if you'd
like to help then that would be fantastic.
If you don't mind I'll implement a 0.6 api in my own server ;)
imho, the most likely place to look for the error
Brett Henderson wrote:
Hi Sagar,
I hope to get time to test this at home tonight but hopefully others
have better answers in the meantime.
These links might also help in the meantime:
http://wiki.openstreetmap.org/index.php/The_Rails_Port
Way way back in the long distant past of the project SteveC arranged for
key/value pairs to be used for adding information about objects (Nodes,
Segments and the unused Areas at the time) but in doing so did not set any
restrictions on their use whatsoever. In fact all tags were concatenated
On Thursday 09 October 2008 19:02:44 Andy Robinson (blackadder-lists) wrote:
Points noted Hugh but in reality it's probably easy enough to find
alternative solutions to these tagging questions.
+1
Since duplicate keys in
the current data have essentially been legacy data or input errors of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Stefan de Konink schreef:
you'll notice that JMEditor, whatever that is, is responsible for
the node errors. and all the way errors are duplicates, so there is
never a conflict in reducing them. if you'd like to fix these then
that would be
Hi,
I'm trying to implement some projection-code for a project of mine..
But I have some trouble with the Mercator projection.
I understood that the projection we use in the slippy map is called
Sphere / Web-Mercator, or EPSG:900913 or EPSG:3785 and is also used by
Google, MS, Yahoo and so on..
Hi Dominic,
If you are into reading, here's some code that nicely commented:
http://trac.osgeo.org/gdal/browser/sandbox/klokan/globalmaptiles.py
Cheers,
Dane
On Oct 9, 2008, at 8:38 AM, Dominik Spies wrote:
Hi,
I'm trying to implement some projection-code for a project of mine..
But I
On Wed, Oct 08, 2008 at 08:51:42AM +0200, Giovanni Mascellani wrote:
The Italian OpenStreetMap community is working on translation JOSM to
Italian. The job is still in progress, but a first result is available
at [1] (about 700 strings translated). Could it be integrated into the
SVN?
Hi!
I
Ian Dees [EMAIL PROTECTED] writes:
On Wed, Oct 8, 2008 at 9:35 PM, Stefan de Konink [EMAIL PROTECTED] wrote:
No way! The database[1] uses indexing under the hood automatically. So
every created_by k or JOSM v is automatically indexed. This gives a
significant space reduction plus fast
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Matthias Julius schreef:
Or make it a normal index instead of a primary key. Then you can have
duplicates.
The database I am using does this under the hood already. The constraint
I have implemented was because:
- - I have an update algorithm
Hugh Barnes [EMAIL PROTECTED] writes:
I'd be curious to see if anyone else sees a need. I find delimited strings
inherently unsatisfactory to work with, so I also wonder if there are any
other workarounds that we could at least recommend?
Multiple values for a tag is certainly useful and
Hugh Barnes [mailto:[EMAIL PROTECTED] wrote:
Sent: 09 October 2008 1:08 PM
To: dev@openstreetmap.org
Cc: Andy Robinson (blackadder-lists)
Subject: Re: [OSM-dev] way 7062297, is this new?
On Thursday 09 October 2008 18:56:42 Andy Robinson (blackadder-lists)
wrote:
Duplicate keys were perfectly
Andy Robinson (blackadder-lists) wrote:
But then
again since it's been pointed out that only 35 current cases exist and I
exist_ed_
I have it on good authority that all those cases have been eradicated by
now.
--
Lennard
___
dev mailing list
On 9 Oct 2008, at 22:20, Ldp wrote:
Andy Robinson (blackadder-lists) wrote:
But then
again since it's been pointed out that only 35 current cases exist
and I
exist_ed_
I have it on good authority that all those cases have been
eradicated by
now.
However they will still be in the
Thanks for all the help. I now have a working rake installation and a
database at version 15.
I've installed the following gems.
gem install -v=2.0.2 rails
gem install libxml-ruby (produced a number of what appeared to be
errors, hopefully not an issue)
gem install -v=0.9.93
After a longer pause, I'd like to move on with -ng and implement server I/O.
Is there a public testing server or do I have to deploy one locally to test
the implementation (and e.g. 0.6 API)?
I don't like to test against live server and while I do plan writing a mock
server
for unit testing, I
See also http://wiki.openstreetmap.org/index.php/Slippy_map_tilenames
2008/10/9 Dominik Spies [EMAIL PROTECTED]:
Hi,
I'm trying to implement some projection-code for a project of mine..
But I have some trouble with the Mercator projection.
I understood that the projection we use in the
34 matches
Mail list logo
