[josm-dev] Lakewalker PlugIn no images
Hi everybody As reported in https://josm.openstreetmap.de/ticket/6152 Lakewalker-PlugIn is unable to download landsat images anymore. It seems that NASA has changed the WMS-Server settings or disabled the service. I tryed to patch LakewalkerWMS.java but couldn't find out what the new URL should look like... Regarding the other tickets for Lakewalker-Plugin it looks like Lakewalker isn't maintained anymore. ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Lakewalker PlugIn no images
Hi, some time ago, I experimented the same problem, but changin the internet conection ( using another network ) the problem was fixed. On Tue, Apr 12, 2011 at 1:57 PM, Peter Herison pheri...@web.de wrote: Hi everybody As reported in https://josm.openstreetmap.de/ticket/6152 Lakewalker-PlugIn is unable to download landsat images anymore. It seems that NASA has changed the WMS-Server settings or disabled the service. I tryed to patch LakewalkerWMS.java but couldn't find out what the new URL should look like... Regarding the other tickets for Lakewalker-Plugin it looks like Lakewalker isn't maintained anymore. ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev -- Danilo Lacoste Ingeniero Civil en informática Moonix Ltda www.moonix.cl ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Lakewalker PlugIn no images
Can anybody confirm, that Lakewalker is working? How does your URL look like? Lakewalker is working; it's just NASA stopped providing their WMS service - there's only tiled access method to Landast now. Anyway, Lakewalker's method of tracing imagery is ugly (no multipolygon support, quite usually it goes to endless loops..) and works only for grayscale WMSes. Please try using something more mature like http://wiki.openstreetmap.org/wiki/Scanaerial instead. -- Darafei Komяpa Praliaskouski OSM BY Team xmpp:m...@komzpa.net mailto:m...@komzpa.net ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] License Change Phase III
looks like we will also need to improve on josm to manage multiple connections to different osm servers and its merging ability. On Tue, Apr 12, 2011 at 9:42 PM, Frederik Ramm frede...@remote.org wrote: Hi, when the API is switched to license change phase 3, any attempt to open a changeset by someone who hasn't yet either agreed to, or rejected, the contributor terms will be met with a 403 Forbidden error code. Will JOSM display the content of that error message to the user (so that the user knows why they got the message and that they need to log in to openstreetmap.org etc.etc.)? Should we make an effort to catch the error in order to allow a translation? Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev -- James Michael DuPont Member of Free Libre Open Source Software Kosova and Albania flossk.org flossal.org ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] License Change Phase III
Frederik Ramm wrote: Hi, when the API is switched to license change phase 3, any attempt to open a changeset by someone who hasn't yet either agreed to, or rejected, the contributor terms will be met with a 403 Forbidden error code. Will JOSM display the content of that error message to the user (so that the user knows why they got the message and that they need to log in to openstreetmap.org etc.etc.)? Should we make an effort to catch the error in order to allow a translation? No, I just did some tests and to the best of my knowledge, the following will happen: * If an Error field is present in the header, JOSM will print it to the command line, but *not* the response body. * Otherwise it will print the response body to the command line. * There will be a message dialog with the text: Authorisation at the OSM server with the OAuth token 'null' failed. The token is not authorised to access the protected resource 'http://api06.openstreetmap.org/api/0.6/changeset/*/upload'. Please launch the preferences dialog and retrieve another OAuth token. Note, that this is shown even if no OAuth is involved, so the message is bogus. Suggested course of action: * Fix the message and make a release ASAP. * Wait for the server change to happen and check if it really works. Make a point release if not. Especially helpful would be an opportunity to test on the development server or at least have a prepared git branch of the rails code prior to the change. Paul ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
