Re: [OSM-dev] Data corruption :) II
Stefan de Konink wrote: Then let me even get a better proposal; A second machines will be installed that has enforced foreign keys. This second machine will produce the planet. And will directly trigger events upon corruption so the main API doesn't need to cope with them until 0.6. So you want us to do a huge amount of engineering work, including sourcing new hardware, just to make things easier for you. Bearing in mind that this will itself delay 0.6 because it will divert effort, and that it will also be hugely duplicative of the 0.6 work. Are you completely mad? Tom -- Tom Hughes ([EMAIL PROTECTED]) http://www.compton.nu/ ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
Hi, Stefan de Konink wrote: No, technically I am King because I am a customer of your data, that is broken. Any proposal to fix it in a reasonable time, hence less than 1 month is accepted. Don't know if I have a wicked sense of humour but I am starting to find this funny. Bye Frederik -- Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09 E008°23'33 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
2008/11/26 Stefan de Konink [EMAIL PROTECTED]: On Wed, 26 Nov 2008, Tom Hughes wrote: Then let me even get a better proposal; A second machines will be installed that has enforced foreign keys. This second machine will produce the planet. And will directly trigger events upon corruption so the main API doesn't need to cope with them until 0.6. So you want us to do a huge amount of engineering work, including sourcing new hardware, just to make things easier for you. Bearing in mind that this will itself delay 0.6 because it will divert effort, and that it will also be hugely duplicative of the 0.6 work. Yup :) And for all other users of your core business. Delivering consistent Geo data. Are you completely mad? No, technically I am King because I am a customer of your data, that is broken. Any proposal to fix it in a reasonable time, hence less than 1 month is accepted. Many corporate boys always go to battle with the stupid argument you just made. Dave ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
On Wed, Nov 26, 2008 at 12:27 PM, Dave Stubbs [EMAIL PROTECTED] wrote: 2008/11/26 Matt Amos [EMAIL PROTECTED]: what would be ideal is a check like node_id references way_nodes.node_id check way_nodes.visible = 1, but i can't find any documentation for this in mysql or postgres. one solution is to delete deleted ways/nodes from current_, but this would complicate the code to determine whether the appropriate response from the API is 403 or 404. Well, as long as the API code is good, and makes this check, then the transaction should cover it for inserts/updates. I'd assume the migration script will have to handle existing inconsistencies. that is exactly why i'm worrying about it :-) Otherwise you could make this check in postgres using the CHECK expression table/column constraint. And possibly some stored procedures. But we're then writing very close to the database layer. And not even our current database layer, as I don't know if mysql supports this. i don't think postgres supports a check constraint on a column in a different table linked by foreign key. at least, if it does they're keeping quiet about it... i agree that we don't want to be writing database-specific stored procedures, but i think its worth exposing as many constraints as we can to the database... The rails way would presumably be to write a validates method, which would work within the transaction, and keep it clean at the application insert/update level. indeed. i've just had a look and some of this stuff isn't inside transactions, but that can easily be fixed. cheers, matt ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] 0.5 API: /api/0.5/user/preferences, values truncated to 256 chars
On Tue, Nov 25, 2008 at 10:23 PM, Frederik Ramm [EMAIL PROTECTED] wrote: Hi, Stefan de Konink wrote: Then it might be better to never use any argument as 'wait till 0.6' because it could take till March... May I remind everyone that my initial estimate for 0.6 was Mid-May ;-) Open Source, volunteers everywhere with varying amounts of time - always best to avoid specifying the year :-) Which is also the point with setting a deadline. I don't believe that the existance of a date, whether that's next wednesday, christmas or january 31st, would have any impact on the actual work being done in a small volunteer community. We can estimate when it'll be ready, and more help will help things happen quicker, but apart from that a deadline would just make a nice whooshing sound as it went by. Cheers, Andy I love deadlines. I like the whooshing sound they make as they go by. http://en.wikiquote.org/wiki/Douglas_Adams#Time ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
Otherwise you could make this check in postgres using the CHECK expression table/column constraint. And possibly some stored procedures. But we're then writing very close to the database layer. And not even our current database layer, as I don't know if mysql supports this. i don't think postgres supports a check constraint on a column in a different table linked by foreign key. at least, if it does they're keeping quiet about it... Yes, it doesn't support subqueries in the check expression direcly, however it does support function calls, which is where the stored procedures come in. So it's possible to do it, but whether it's either efficient or desirable is another matter :-). ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
Frederik Ramm wrote: So as far as I am concerned, out with the invisible objects in the current tables (saves us another column as well). But that would probably be a big change that would require a lot of re-testing... maybe wait until 0.7 ;-) I'm laughing about your comments too, so I guess we have the same kind of humor :D Stefan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
Hi, Stefan de Konink wrote: Frederik Ramm wrote: So as far as I am concerned, out with the invisible objects in the current tables (saves us another column as well). But that would probably be a big change that would require a lot of re-testing... maybe wait until 0.7 ;-) I'm laughing about your comments too, so I guess we have the same kind of humor :D No, no, if it were the same kind of humour then my comment would have to read You're right, I'm sure TomH will fix this up tonight, or at least within an acceptable timeframe (i.e. anything within the next 48 hours), and if he's too lazy to do this then he should just get some of the company boys to help him. You're laughing about my realism, I'm laughing about your, er, rather visionary point of view. But take it easy; every society has its visionaries to whom nobody listens. We'll all be sorry later but until then let's just get on with what we're doing. Bye Frederik -- Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09 E008°23'33 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
Hi, Matt Amos wrote: one solution is to delete deleted ways/nodes from current_, but this would complicate the code to determine whether the appropriate response from the API is 403 or 404. I have never used that distinction for anything. It is implicit in the object id anyway - any node that is less than the maximum id has existed at some point in time because we have auto increments ;-) and any node with a higher id that the maximum has never existed. So as far as I am concerned, out with the invisible objects in the current tables (saves us another column as well). But that would probably be a big change that would require a lot of re-testing... maybe wait until 0.7 ;-) Bye Frederik -- Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09 E008°23'33 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
On Wed, 26 Nov 2008, Tom Hughes wrote: Then let me even get a better proposal; A second machines will be installed that has enforced foreign keys. This second machine will produce the planet. And will directly trigger events upon corruption so the main API doesn't need to cope with them until 0.6. So you want us to do a huge amount of engineering work, including sourcing new hardware, just to make things easier for you. Bearing in mind that this will itself delay 0.6 because it will divert effort, and that it will also be hugely duplicative of the 0.6 work. Yup :) And for all other users of your core business. Delivering consistent Geo data. Are you completely mad? No, technically I am King because I am a customer of your data, that is broken. Any proposal to fix it in a reasonable time, hence less than 1 month is accepted. Stefan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
2008/11/26 Matt Amos [EMAIL PROTECTED]: On Wed, Nov 26, 2008 at 7:54 AM, Stefan de Konink [EMAIL PROTECTED] wrote: Then let me even get a better proposal; A second machines will be installed that has enforced foreign keys. This second machine will produce the planet. And will directly trigger events upon corruption so the main API doesn't need to cope with them until 0.6. it is worth noting that foreign keys and transactions alone will drastically reduce the number of problems, but may not solve them entirely. the foreign key from current_way_nodes to current_ways and current_nodes only ensures that those nodes have existed. the current_* table stores (as the name suggests) the current state of entities. that state may be deleted. what would be ideal is a check like node_id references way_nodes.node_id check way_nodes.visible = 1, but i can't find any documentation for this in mysql or postgres. one solution is to delete deleted ways/nodes from current_, but this would complicate the code to determine whether the appropriate response from the API is 403 or 404. thoughts, suggestions? Well, as long as the API code is good, and makes this check, then the transaction should cover it for inserts/updates. I'd assume the migration script will have to handle existing inconsistencies. Otherwise you could make this check in postgres using the CHECK expression table/column constraint. And possibly some stored procedures. But we're then writing very close to the database layer. And not even our current database layer, as I don't know if mysql supports this. The rails way would presumably be to write a validates method, which would work within the transaction, and keep it clean at the application insert/update level. Dave ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Visualising change (.osc) files
On Tue, Nov 25, 2008 at 9:50 PM, Brett Henderson [EMAIL PROTECTED] wrote: PS. I really should document the 0.6 pgsql schema on the wiki at some point. If we can come up with some names to distinguish between * pgsql schema from osmosis * pgsql schema from osm2pgsql * pgsql schema from rails_port(*) then that'll maybe save confusion down the line. If not names then just clear references as to which one is which. Cheers, Andy (*) New with API 0.6!! Option to run with PostgreSQL backend!! Almost entirely untested!! ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
Hi, Stefan de Konink wrote: Then let me even get a better proposal; A second machines will be installed that has enforced foreign keys. Another proposal from cloud-cuckoo-land. Enforced foreign keys means a full switch to InnoDB tables (or another RDMS altogether), something we're planning for 0.6 but sure as hell don't have the manpower to do along the side. Same for the second machine. Tell you what - you simply do something else for a few months and everything will be cool when you return. No need to get all upset about the current state of affairs and devise workarounds that will cost *everybody* their precious time when the solution is just around the corner. Bye Frederik -- Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09 E008°23'33 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [josm-dev] white stripes in latest YAHOO (webkit)
I've downloaded latest ewms-plugin within JOSM and unpacked the webkit-binary to C:\windows\ (it's bad, I know). xeen schrieb: How did you get it to run anyway? (i.e. which command line do you use in the settings?) Thanks! xeen On Wed, Nov 26, 2008 at 15:04, Tobias Wendorff [EMAIL PROTECTED] wrote: Hi there, I've just tried out latest ewmsplugin with YAHOO (webkit on Windows). In Dortmund (51.52, 7.46) I'm getting white stripes between the images. Also, the images are very distorted. I'm using Mercator-projection, like Yahoo does. Is there already a bugfix or are you working on it? Best regards, Tobias ___ josm-dev mailing list [EMAIL PROTECTED] http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list [EMAIL PROTECTED] http://lists.openstreetmap.org/listinfo/josm-dev
[OSM-dev] Correct place to submit patches?
Hi all, I'm new to this mailing list and to OSM in general so would like to introduce myself first. I am Bradley Kite, and have an interest in getting Mapnik/OSM running on the Android mobile platform: http://code.google.com/p/osmdroid/ Currently, the software downloads map tiles on demand (and caches them locally), but I have been working on having a map-tile renderer work on the phone itself, from a database on the phone's SD card (so that map-tiles can be provided in the absence of phone signal). To this aim, I have mostly ported mapnik to Java (its not complete yet, but not far from it) (http://code.google.com/p/osmdroid/source/browse/#svn/branches/osm-contributor) and have patched osm2pgsql so that it can output to an sqlite database instead of postgres (sqlite libraries etc. come with the phone's software stack). I'd like to submit this patch back so that it could be included in future versions of osm2pgqsl - so that others can build sqlite databases of their local countries that can work on the phone. Please advise on the correct procedure. Regards -- Brad. ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
On 24 Nov 2008, at 04:31, Tom Hughes wrote: What is the down time you expect for 0.6 migration? We are still attempting to quantify that. Awesome :-) Best Steve ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Correct place to submit patches?
On Wed, Nov 26, 2008 at 5:22 PM, Bradley Kite [EMAIL PROTECTED] wrote: Hi all, I'm new to this mailing list and to OSM in general so would like to introduce myself first. I am Bradley Kite, and have an interest in getting Mapnik/OSM running on the Android mobile platform: http://code.google.com/p/osmdroid/ Currently, the software downloads map tiles on demand (and caches them locally), but I have been working on having a map-tile renderer work on the phone itself, from a database on the phone's SD card (so that map-tiles can be provided in the absence of phone signal). To this aim, I have mostly ported mapnik to Java (its not complete yet, but not far from it) (http://code.google.com/p/osmdroid/source/browse/#svn/branches/osm-contributor) and have patched osm2pgsql so that it can output to an sqlite database instead of postgres (sqlite libraries etc. come with the phone's software stack). I'd like to submit this patch back so that it could be included in future versions of osm2pgqsl - so that others can build sqlite databases of their local countries that can work on the phone. Posting patches to the list is fine, albeit uncommon in OSM. Adding patches to a suitable trac ticket ( http://trac.openstreetmap.org ) is probably better, or if you've got bigger plans just ask for an SVN account (ask on IRC) and do the work directly. We're pretty liberal about svn access and people helping out. Cheers, Andy ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] 'holes' in buildings
I'm running my own mapnik server and have noticed a strange problem with the rendering. I don't seem to be getting the holes in buildings You need to use osm2pgsql slim mode (-s), apparently relation parsing is broken in the in-memory mode, since it can't decide which ways are valuable enough to keep before parsing the relation. (Or something similar) Running the current SVN version of osm2pgsql in slim mode does fixed the problem. Many thanks! -- Brian ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] API 0.6 Test Server
Hi all, I have set up a copy of the 0.6 API at http://api06.dev.openstreetmap.org/ as a testing server. The previous version that was originally at this address was quite neglected as the original maintainer had moved onto other projects. It currently contains a planet extract of the London area. I hope to keep it tracking svn closely. Many thanks to Shaun McDonald, Chris Schmidt and Brett Henderson for their help so far. -- Regards, Thomas Wood (Edgemaster) ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
On Wed, Nov 26, 2008 at 02:26:27PM +0100, Frederik Ramm wrote: I have never used that distinction for anything. It is implicit in the object id anyway - any node that is less than the maximum id has existed at some point in time because we have auto increments ;-) and any node with a higher id that the maximum has never existed. That a sequence is actually contiguous is a big assumption and probably dependent on the DBMS. What the current spec says is a different matter (I don’t know, SQL92 certainly doesn’t define sequences). Simon -- A complex system that works is invariably found to have evolved from a simple system that works.—John Gall signature.asc Description: Digital signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Data corruption :) II
Simon Ward wrote: On Wed, Nov 26, 2008 at 02:26:27PM +0100, Frederik Ramm wrote: I have never used that distinction for anything. It is implicit in the object id anyway - any node that is less than the maximum id has existed at some point in time because we have auto increments ;-) and any node with a higher id that the maximum has never existed. That a sequence is actually contiguous is a big assumption and probably dependent on the DBMS. What the current spec says is a different matter (I don’t know, SQL92 certainly doesn’t define sequences). Yep, dependent on DB. Oracle for example will almost certainly not be sequential. Rollbacks after id allocation will usually result in gaps. But I'm curious why you would ever need to know if an id has existed? I don't understand why deleted items are stored in the current tables. From an osmosis perspective I've never had a need to know this type of thing. Full information will always be in the history table anyway and an attempt to use an id that has been used in the past will result in a primary key violation due to version 1 already existing. Perhaps this is not how rails works ... ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[josm-dev] white stripes in latest YAHOO (webkit)
Hi there, I've just tried out latest ewmsplugin with YAHOO (webkit on Windows). In Dortmund (51.52, 7.46) I'm getting white stripes between the images. Also, the images are very distorted. I'm using Mercator-projection, like Yahoo does. Is there already a bugfix or are you working on it? Best regards, Tobias ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] ewmsplugin on win32
On Sat, 22 Nov 2008, Robin Rattay wrote: Please update plugin and redownload the webkit-image stuff and retry. I've been trying to use the plugin the last few days now, too. However webkit-image doesn't work for me on Win XP. I've try this new version and the previous version. Testing on the command line with webkit-image.exe http://www.google.de; and webkit-image.exe http://www.google.de test.png doesn't return anything - neither an image nor an error message. The latter just gives me a 0 byte file. How did you install it? You need to copy all files (including subdirectories) to the path where the executable is. And probably you need to instruct your firewall to allow network access for the tool as well. BTW: webkit-image now outputs JPG, not PNG. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] white stripes in latest YAHOO (webkit)
Hi Dirk works like a charm! Thanks a lot! -- Karl -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Dirk Stöcker Gesendet: Mittwoch, 26. November 2008 16:45 An: josm-dev@openstreetmap.org Betreff: Re: [josm-dev] white stripes in latest YAHOO (webkit) On Wed, 26 Nov 2008, Tobias Wendorff wrote: I've just tried out latest ewmsplugin with YAHOO (webkit on Windows). In Dortmund (51.52, 7.46) I'm getting white stripes between the images. Also, the images are very distorted. I'm using Mercator-projection, like Yahoo does. Is there already a bugfix or are you working on it? Redownload the binary (Should have date 26.11.2008 for all files inside). That should fix the issue as I now found a proper way to handle resizing. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] white stripes in latest YAHOO (webkit)
On Wed, 26 Nov 2008, Karl Guggisberg wrote: works like a charm! Thanks a lot! With one exception - In nothern or southern regions you get scrollbars inside the picture when the picture height/width is greater than your screen width. If someone finds a way to trick Qt into assuming it has a larger screen please tell me. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] [PATCH] Hide splashscreen when other windows is shown
Hi, attached patch automatically hides splashscreen when some window is shown (ie missing plugin, broken config, ..). Without the patch splash screen blocks the other window making josm unable to start. -- Jiri splash.patch Description: Binary data ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] ewmsplugin on win32
Hi, I also tried the ewmsplugin with WinXP. However webkit-image doesn't work for me on Win XP. I've try this new version and the previous version I can use this commandline: webkit-image http://www.google.com/ test.jpg That gives an image 2000x2000 as configured in webkit-image.cpp containig the rendered web content in an area with my screen resolution (placed top left). Rest of screen is black. The image shows some sort of dithering/compression artefacts. calling webkit-image with this URL returns a zero sized image. file://C:/Documents%20and%20Settings/Stephan/Application%20Data/JOSM/plugins/wmsplugin/ymap.html?request=getmapformat=image/jpegbbox=101.1576781,5.7804388,104.0478975,8.6706581width=500height=500 Opening the URL in Firefox loads a map. I suppose this is a problem with webkit-image. Someone working on this? Stephan ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] [PATCH] Hide splashscreen when other windows is shown
Hi, Jiri Klement wrote: attached patch automatically hides splashscreen when some window is shown (ie missing plugin, broken config, ..). Without the patch splash screen blocks the other window making josm unable to start. Patch applied for r1093. Bye Frederik -- Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] ewmsplugin on win32
Stephan wrote: calling webkit-image with this URL returns a zero sized image. file://C:/Documents%20and%20Settings/Stephan/Application%20Data/JOSM/plugins/wmsplugin/ymap.html?request=getmapformat=image/jpegbbox=101.1576781,5.7804388,104.0478975,8.6706581width=500height=500 Opening the URL in Firefox loads a map. I suppose this is a problem with webkit-image. Someone working on this? Besides this problem: I tried debugging the plugin with eclipse. Now webkit returned data. Aerial images visible in JOSM. Very strange. It uses different coordinates now. Something wrong with the mentioned URL? Stephan ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] ewmsplugin on win32
On Thu, 27 Nov 2008, Stephan wrote: calling webkit-image with this URL returns a zero sized image. file://C:/Documents%20and%20Settings/Stephan/Application%20Data/JOSM/plugins/wmsplugin/ymap.html?request=getmapformat=image/jpegbbox=101.1576781,5.7804388,104.0478975,8.6706581width=500height=500 Opening the URL in Firefox loads a map. I suppose this is a problem with webkit-image. Someone working on this? Besides this problem: I tried debugging the plugin with eclipse. Now webkit returned data. Aerial images visible in JOSM. Very strange. It uses different coordinates now. Something wrong with the mentioned URL? Your above URL suggest an old version of the ymap.html and (e)wmsplugin. A new URL does not have request=getmapformat=image/jpeg. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
