Re: [OSM-dev] Coastline changes Antarctica
On Mon, Mar 11, 2013 at 10:53:16AM -0700, Paul Norman wrote: From: Jochen Topf [mailto:joc...@remote.org] Sent: Monday, March 11, 2013 10:17 AM Subject: Re: [OSM-dev] Coastline changes Antarctica If tile.osm.org has by now switched to using OSMCoastline and uses a current version there is no impact. If it still uses coastcheck it will break. I believe the toolchain on tile.osm.org uses the Feb 8th 2013 version of coastcheck. You'll need to talk to jburgess to make sure you don't break osm.org with your import. I see you put him on Cc. So, Jon, please speak up if there are any issues. One thing I forgot to mention in my blog post: OSMCoastline doesn't simplify the coastline. In the long run Christophs tool does a better job, in the short run you can either keep using whatever creates the shoreline 300 file, or just don't do it. I don't really see the need for the simplification from a performance perspective. (Low-zoom tiles are not rendered that often and there are so few of them that it doesn't matter if it takes a little bit longer.) And for a better looking coastline in low zoom levels you need to do more than just line simplification. Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] How to check if a user has entered valid openstreetmap username/password pair using php?
I am writing an app which allows users to submit values to pre-defined keys. But in order to make these edits by the user's own name, I first need to check if s/he has entered valid username/password combination. And I want to check it against the OSM user database. What is the easiest way to do it? And I'm using php for that ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On 12/03/13 08:25, Jochen Topf wrote: On Mon, Mar 11, 2013 at 10:53:16AM -0700, Paul Norman wrote: From: Jochen Topf [mailto:joc...@remote.org] Sent: Monday, March 11, 2013 10:17 AM Subject: Re: [OSM-dev] Coastline changes Antarctica If tile.osm.org has by now switched to using OSMCoastline and uses a current version there is no impact. If it still uses coastcheck it will break. I believe the toolchain on tile.osm.org uses the Feb 8th 2013 version of coastcheck. You'll need to talk to jburgess to make sure you don't break osm.org with your import. I see you put him on Cc. So, Jon, please speak up if there are any issues. As Paul said tile.osm.org is using a local copy of the files from the old system that is only updated manually and irregularly. Andy and I were talking about this last week and were of the opinion that we should switch to using your data, and to using sea polygons with land as the default background rather than the current system, and I think Andy would happily take a patch against openstreetmap-carto which did that. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
From: Jochen Topf [mailto:joc...@remote.org] Sent: Tuesday, March 12, 2013 1:25 AM Subject: Re: [OSM-dev] Coastline changes Antarctica On Mon, Mar 11, 2013 at 10:53:16AM -0700, Paul Norman wrote: From: Jochen Topf [mailto:joc...@remote.org] Sent: Monday, March 11, 2013 10:17 AM Subject: Re: [OSM-dev] Coastline changes Antarctica If tile.osm.org has by now switched to using OSMCoastline and uses a current version there is no impact. If it still uses coastcheck it will break. I believe the toolchain on tile.osm.org uses the Feb 8th 2013 version of coastcheck. You'll need to talk to jburgess to make sure you don't break osm.org with your import. I see you put him on Cc. So, Jon, please speak up if there are any issues. The I believe was about the version, not about using coastcheck. If it will break coastcheck as you've said above, it will cause issues on tile.osm.org. You should not import the -180/180 part until a plan for tile.osm.org has been worked out. However, are you certain it breaks coastcheck if the coastline is oriented the right way? My understanding was it could use the direction of a coastline fragment to work out which side was land. ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On Tue, Mar 12, 2013 at 01:53:30AM -0700, Paul Norman wrote: You should not import the -180/180 part until a plan for tile.osm.org has been worked out. If this isn't solved before we do the import we just add those bogus coastline ways back in as a temporary measure. Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On Tue, Mar 12, 2013 at 08:41:36AM +, Tom Hughes wrote: On 12/03/13 08:25, Jochen Topf wrote: On Mon, Mar 11, 2013 at 10:53:16AM -0700, Paul Norman wrote: From: Jochen Topf [mailto:joc...@remote.org] Sent: Monday, March 11, 2013 10:17 AM Subject: Re: [OSM-dev] Coastline changes Antarctica If tile.osm.org has by now switched to using OSMCoastline and uses a current version there is no impact. If it still uses coastcheck it will break. I believe the toolchain on tile.osm.org uses the Feb 8th 2013 version of coastcheck. You'll need to talk to jburgess to make sure you don't break osm.org with your import. I see you put him on Cc. So, Jon, please speak up if there are any issues. As Paul said tile.osm.org is using a local copy of the files from the old system that is only updated manually and irregularly. Andy and I were talking about this last week and were of the opinion that we should switch to using your data, and to using sea polygons with land as the default background rather than the current system, and I think Andy would happily take a patch against openstreetmap-carto which did that. I am not sure it is a good idea to switch to water polygons. Those polygons are much more complicated because they contain lots of holes, so they are slower to render. I'd only do that if really necessary (for instance when you want to mask something below the water polygon. Is the carto style live now? Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On Tue, Mar 12, 2013 at 01:53:30AM -0700, Paul Norman wrote: From: Jochen Topf [mailto:joc...@remote.org] Sent: Tuesday, March 12, 2013 1:25 AM Subject: Re: [OSM-dev] Coastline changes Antarctica On Mon, Mar 11, 2013 at 10:53:16AM -0700, Paul Norman wrote: From: Jochen Topf [mailto:joc...@remote.org] Sent: Monday, March 11, 2013 10:17 AM Subject: Re: [OSM-dev] Coastline changes Antarctica If tile.osm.org has by now switched to using OSMCoastline and uses a current version there is no impact. If it still uses coastcheck it will break. I believe the toolchain on tile.osm.org uses the Feb 8th 2013 version of coastcheck. You'll need to talk to jburgess to make sure you don't break osm.org with your import. I see you put him on Cc. So, Jon, please speak up if there are any issues. The I believe was about the version, not about using coastcheck. If it will break coastcheck as you've said above, it will cause issues on tile.osm.org. You should not import the -180/180 part until a plan for tile.osm.org has been worked out. However, are you certain it breaks coastcheck if the coastline is oriented the right way? My understanding was it could use the direction of a coastline fragment to work out which side was land. I am not an expert in coastcheck, but I do believe coastcheck still needs a closed polygon to work. Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On 12/03/13 09:07, Jochen Topf wrote: On Tue, Mar 12, 2013 at 08:41:36AM +, Tom Hughes wrote: Andy and I were talking about this last week and were of the opinion that we should switch to using your data, and to using sea polygons with land as the default background rather than the current system, and I think Andy would happily take a patch against openstreetmap-carto which did that. I am not sure it is a good idea to switch to water polygons. Those polygons are much more complicated because they contain lots of holes, so they are slower to render. I'd only do that if really necessary (for instance when you want to mask something below the water polygon. Interesting - that change was Andy's idea and I think the thought was to reduce the damage done by any breakage and to ensure that we're not matching any massive polygons in the busy (land) areas. Is the carto style live now? No, but I have been actively working on writing chef recipes to manage a new tile server, and they are based on it. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On Tue, Mar 12, 2013 at 09:12:39AM +, Tom Hughes wrote: On 12/03/13 09:07, Jochen Topf wrote: On Tue, Mar 12, 2013 at 08:41:36AM +, Tom Hughes wrote: Andy and I were talking about this last week and were of the opinion that we should switch to using your data, and to using sea polygons with land as the default background rather than the current system, and I think Andy would happily take a patch against openstreetmap-carto which did that. I am not sure it is a good idea to switch to water polygons. Those polygons are much more complicated because they contain lots of holes, so they are slower to render. I'd only do that if really necessary (for instance when you want to mask something below the water polygon. Interesting - that change was Andy's idea and I think the thought was to reduce the damage done by any breakage and to ensure that we're not matching any massive polygons in the busy (land) areas. OSMCoastline first generates the land polygons, them splits them, then creates the water polygons as inverse from the lang polygons. If the land polygons are broken, so are the water polygons. So I don't think you can reduce the chance of breakage that way. Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On 12/03/13 09:17, Jochen Topf wrote: On Tue, Mar 12, 2013 at 09:12:39AM +, Tom Hughes wrote: Interesting - that change was Andy's idea and I think the thought was to reduce the damage done by any breakage and to ensure that we're not matching any massive polygons in the busy (land) areas. OSMCoastline first generates the land polygons, them splits them, then creates the water polygons as inverse from the lang polygons. If the land polygons are broken, so are the water polygons. So I don't think you can reduce the chance of breakage that way. Sure, but the point was to fail to the land background colour not the sea so that you don't get flooding of the land. Don't know if it actually works like that but I think that was the idea. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
I'm not sure if it works, but I think it might be the better solution to have land flooded on the maps than to have water becoming deserts. On land we might have data which makes errors visually obvious: There are streets in the sea - something has to be wrong. At the ocean we don't have, but in deserts etc. it's the same: There is empty land - there might not yet be data here, or there's desert and really more or less nothing to see. Sure: flooded land does not look very well, but I guess it's found and fixed faster than water that's rendered as land. regards Peter Am 12.03.2013 10:20, schrieb Tom Hughes: On 12/03/13 09:17, Jochen Topf wrote: On Tue, Mar 12, 2013 at 09:12:39AM +, Tom Hughes wrote: Interesting - that change was Andy's idea and I think the thought was to reduce the damage done by any breakage and to ensure that we're not matching any massive polygons in the busy (land) areas. OSMCoastline first generates the land polygons, them splits them, then creates the water polygons as inverse from the lang polygons. If the land polygons are broken, so are the water polygons. So I don't think you can reduce the chance of breakage that way. Sure, but the point was to fail to the land background colour not the sea so that you don't get flooding of the land. Don't know if it actually works like that but I think that was the idea. Tom ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On Tue, Mar 12, 2013 at 09:20:51AM +, Tom Hughes wrote: On 12/03/13 09:17, Jochen Topf wrote: On Tue, Mar 12, 2013 at 09:12:39AM +, Tom Hughes wrote: Interesting - that change was Andy's idea and I think the thought was to reduce the damage done by any breakage and to ensure that we're not matching any massive polygons in the busy (land) areas. OSMCoastline first generates the land polygons, them splits them, then creates the water polygons as inverse from the lang polygons. If the land polygons are broken, so are the water polygons. So I don't think you can reduce the chance of breakage that way. Sure, but the point was to fail to the land background colour not the sea so that you don't get flooding of the land. Don't know if it actually works like that but I think that was the idea. Depends on where the error is. When the error is in the coastline assembly and extraction (which is the most likely case, we have seen this often enough) it will not help. Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] How to check if a user has entered valid openstreetmap username/password pair using php?
On Tue, 12 Mar 2013, Sazal Sthapit wrote: I am writing an app which allows users to submit values to pre-defined keys. But in order to make these edits by the user's own name, I first need to check if s/he has entered valid username/password combination. And I want to check it against the OSM user database. What is the easiest way to do it? And I'm using php for that You should *not* be asking for their username and password, but instead use the OAuth service: http://wiki.openstreetmap.org/wiki/Oauth From PHP, you would use the oauth pecl extension (http://pecl.php.net/package/oauth) to do the necessary work. cheers, Derick ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] How to check if a user has entered valid openstreetmap username/password pair using php?
If you're going to be communicating with the OSM API server directly from PHP I'd recommend Services_OpenStreetMap ( https://pear.php.net/package/Services_OpenStreetMap ). It's fully unit tested and allows for mock requests so you can test your app without hitting the OSM server until you're sure that you have everything in place. ;) Ken Disclaimer: I'm the guy that developed it. On Tue, Mar 12, 2013 at 8:42 AM, Sazal Sthapit sazalstha...@gmail.comwrote: I am writing an app which allows users to submit values to pre-defined keys. But in order to make these edits by the user's own name, I first need to check if s/he has entered valid username/password combination. And I want to check it against the OSM user database. What is the easiest way to do it? And I'm using php for that ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev -- http://blogs.linux.ie/kenguest/ ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] How to check if a user has entered valid openstreetmap username/password pair using php?
On 12/03/2013 09:53, Derick Rethans wrote: You should *not* be asking for their username and password WHS in Spades. It's incredibly bad practice, isn't very robust and I for one wouldn't trust any application these days that asked me for plain credentials. J. ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On 12 March 2013 09:12, Tom Hughes t...@compton.nu wrote: I am not sure it is a good idea to switch to water polygons. Those polygons are much more complicated because they contain lots of holes, so they are slower to render. I'd only do that if really necessary (for instance when you want to mask something below the water polygon. Interesting - that change was Andy's idea and I think the thought was to reduce the damage done by any breakage and to ensure that we're not matching any massive polygons in the busy (land) areas. So my line of thinking is as follows: 1) Jochen's proposed changes are going to break all coastcheck-created shapefiles, so openstreetmap-carto should instead use ones from OSMCoastline 2) Jochen does some form of QA for OSMCoastline so they are good to use directly 3) If you're not using hillshading, inverse vs normal makes no visual difference. But as soon as you use hillshading, you want inverse. So all else being equal, inverse should be the default 4) It's also confusing to have the map background as blue, when most people editing stylesheets think the background colour would be the land colour. 5) The vast majority of rendered tiles are all land. So it seems strange to draw a blue background, to immediately colour it with a land polygon, in almost every case. I take the point about the complexity of water polygons vs land polygons though, it's not something I'd thought of. I wonder if it invalidates the performance advantages described in 5) ? Cheers, Andy ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Coastline changes Antarctica
On Tuesday 12 March 2013, Jochen Topf wrote: OSMCoastline first generates the land polygons, them splits them, then creates the water polygons as inverse from the lang polygons. If the land polygons are broken, so are the water polygons. So I don't think you can reduce the chance of breakage that way. Possibly a better way to prevent large errors in the coastline would be to maintain a simplified version known to be free of large errors and use it to create bounds for the real up-to-date coastline. As you said the quality of the OSM coastline is quite good these days globally so at least on the land side it can be said with very high confidence that a few kilometers from the OSM coastline there is only land. So using a correspondingly buffered old and verified land polygon in addition to the real one would prevent large errors either by accident or by vandalism and would not hamper real improvements of the data. I don't know how often you discard the new data based on comparison with previous day data but the above would be an alternative to that. Greetings, -- Christoph Hormann http://www.imagico.de/ ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Zeroing or Extending a Hillshade-Tiff
Am 11.03.2013 21:10, schrieb Sven Geggus: Peter Körner osm-li...@mazdermind.de wrote: what way would you choose and wich tools could be used to go that way? Use the Water-Polygons from openstreetmapdata.com instead of land polygons. That's not that easy for the polar regions, because transforming the splittet polygons to the destination projection results in gaps because of straigt lines not beeing curved. For the land there are complete polygons which are used on the Antarctica map but there are no complete water polygons, because they would be too complex (a huge polygon with 400.000+ holes). So in order to get this right one would need to modify jochend osmcoastline tool to support EPSG:3031 natively, to all corrdinates are transformed before splitting and calculating the water polygons. Peter ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
