Re: [OSM-talk] Coastline update process seems to be broken - major costline change near the Gulf of Ob
On Thu, Sep 15, 2022 at 01:05:51AM +0200, Marc_marc wrote: > I have learn about this area and it seem that the Gulf of Ob is an area > affected by tiles. > so the coastline should follow the Gulf as before and not stop somewhere > inside the Gulf it-self > > I have reverted the coastline change in > https://www.openstreetmap.org/changeset/126200089 Thanks. I have manually "unfrozen" the processing now. We'll probably have some other bad edits that make it through this way, but at least the big one is avoided. Jochen -- Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline update process seems to be broken - costline change near Bahía de Bluefields, Nicaragua
Hello, Le 15.09.22 à 01:05, Marc_marc a écrit : I hope this allow the export to resume this night. unfortunately not I guess the blocking factor now is the change around https://www.openstreetmap.org/way/1087702973 https://overpass-turbo.eu/s/1lTm https://www.openstreetmap.org/changeset/125145822 not having any knowledge of this place, i wrote to the previous contributor. however, i have the impression that this lagoon is largely connected to the sea and should therefore be influenced by the tides. and that the part of the change concerning natural=coastline is therefore wrong Regards, Marc ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline update process seems to be broken - major costline change near the Gulf of Ob
Hello, I have learn about this area and it seem that the Gulf of Ob is an area affected by tiles. so the coastline should follow the Gulf as before and not stop somewhere inside the Gulf it-self I have reverted the coastline change in https://www.openstreetmap.org/changeset/126200089 talk with the previous contributor in https://www.openstreetmap.org/changeset/124352504 I still have an issue with a branch inside the Gulf https://www.openstreetmap.org/way/735010441 river should stop at the coastline no ? but how to tag that, a strait? ? feel free to review, talk, ... and I hope this allow the export to resume this night. Regards, Marc ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline/Icesheet extracts moving to new server
Hi! the OSM extracts formerly at openstreetmapdata.com are moving to their new home at https://osmdata.openstreetmap.de/ . If you are using the coastlines or icesheet downloads switch to that site now! If you are using generalized datasets, contact me. These datasets are not available on the new site (yet) and we are trying to gauge interest. Some more background here: https://blog.jochentopf.com/2019-03-07-the-new-osmdata-service.html Jochen -- Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Thu, Nov 21, 2013 at 09:24:46PM -0800, Paul Norman wrote: From: Jochen Topf [mailto:joc...@remote.org] Sent: Monday, November 18, 2013 8:13 AM To: talk@openstreetmap.org Subject: [OSM-talk] Coastline updates Hi! For the last about two weeks we haven't gotten any coastline updates through. The problem is that every day there is something broken somewhere with the coastline. Often problems get fixed the same day, but new problems show up the next. Can't osmcoastline localize these problems to a small area? Coastcheck kept any errors from impacting entire continents, even when there were high numbers of errors. I remember it finding 2k errors when I started running it regularly! Osmcoastline fixes small gaps in the data. I don't know of anything more coastcheck did. If anybody can give me any algorithms how to fix the data or localize these problems, please do. We're always going to have local coastline errors, so we have to figure out how to recover from them I think we have to face it: The approach of allowing the user to add anything to the map and later fix it has failed. I strongly believed in it for the longest time. But I don't any more. We have to have stronger guarantees in the data structures and more checks in editors and in the API. Remember, the coastline is one of the easier problems there. Boundaries are much more complicated. Having spent months already on this easy problem, I don't see how our limited ressources are going to solve this if we don't tackle the problem in a very different way. Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
Hi, I think we have to face it: The approach of allowing the user to add anything to the map and later fix it has failed. I strongly believed in it for the longest time. But I don't any more. We have to have stronger guarantees in the data structures and more checks in editors and in the API. Remember, the coastline is one of the easier problems there. Boundaries are much more complicated. Having spent months already on this easy problem, I don't see how our limited ressources are going to solve this if we don't tackle the problem in a very different way. A first step might be to disallow upload of certain easily detected errors (e.g. self intersecting version=1 ways with coastline tags) either in the editor(s) or in the API. This is certainly not going to magically fix all coastline problems but it will lessen the workload of the advanced mappers who try to fix coastline problems. Regards, Patrick Petschge Kilian ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
From: Jochen Topf [mailto:joc...@remote.org] Sent: Friday, November 22, 2013 1:51 AM To: Paul Norman Cc: talk@openstreetmap.org Subject: Re: [OSM-talk] Coastline updates On Thu, Nov 21, 2013 at 09:24:46PM -0800, Paul Norman wrote: From: Jochen Topf [mailto:joc...@remote.org] Sent: Monday, November 18, 2013 8:13 AM To: talk@openstreetmap.org Subject: [OSM-talk] Coastline updates Hi! For the last about two weeks we haven't gotten any coastline updates through. The problem is that every day there is something broken somewhere with the coastline. Often problems get fixed the same day, but new problems show up the next. Can't osmcoastline localize these problems to a small area? Coastcheck kept any errors from impacting entire continents, even when there were high numbers of errors. I remember it finding 2k errors when I started running it regularly! Osmcoastline fixes small gaps in the data. I don't know of anything more coastcheck did. If anybody can give me any algorithms how to fix the data or localize these problems, please do. A particular square (400x400 mercator km, I think) containing coastline can be evaluated without considering the rest of the continent thanks to the directionality of coastline ways mattering. You'd periodically get squares that would end up incorrect, but it wouldn't generally cause incorrect results outside that square. I don't know any details of the algorithms used since I didn't write or maintain them, I just know the results. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Friday 22 November 2013, Paul Norman wrote: A particular square (400x400 mercator km, I think) containing coastline can be evaluated without considering the rest of the continent thanks to the directionality of coastline ways mattering. You'd periodically get squares that would end up incorrect, but it wouldn't generally cause incorrect results outside that square. I suggested something similar some time ago - processing in tiles would allow partial updates of the valid areas and the invalid tiles would simply be left in the previous state. Given the dynamics of the errors in the OSM inspector this would probably not cause any of the tiles to get overly old due to persistent errors. This is however not trivial to implement, it would not produce full unsplit polygons (which are sometimes needed - not for normal rendering though) and it would occasionally lead to small artefacts at the tile boundaries when one tile is changed and the other tile is not. -- Christoph Hormann http://www.imagico.de/ ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Wed, Nov 20, 2013 at 10:49:36PM +0100, Jochen Topf wrote: BTW it seems that the inspector doesn't show icons on errors in the lowest zoomlevel (experienced with Firefox and Opera). Works for me. What you are seeing might be due to a different known bug with OSMI: If the 180° line is in the view, it doesn't show the overlay at all. Of course this happens more often in lower zoom levels, because the chances are greater that the 180° line is inside your window. Try moving the map around or making your window smaller. Hm, you are right. I have seen the same problem now. Strange. Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
From: Jochen Topf [mailto:joc...@remote.org] Sent: Monday, November 18, 2013 8:13 AM To: talk@openstreetmap.org Subject: [OSM-talk] Coastline updates Hi! For the last about two weeks we haven't gotten any coastline updates through. The problem is that every day there is something broken somewhere with the coastline. Often problems get fixed the same day, but new problems show up the next. Can't osmcoastline localize these problems to a small area? Coastcheck kept any errors from impacting entire continents, even when there were high numbers of errors. I remember it finding 2k errors when I started running it regularly! We're always going to have local coastline errors, so we have to figure out how to recover from them ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
Jochen Topf wrote: I have now changed the coastline update process from once a day to once every 4 hours. This means updates show up quicker in the OSM Inspector at http://tools.geofabrik.de/osmi/?view=coastline . Some mappers still break the coastlines faster than you check them. I looked at a lot of the 4h-updates of your inspector and there was always an error. BTW it seems that the inspector doesn't show icons on errors in the lowest zoomlevel (experienced with Firefox and Opera). Thomas ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Wed, Nov 20, 2013 at 06:53:15PM +0100, malenki wrote: Jochen Topf wrote: I have now changed the coastline update process from once a day to once every 4 hours. This means updates show up quicker in the OSM Inspector at http://tools.geofabrik.de/osmi/?view=coastline . Some mappers still break the coastlines faster than you check them. I looked at a lot of the 4h-updates of your inspector and there was always an error. I have seen the same thing. :-( BTW it seems that the inspector doesn't show icons on errors in the lowest zoomlevel (experienced with Firefox and Opera). Works for me. What you are seeing might be due to a different known bug with OSMI: If the 180° line is in the view, it doesn't show the overlay at all. Of course this happens more often in lower zoom levels, because the chances are greater that the 180° line is inside your window. Try moving the map around or making your window smaller. Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline updates
Hi! For the last about two weeks we haven't gotten any coastline updates through. The problem is that every day there is something broken somewhere with the coastline. Often problems get fixed the same day, but new problems show up the next. I have now changed the coastline update process from once a day to once every 4 hours. This means updates show up quicker in the OSM Inspector at http://tools.geofabrik.de/osmi/?view=coastline . If you fix something, you can see the result earlier and the chances that we get a good coastline increase. Please use the OSM Inspector to check on your own and other peoples work. Remember the coastline has to be one unbroken line of ways (tagged natural=coastline) that are connected end-to-end. The land always has to be on the left side, the water on the right side of that way. Never leave the coastline in a broken state, even if you think you'll come back to it tomorrow. Unless with most other stuff you edit in OSM, if you break the coastline in one place, it might mean the rest of the world doesn't get coastline updates! Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Monday 18 November 2013, Jochen Topf wrote: Hi! For the last about two weeks we haven't gotten any coastline updates through. The problem is that every day there is something broken somewhere with the coastline. Often problems get fixed the same day, but new problems show up the next. I have now changed the coastline update process from once a day to once every 4 hours. This means updates show up quicker in the OSM Inspector at http://tools.geofabrik.de/osmi/?view=coastline . Sounds good. This should also increase the chance that if you see an error in the OSMI it is not already fixed (which is very common at the moment and somewhat annoying of course). How sensitive is your system by the way in discarding a coastline as broken? Obviously any unfixable error in one of the four large continental coastlines will trigger it. Same for large islands like Greenland and New Guinea i suppose. But there probably is a limit. There have for example been many coastline errors in the Philippines recently due to recent mapping activity there but many on fairly small islands. -- Christoph Hormann http://www.imagico.de/ ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline generation resumed
WOW!!! all of the errors seems to be fixed as of now (2002 CET), even the two which show up on the slippymap. good job everyone... -S On Sat, Aug 4, 2012 at 2:26 AM, Paul Norman penor...@mac.com wrote: Whoops - looks like I had disabled the cron job. Files should start uploading at about 2-3 AM UTC. -Original Message- From: Simone Cortesi [mailto:sim...@cortesi.com] Sent: Friday, August 03, 2012 2:34 PM To: Paul Norman Cc: osm-talk Subject: Re: [OSM-talk] Coastline generation resumed Paul, are you still running it 3 times a day? It seems to be in a frozen state since at least 4 days. Fixed errors still show up. Any idea? Thanks, Simone On Wed, Jul 25, 2012 at 7:42 AM, Paul Norman penor...@mac.com wrote: Minor update: I am now running three times a day. Exact upload times depend on runtime which is largely a factor of dev server speed. Errors points are definitely going down. Many thanks for David Groom for both hosting the visualization and for often fixing errors before I can get to them, even though I know when my runs finish. From: Paul Norman [mailto:penor...@mac.com] Sent: Sunday, July 22, 2012 11:55 PM To: 'osm-talk' Subject: [OSM-talk] Coastline generation resumed I have resumed my daily generation of coastline files. These are generated with the coastcheck program[1] from my jxapi database starting at 5 AM pacific time. They take 3-4 hours to generate and upload, depending on my internet speed at the time. The completed files are uploaded to http://pnorman.dev.openstreetmap.org/coastlines/ If opening these shapefiles in QGIS be sure to create a spatial index for tolerable performance. There is a visualization of errors at http://www.wightpaths.co.uk/coast/ Many of the errors appear to be short errors between ways that became disconnected. More complicated errors are often best fixed by deleting the bad coastline and retracing. [1]: http://svn.openstreetmap.org/applications/utils/coastcheck/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk -- -S -- -S ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline generation resumed
Paul, are you still running it 3 times a day? It seems to be in a frozen state since at least 4 days. Fixed errors still show up. Any idea? Thanks, Simone On Wed, Jul 25, 2012 at 7:42 AM, Paul Norman penor...@mac.com wrote: Minor update: I am now running three times a day. Exact upload times depend on runtime which is largely a factor of dev server speed. Errors points are definitely going down. Many thanks for David Groom for both hosting the visualization and for often fixing errors before I can get to them, even though I know when my runs finish. From: Paul Norman [mailto:penor...@mac.com] Sent: Sunday, July 22, 2012 11:55 PM To: 'osm-talk' Subject: [OSM-talk] Coastline generation resumed I have resumed my daily generation of coastline files. These are generated with the coastcheck program[1] from my jxapi database starting at 5 AM pacific time. They take 3-4 hours to generate and upload, depending on my internet speed at the time. The completed files are uploaded to http://pnorman.dev.openstreetmap.org/coastlines/ If opening these shapefiles in QGIS be sure to create a spatial index for tolerable performance. There is a visualization of errors at http://www.wightpaths.co.uk/coast/ Many of the errors appear to be short errors between ways that became disconnected. More complicated errors are often best fixed by deleting the bad coastline and retracing. [1]: http://svn.openstreetmap.org/applications/utils/coastcheck/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk -- -S ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline generation resumed
Whoops - looks like I had disabled the cron job. Files should start uploading at about 2-3 AM UTC. -Original Message- From: Simone Cortesi [mailto:sim...@cortesi.com] Sent: Friday, August 03, 2012 2:34 PM To: Paul Norman Cc: osm-talk Subject: Re: [OSM-talk] Coastline generation resumed Paul, are you still running it 3 times a day? It seems to be in a frozen state since at least 4 days. Fixed errors still show up. Any idea? Thanks, Simone On Wed, Jul 25, 2012 at 7:42 AM, Paul Norman penor...@mac.com wrote: Minor update: I am now running three times a day. Exact upload times depend on runtime which is largely a factor of dev server speed. Errors points are definitely going down. Many thanks for David Groom for both hosting the visualization and for often fixing errors before I can get to them, even though I know when my runs finish. From: Paul Norman [mailto:penor...@mac.com] Sent: Sunday, July 22, 2012 11:55 PM To: 'osm-talk' Subject: [OSM-talk] Coastline generation resumed I have resumed my daily generation of coastline files. These are generated with the coastcheck program[1] from my jxapi database starting at 5 AM pacific time. They take 3-4 hours to generate and upload, depending on my internet speed at the time. The completed files are uploaded to http://pnorman.dev.openstreetmap.org/coastlines/ If opening these shapefiles in QGIS be sure to create a spatial index for tolerable performance. There is a visualization of errors at http://www.wightpaths.co.uk/coast/ Many of the errors appear to be short errors between ways that became disconnected. More complicated errors are often best fixed by deleting the bad coastline and retracing. [1]: http://svn.openstreetmap.org/applications/utils/coastcheck/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk -- -S ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline generation resumed
And thanks to you Paul for the data files in the first place. Also I wouldn't want the impression I'm the only one fixing coastline errors, so thanks to the rest of you as well. Just to be clear the error points layer is automatically updated from Paul's files. The other error layers require manual generation so may only get done once a day. Also due to the number of error points the map current won't display in some (maybe all) versions of IE, but is OK in Firefox Chrome. I can't be bothered to fix this, as the number of error points is falling daily, and so it won't be an issue in a while. David - Original Message - From: Paul Norman To: 'osm-talk' Cc: David Groom Sent: Wednesday, July 25, 2012 6:42 AM Subject: RE: [OSM-talk] Coastline generation resumed Minor update: I am now running three times a day. Exact upload times depend on runtime which is largely a factor of dev server speed. Errors points are definitely going down. Many thanks for David Groom for both hosting the visualization and for often fixing errors before I can get to them, even though I know when my runs finish. From: Paul Norman [mailto:penor...@mac.com] Sent: Sunday, July 22, 2012 11:55 PM To: 'osm-talk' Subject: [OSM-talk] Coastline generation resumed I have resumed my daily generation of coastline files. These are generated with the coastcheck program[1] from my jxapi database starting at 5 AM pacific time. They take 3-4 hours to generate and upload, depending on my internet speed at the time. The completed files are uploaded to http://pnorman.dev.openstreetmap.org/coastlines/ If opening these shapefiles in QGIS be sure to create a spatial index for tolerable performance. There is a visualization of errors at http://www.wightpaths.co.uk/coast/ Many of the errors appear to be short errors between ways that became disconnected. More complicated errors are often best fixed by deleting the bad coastline and retracing. [1]: http://svn.openstreetmap.org/applications/utils/coastcheck/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline generation resumed
Minor update: I am now running three times a day. Exact upload times depend on runtime which is largely a factor of dev server speed. Errors points are definitely going down. Many thanks for David Groom for both hosting the visualization and for often fixing errors before I can get to them, even though I know when my runs finish. From: Paul Norman [mailto:penor...@mac.com] Sent: Sunday, July 22, 2012 11:55 PM To: 'osm-talk' Subject: [OSM-talk] Coastline generation resumed I have resumed my daily generation of coastline files. These are generated with the coastcheck program[1] from my jxapi database starting at 5 AM pacific time. They take 3-4 hours to generate and upload, depending on my internet speed at the time. The completed files are uploaded to http://pnorman.dev.openstreetmap.org/coastlines/ If opening these shapefiles in QGIS be sure to create a spatial index for tolerable performance. There is a visualization of errors at http://www.wightpaths.co.uk/coast/ Many of the errors appear to be short errors between ways that became disconnected. More complicated errors are often best fixed by deleting the bad coastline and retracing. [1]: http://svn.openstreetmap.org/applications/utils/coastcheck/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline generation resumed
I have resumed my daily generation of coastline files. These are generated with the coastcheck program[1] from my jxapi database starting at 5 AM pacific time. They take 3-4 hours to generate and upload, depending on my internet speed at the time. The completed files are uploaded to http://pnorman.dev.openstreetmap.org/coastlines/ If opening these shapefiles in QGIS be sure to create a spatial index for tolerable performance. There is a visualization of errors at http://www.wightpaths.co.uk/coast/ Many of the errors appear to be short errors between ways that became disconnected. More complicated errors are often best fixed by deleting the bad coastline and retracing. [1]: http://svn.openstreetmap.org/applications/utils/coastcheck/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline generation resumed
On Mon, Jul 23, 2012 at 8:55 AM, Paul Norman penor...@mac.com wrote: There is a visualization of errors at http://www.wightpaths.co.uk/coast/ Many of the errors appear to be short errors between ways that became disconnected. More complicated errors are often best fixed by deleting the bad coastline and retracing. Thanks a lot! -- -S ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline rendering in Quebec
On the talk-ca list there have been a few discussion about problems with flooded areas in southern Quebec. The conclusion seems to be that the problems are due to the rendering of the coastline which only gets updated every once in a while. The two cases are: * http://www.openstreetmap.org/?lat=45.6101lon=-73.4411zoom=13layers=M This problem is comparatively recent. Current data appears to be correct. Problem is visible on zoom=13 * http://www.openstreetmap.org/?lat=45.342lon=-74.24zoom=9layers=M This one has been around for at least 6 months. Current data appears to be correct. Problem is visible on zoom=9 We haven't been able to figure out who to contact about these issues. Can anyone point us in the right direction? Thanks, Harald. -- Please use encrypted communication whenever possible! Key-ID: 0x199DC50F ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates still running?
On Wed, 2012-04-11 at 20:41 +0100, OJ W wrote: Is there some problem with the coastline at Doha airport? The new coastline (changed since February) doesn't yet appear in rendered maps, but looks reasonable in the Edit view: http://www.openstreetmap.org/?lat=25.24915lon=51.61024zoom=15layers=M I have just deployed an updated set of coastline shapefiles which look like they will fix the problem once the area is rendered again. Jon ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
Hi Paul, do you plan another update? Regards Thomas Paul Norman wrote I have completed another coastline generation and it has uploaded. This version respects odbl=clean. The shapefiles are in their normal place at http://pnorman.dev.openstreetmap.org/coastlines/ Included is a .osm file with all the error points. An overview can be found at http://maps.paulnorman.ca/coastlines2.png Detailed views: Great Lakes: http://maps.paulnorman.ca/coastlines-lakes2.png Europe: http://maps.paulnorman.ca/coastlines-europe2.png US West Coast: http://maps.paulnorman.ca/coastlines-west2.png Australia: http://maps.paulnorman.ca/coastlines-au2.png There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State The mouth of the Columbia river in Washington The Eastern Australia coast The points indicated by the maps and by processedc_p files are where coastcheck encountered an error and had to guess where the coastline continues. These should generally represent transitions between ODbL clean and ODbL dirty sections of the coastline. Islands with no ODbL clean sections will not generate any error points. http://www.wightpaths.co.uk/coast/CT-only.php and http://suncobalt.homeip.net:82/coastline.php are two visualizations of errors but neither has yet updated to the new data. I hope to complete one more run of the ODbL-clean coastlines before the downtime. During the downtime I will be running a set of ODbL-clean and conventional coastlines (and a planet file). If diffs are available during the rebuild process I will be generating them then and reloading my database when the ODbL planet is published. Technical details: This new run takes into account odbl=clean. It may not correctly handle 1. Objects that are dirty via a changeset override 2. Objects that WTFE reported clean but are now dirty 3. Certain sequences of edits and tag additions that are not likely to occur frequently with coastlines and which require access to a full history database to evaluate The data is from 7 AM PST and the ODbL status is slightly more recent. ___ talk mailing list talk@ http://lists.openstreetmap.org/listinfo/talk -- View this message in context: http://gis.19327.n5.nabble.com/Coastline-Update-tp5608185p5617862.html Sent from the General Discussion mailing list archive at Nabble.com. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
Replication diffs have just resumed from a temporary location. I am not yet certain if my server will be able to keep up with these diffs. If it is, I will start another run at about midnight UTC. I have a good half-dozen apps that consume minutely diffs and I need to switch all of their locations -Original Message- From: ThomasB [mailto:toba0...@yahoo.de] Sent: Wednesday, April 04, 2012 7:01 AM To: talk@openstreetmap.org Subject: Re: [OSM-talk] Coastline Update Hi Paul, do you plan another update? Regards Thomas Paul Norman wrote I have completed another coastline generation and it has uploaded. This version respects odbl=clean. The shapefiles are in their normal place at http://pnorman.dev.openstreetmap.org/coastlines/ Included is a .osm file with all the error points. An overview can be found at http://maps.paulnorman.ca/coastlines2.png Detailed views: Great Lakes: http://maps.paulnorman.ca/coastlines-lakes2.png Europe: http://maps.paulnorman.ca/coastlines-europe2.png US West Coast: http://maps.paulnorman.ca/coastlines-west2.png Australia: http://maps.paulnorman.ca/coastlines-au2.png There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State The mouth of the Columbia river in Washington The Eastern Australia coast The points indicated by the maps and by processedc_p files are where coastcheck encountered an error and had to guess where the coastline continues. These should generally represent transitions between ODbL clean and ODbL dirty sections of the coastline. Islands with no ODbL clean sections will not generate any error points. http://www.wightpaths.co.uk/coast/CT-only.php and http://suncobalt.homeip.net:82/coastline.php are two visualizations of errors but neither has yet updated to the new data. I hope to complete one more run of the ODbL-clean coastlines before the downtime. During the downtime I will be running a set of ODbL-clean and conventional coastlines (and a planet file). If diffs are available during the rebuild process I will be generating them then and reloading my database when the ODbL planet is published. Technical details: This new run takes into account odbl=clean. It may not correctly handle 1. Objects that are dirty via a changeset override 2. Objects that WTFE reported clean but are now dirty 3. Certain sequences of edits and tag additions that are not likely to occur frequently with coastlines and which require access to a full history database to evaluate The data is from 7 AM PST and the ODbL status is slightly more recent. ___ talk mailing list talk@ http://lists.openstreetmap.org/listinfo/talk -- View this message in context: http://gis.19327.n5.nabble.com/Coastline- Update-tp5608185p5617862.html Sent from the General Discussion mailing list archive at Nabble.com. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
On 1-4-2012 3:40, Paul Norman wrote: Just be careful to not accidentally upload the .osm that indicate the problems. You should modify it to have upload='false' in there. Then JOSM will discourage you from uploading that file. osm version='0.6' upload='false' See http://josm.openstreetmap.de/ticket/4043 -- Lennard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
- Original Message - From: Steve Bennett stevag...@gmail.com To: Paul Norman penor...@mac.com Cc: talk@openstreetmap.org Sent: Sunday, April 01, 2012 12:58 AM Subject: Re: [OSM-talk] Coastline Update On Sat, Mar 31, 2012 at 2:26 PM, Paul Norman penor...@mac.com wrote: There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State The mouth of the Columbia river in Washington The Eastern Australia coast Speaking as an Eastern Australian coast dweller, what do we need to do? What do the red spots in the map mean, and what do we need to do about them? Steve What do the red dots mean? the red dots represent where there is a possibility of a gap in gap in the OSM coastline ways following the deletion of data which is happening this weekend. This gap could just be a few metres, or the dot could represent the start of a missing section of many 10's (or possibly 100's) of kilometres. In order for Mapnik to render coastline correctly there needs to be a continuos line of coastline ways around all landmasses. Any gaps in the coastline ways will lead to poor rendering. What can we do about this ? The missing sections in the coastline will need to be completed. There are various ways this can be done. In Australia there is the option of: tracing from Bing or AGRI. there is also the possibility of importing data. I did offer on the talk-au [1] list to re-import PGS data (relatively low quality), though I did ask whether it was better to delay and wait until someone had time to reimport ABS data If you are going to add in any coastline data please be aware that the direction it is drawn is very important. It must be drawn so that the sea is on the right hand side of the way. Although it would be possible in the next few days to redraw some coastline using JOSM and store this off line ready to upload when the database comes back on line, my opinion is that it is better now to do nothing until the new database comes back on line in a few days. I am sure that Paul Norman will then regenerate the shapefiles from which the reds dots are derived, and the error maps will be updated to show actual positions where coastline ways are then missing . Regards David [1] http://lists.openstreetmap.org/pipermail/talk-au/2012-March/008957.html Steve ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
Paul Norman wrote http://suncobalt.homeip.net:82/coastline.php are two visualizations of errors but neither has yet updated to the new data. It updated now. Thanks for providing the data. -- View this message in context: http://gis.19327.n5.nabble.com/Coastline-Update-tp5608185p5608324.html Sent from the General Discussion mailing list archive at Nabble.com. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
Paul A big thank you for providing all of the data. It has helped to greatly reduce the number of error points over the last week. Regards David - Original Message - From: Paul Norman penor...@mac.com To: talk@openstreetmap.org Sent: Saturday, March 31, 2012 4:26 AM Subject: [OSM-talk] Coastline Update I have completed another coastline generation and it has uploaded. This version respects odbl=clean. The shapefiles are in their normal place at http://pnorman.dev.openstreetmap.org/coastlines/ Included is a .osm file with all the error points. An overview can be found at http://maps.paulnorman.ca/coastlines2.png Detailed views: Great Lakes: http://maps.paulnorman.ca/coastlines-lakes2.png Europe: http://maps.paulnorman.ca/coastlines-europe2.png US West Coast: http://maps.paulnorman.ca/coastlines-west2.png Australia: http://maps.paulnorman.ca/coastlines-au2.png There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State The mouth of the Columbia river in Washington The Eastern Australia coast The points indicated by the maps and by processedc_p files are where coastcheck encountered an error and had to guess where the coastline continues. These should generally represent transitions between ODbL clean and ODbL dirty sections of the coastline. Islands with no ODbL clean sections will not generate any error points. http://www.wightpaths.co.uk/coast/CT-only.php and http://suncobalt.homeip.net:82/coastline.php are two visualizations of errors but neither has yet updated to the new data. I hope to complete one more run of the ODbL-clean coastlines before the downtime. During the downtime I will be running a set of ODbL-clean and conventional coastlines (and a planet file). If diffs are available during the rebuild process I will be generating them then and reloading my database when the ODbL planet is published. Technical details: This new run takes into account odbl=clean. It may not correctly handle 1. Objects that are dirty via a changeset override 2. Objects that WTFE reported clean but are now dirty 3. Certain sequences of edits and tag additions that are not likely to occur frequently with coastlines and which require access to a full history database to evaluate The data is from 7 AM PST and the ODbL status is slightly more recent. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
Toby wrote: Assuming you used the data I supplied this morning, it is actually from 12:30 AM CST last night when I started the jxapi query before going to bed. Also, it looks like http://www.wightpaths.co.uk/coast/CT-only.php has been updated with your new files since you sent your email. Perhaps I don't understand what I'm looking for, but have checked the 4 points on the Scottish coastlines indicated on the link above. I can't see what is wrong with any of them. Some of the ways were edited on the 24th March 2012 which I guess might have fixed whatever the issue was, but if the data is from (consults timezones) yesterday-ish then I'm not sure why they would still show. The points seem to correspond with Paul's Europe png too. Ed ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
- Original Message - From: Ed Loach e...@loach.me.uk To: 'Toby Murray' toby.mur...@gmail.com; talk@openstreetmap.org Sent: Saturday, March 31, 2012 11:58 AM Subject: Re: [OSM-talk] Coastline Update Toby wrote: Assuming you used the data I supplied this morning, it is actually from 12:30 AM CST last night when I started the jxapi query before going to bed. Also, it looks like http://www.wightpaths.co.uk/coast/CT-only.php has been updated with your new files since you sent your email. Perhaps I don't understand what I'm looking for, but have checked the 4 points on the Scottish coastlines indicated on the link above. I can't see what is wrong with any of them. Some of the ways were edited on the 24th March 2012 which I guess might have fixed whatever the issue was, but if the data is from (consults timezones) yesterday-ish then I'm not sure why they would still show. The points seem to correspond with Paul's Europe png too. I think the answer lies in the original comment from Paul [1] This is somewhat more aggressive than the rebuild will be, As far as I can tell the error points sometimes get displayed where there are what the JOSM relicencing plugin calls possible data loss. As such the error points produced by Paul, and the two maps built upon that data are an indication of possible problems, not a 100% definite statement of actual problems. Furthermore, as I understand it, none of the tools which find dirty ways and nodes are actually using the same logic as the actual rebuild will use, so its impossible to get a 100% accurate picture of what will happen. Regards David [1] http://lists.openstreetmap.org/pipermail/talk/2012-March/062486.html Ed ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
Toby wrote: Assuming you used the data I supplied this morning, it is actually from 12:30 AM CST last night when I started the jxapi query before going to bed. Also, it looks like http://www.wightpaths.co.uk/coast/CT-only.php has been updated with your new files since you sent your email. Perhaps I don't understand what I'm looking for, but have checked the 4 points on the Scottish coastlines indicated on the link above. I can't see what is wrong with any of them. Some of the ways were edited on the 24th March 2012 which I guess might have fixed whatever the issue was, but if the data is from (consults timezones) yesterday-ish then I'm not sure why they would still show. The points seem to correspond with Paul's Europe png too. I think the answer lies in the original comment from Paul [1] This is somewhat more aggressive than the rebuild will be, As far as I can tell the error points sometimes get displayed where there are what the JOSM relicencing plugin calls possible data loss. As such the error points produced by Paul, and the two maps built upon that data are an indication of possible problems, not a 100% definite statement of actual problems. Furthermore, as I understand it, none of the tools which find dirty ways and nodes are actually using the same logic as the actual rebuild will use, so its impossible to get a 100% accurate picture of what will happen. Regards David Nodes and ways are removed by cleanway. The exact logic used is as follows: Do nothing to v1 objects created by acceptors Do nothing to objects reported as clean by WTFE the last run Then, for ways: Do nothing to ways with odbl=clean Drop ways where WTFE reports a severity=normal problem with the first version Record the ways that were clean to avoid querying them next time For nodes: Drop nodes where WTFE reports a severity=normal problem Record the nodes that were clean to avoid querying them next time A dropped end or start node or a dropped way will result in a break and an error. If anyone has suggestions for improving the algorithm I would welcome them. Keep in mind that I only have access to the current version of the object and the WTFE response. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
On Sat, Mar 31, 2012 at 2:26 PM, Paul Norman penor...@mac.com wrote: There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State The mouth of the Columbia river in Washington The Eastern Australia coast Speaking as an Eastern Australian coast dweller, what do we need to do? What do the red spots in the map mean, and what do we need to do about them? Steve ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
On Fri, Mar 30, 2012 at 8:26 PM, Paul Norman penor...@mac.com wrote: I have completed another coastline generation and it has uploaded. This version respects odbl=clean. The shapefiles are in their normal place at http://pnorman.dev.openstreetmap.org/coastlines/ Included is a .osm file with all the error points. There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State I just pulled the osm file into josm. I did a check of a couple of error points in the osm file in Puget Sound (Edmunds WA.) They appear to be about 10+ meters from the shoreline according to the bing image. Since I'm new at this, but since I live in the Puget Sound and would like to help fix it, what is an acceptable error distance? Also - the bing image doesn't give a date and time to determine the tide level. Or am I missing something? Clifford ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
On Sun, 01 Apr 2012 09:31:53 Clifford Snow wrote: On Fri, Mar 30, 2012 at 8:26 PM, Paul Norman penor...@mac.com wrote: I have completed another coastline generation and it has uploaded. This version respects odbl=clean. The shapefiles are in their normal place at http://pnorman.dev.openstreetmap.org/coastlines/ Included is a .osm file with all the error points. There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State I just pulled the osm file into josm. I did a check of a couple of error points in the osm file in Puget Sound (Edmunds WA.) They appear to be about 10+ meters from the shoreline according to the bing image. Since I'm new at this, but since I live in the Puget Sound and would like to help fix it, what is an acceptable error distance? Also - the bing image doesn't give a date and time to determine the tide level. Or am I missing something? Are you sure the Bing image is correctly aligned? There is no guarantee that it is. Find a bunch of GPS traces nearby for a road or other very visible feature and ensure they line up with that feature on the Bing image. If they do, you're fine- use the Bing image to correct the coastline. If they don't, then use the tools in Potlatch or JOSM to move the Bing layer into alignment *then* correct the coastline. The coastline should follow the line of high tide. Use your best judgement to determine this. You're not missing something. Best wishes, Andrew ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
-Original Message- From: Andrew Errington [mailto:a.erring...@lancaster.ac.uk] Sent: Saturday, March 31, 2012 6:01 PM To: talk@openstreetmap.org Subject: Re: [OSM-talk] Coastline Update On Sun, 01 Apr 2012 09:31:53 Clifford Snow wrote: On Fri, Mar 30, 2012 at 8:26 PM, Paul Norman penor...@mac.com wrote: I have completed another coastline generation and it has uploaded. This version respects odbl=clean. The shapefiles are in their normal place at http://pnorman.dev.openstreetmap.org/coastlines/ Included is a .osm file with all the error points. There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State I just pulled the osm file into josm. I did a check of a couple of error points in the osm file in Puget Sound (Edmunds WA.) They appear to be about 10+ meters from the shoreline according to the bing image. Since I'm new at this, but since I live in the Puget Sound and would like to help fix it, what is an acceptable error distance? Also - the bing image doesn't give a date and time to determine the tide level. Or am I missing something? Are you sure the Bing image is correctly aligned? There is no guarantee that it is. Find a bunch of GPS traces nearby for a road or other very visible feature and ensure they line up with that feature on the Bing image. If they do, you're fine- use the Bing image to correct the coastline. If they don't, then use the tools in Potlatch or JOSM to move the Bing layer into alignment *then* correct the coastline. The coastline should follow the line of high tide. Use your best judgement to determine this. You're not missing something. The MapQuest Open Aerial imagery should be pretty well aligned. My procedure is as follows: Pick an area that needs work and download it Select natural=coastline | child natural=coastline in JOSM and run the validator on it Pick somewhere to start and delete dirty coastline and then start tracing. Just be careful to not accidentally upload the .osm that indicate the problems. A new set of files is up, with data from about 18 hours ago I believe. processedc_p.tar.bz2 is still uploading. I have another fresh set generating too. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline Update
I have completed another coastline generation and it has uploaded. This version respects odbl=clean. The shapefiles are in their normal place at http://pnorman.dev.openstreetmap.org/coastlines/ Included is a .osm file with all the error points. An overview can be found at http://maps.paulnorman.ca/coastlines2.png Detailed views: Great Lakes: http://maps.paulnorman.ca/coastlines-lakes2.png Europe: http://maps.paulnorman.ca/coastlines-europe2.png US West Coast: http://maps.paulnorman.ca/coastlines-west2.png Australia: http://maps.paulnorman.ca/coastlines-au2.png There are no significant multi-square flooded or dry areas. The following areas have significant number of error points: Pudget Sound in Washington State The mouth of the Columbia river in Washington The Eastern Australia coast The points indicated by the maps and by processedc_p files are where coastcheck encountered an error and had to guess where the coastline continues. These should generally represent transitions between ODbL clean and ODbL dirty sections of the coastline. Islands with no ODbL clean sections will not generate any error points. http://www.wightpaths.co.uk/coast/CT-only.php and http://suncobalt.homeip.net:82/coastline.php are two visualizations of errors but neither has yet updated to the new data. I hope to complete one more run of the ODbL-clean coastlines before the downtime. During the downtime I will be running a set of ODbL-clean and conventional coastlines (and a planet file). If diffs are available during the rebuild process I will be generating them then and reloading my database when the ODbL planet is published. Technical details: This new run takes into account odbl=clean. It may not correctly handle 1. Objects that are dirty via a changeset override 2. Objects that WTFE reported clean but are now dirty 3. Certain sequences of edits and tag additions that are not likely to occur frequently with coastlines and which require access to a full history database to evaluate The data is from 7 AM PST and the ODbL status is slightly more recent. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline Update
On Fri, Mar 30, 2012 at 10:26 PM, Paul Norman penor...@mac.com wrote: The data is from 7 AM PST and the ODbL status is slightly more recent. Assuming you used the data I supplied this morning, it is actually from 12:30 AM CST last night when I started the jxapi query before going to bed. Also, it looks like http://www.wightpaths.co.uk/coast/CT-only.php has been updated with your new files since you sent your email. Toby ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline rerender
Is there any way we can get a coastline rerender some time soon? It's been broken (but fixed in the data) around inverness for nearly a month now. Thanks Tom Davie ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline rerender
http://metro.teczno.com/#coastline - someone? On Jan 10, 2012, at 1:44 PM, Thomas Davie wrote: Is there any way we can get a coastline rerender some time soon? It's been broken (but fixed in the data) around inverness for nearly a month now. Thanks Tom Davie ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk michal migurski- m...@stamen.com 415.558.1610 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline errors ( was Argh, Canvec imports)
- Original Message - From: Simone Cortesi sim...@cortesi.com To: Michal Migurski m...@stamen.com Cc: Talk Openstreetmap talk@openstreetmap.org Sent: Thursday, November 17, 2011 9:54 AM Subject: Re: [OSM-talk] Argh, Canvec imports On Thu, Nov 17, 2011 at 08:40, Michal Migurski m...@stamen.com wrote: A cry of frustration: I do bimonthly runs of the worldwide coastlines (http://metro.teczno.com/#coastline), and Canada seems to be a recurring source of problems. What the heck is going on up there? I consistently see new imports of what seems to be Canvec data screwing up coastlines and making for some deeply broken renders: http://mike.teczno.com/img/broken-coast.png Most of that junk in the Atlantic Ocean is newly introduced within the last few weeks, and is making it difficult to get out a clean coastline suitable for rendering. It shows up in the main OSM mapnik tiles in Hudson Bay, too: http://www.openstreetmap.org/?lat=55.7lon=-83.6zoom=5layers=M I've been trying to fix problems as I encounter them and I've managed to fix invalid coastilnes around Baltimore, Houston, Tampa and the dreaded Montréal area in an effort to generate a usable map of North America, but this Canvec stuff is absolutely killing me. I care about the coastline too, long time ago there used to be this: http://www.openstreetmap.nl/coastlines.html where anyone could go and fix coastline errors that did show up on a purpose made mapnik layer. I see there is a geofabrik layer for that same purpos, but it is limited just to europe. Michal, are you aware of any such layer, but worldwide? Simone I use this http://www.wightpaths.co.uk/coast/ . I generate the error points from the error points shapefile at http://metro.teczno.com/#coastline My version is not as comprehensive as the old version at http://www.openstreetmap.nl/coastlines.html , since it only shows the error points. I try and remember to look every couple of weeks to see if there are new extracts http://metro.teczno.com/, and then regenerate my error file. David ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline extracts now added to metropolitan area extracts
Hi everyone, I've updated my metro extracts with some new cities and individual extracts of the coastline shapefiles for each area: http://metro.teczno.com/ I've been slowly adding cities, but I'm being somewhat U.S.-centric in my choices. If you have something you'd like to see in the list don't hesitate to contact me. It's just a simple matter of appending a line of text to a file! (and waiting). -mike. michal migurski- m...@stamen.com 415.558.1610 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline extracts now added to metropolitan area extracts
From: Michal Migurski [mailto:m...@stamen.com] Subject: [OSM-talk] Coastline extracts now added to metropolitan area extracts Hi everyone, I've updated my metro extracts with some new cities and individual extracts of the coastline shapefiles for each area: http://metro.teczno.com/ I've been slowly adding cities, but I'm being somewhat U.S.-centric in my choices. If you have something you'd like to see in the list don't hesitate to contact me. It's just a simple matter of appending a line of text to a file! (and waiting). -mike. Do you prefer the information as bboxes or polygons? Also, for cities that have metropolitan areas around them do you want the city itself, or the city and metropolitan area? ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline extracts now added to metropolitan area extracts
On Oct 9, 2011, at 7:06 PM, Paul Norman wrote: I've been slowly adding cities, but I'm being somewhat U.S.-centric in my choices. If you have something you'd like to see in the list don't hesitate to contact me. It's just a simple matter of appending a line of text to a file! (and waiting). -mike. Do you prefer the information as bboxes or polygons? Also, for cities that have metropolitan areas around them do you want the city itself, or the city and metropolitan area? Bbox with the surrounding metro area is best, I think. I've tried to add about a ring road's worth of padding around each one: http://metro.teczno.com/previews/atlanta.jpg http://metro.teczno.com/previews/berlin.jpg -mike. michal migurski- m...@stamen.com 415.558.1610 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline anf blau background
Dear experts, I rendered some area by mapnik from France and Germany derived from Europe.osm.bz2. But some part of them are blue. is it some problem with small coast line in this case? or no, that is because of some thing else? please see the attachment. Thank you in advance, Saphy attachment: Meta_10_535_352.png___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline broken ?
Pierre asked: Can someone help me to fix this. Yes. Just wait. Mapnik coastlines are updated at long intervals (wiki says every few weeks). Looks OK to me on the Osmarender layer. Ed ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline broken ?
Ed Loach e...@loach.me.uk wrote: Can someone help me to fix this. Yes. Just wait. Mapnik coastlines are updated at long intervals (wiki says every few weeks). Looks OK to me on the Osmarender layer. OK i just say this, thanks. I seems that the river bank removal has been updated (in mapnik render) but not the new coastline... Just wait ;-) -- Pierre-Alain Dorange OSM experiences : http://www.leretourdelautruche.com/map/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline broken ?
On 14/06/11 12:07, Pierre-Alain Dorange wrote: OK i just say this, thanks. I seems that the river bank removal has been updated (in mapnik render) but not the new coastline... Just wait ;-) The coastline data will be updated in a few weeks, but the mapnik layer won't notice this. It will only get re-rendered if some other change forces it to notice, or the tiles are manually /dirty'd. -- Borbus. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] coastline broken ?
I made a modification in my country coastline (France). I added a coastline for the Estuaire de la Gironde (estuary) that was previously build on river banks (but it was incorrect, it was not a river). So i split the riverbank and made it natural=coastline. But since (2 days) the rendering is bad (mapnik, openmapquest, bing) for this portion at some zoom level... Rendering has been update (the boundary associated is now correclty render). I check in the wiki and the coastline a made seems correct (the way was connected to previous one end-to-end, the direction is OK...). The map : http://www.openstreetmap.org/?lat=45.1089lon=-0.6574zoom=13layers=M The way added : http://www.openstreetmap.org/browse/way/4544322 The relation for this portion of France coasline : http://www.openstreetmap.org/browse/relation/1104125 The QA tool coastline checker doesn't work : http://wiki.openstreetmap.org/wiki/Coastline_error_checker OSM Inspector (Water) do not show unconnected coastline : http://tools.geofabrik.de/osmi/?view=waterlon=-0.68446lat=45.11871zo om=12opacity=0.73overlays=bodies_of_water,bodies_of_water,broken_bow,v map0_rivers,long_rivers,waterways_river,waterways_stream,waterways_drain ,waterways_canal,waterways_riverbank,waterways_other,waterways_width,wat erways_in_tunnels,waterways_on_bridges,waterways_without_names,waterway_ nodes,coastline,coastline,simple_islands,coastline_nodes,rivermouths,coa stline_not_simple,coastline_unconnected Can someone help me to fix this. -- Pierre-Alain Dorange OSM experiences : http://www.leretourdelautruche.com/map/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline updates
Hi! I have edited coastlines in Cornwall last summer and they are still not updated on the main map. (Easy to see because the border and coastline share the same location in the data but show up differently on the map.) The coastline error checker says: Last update of coastline errors: Wed Apr 14 13:19:17 UTC 2010 It also says it needs new hosting. I guess thats the problem. Can we get this going again? What exactly is needed? Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
- Original Message - From: Jochen Topf joc...@remote.org To: OSM Talk talk@openstreetmap.org Sent: Friday, February 25, 2011 4:03 PM Subject: [OSM-talk] Coastline updates Hi! I have edited coastlines in Cornwall last summer and they are still not updated on the main map. (Easy to see because the border and coastline share the same location in the data but show up differently on the map.) The coastline error checker says: Last update of coastline errors: Wed Apr 14 13:19:17 UTC 2010 It also says it needs new hosting. I guess thats the problem. Can we get this going again? What exactly is needed? The error checker hasn't been working for a long time, but I'm sure that coastline edits I made in January have since shown up on the map David Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
- Original Message - From: Jochen Topf joc...@remote.org To: OSM Talk talk@openstreetmap.org Sent: Friday, February 25, 2011 4:03 PM Subject: [OSM-talk] Coastline updates Hi! I have edited coastlines in Cornwall last summer and they are still not updated on the main map. (Easy to see because the border and coastline share the same location in the data but show up differently on the map.) Can you gave an example location? David The coastline error checker says: Last update of coastline errors: Wed Apr 14 13:19:17 UTC 2010 It also says it needs new hosting. I guess thats the problem. Can we get this going again? What exactly is needed? Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Fri, 25 Feb 2011 17:39:46 -, David Groom wrote: I have edited coastlines in Cornwall last summer and they are still not updated on the main map. (Easy to see because the border and coastline share the same location in the data but show up differently on the map.) Can you gave an example location? Same problem here: http://osm.org/go/xZHqTlPn http://www.openstreetmap.org/browse/way/33900429 The shape was changed in January, the other revisions are for added nodes (slipways or other similar things). -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
Is there any reason to still have the NPE layer accessible from the editors. It was useful in the pre-OS/Bing days but seems like a liability now? Kevin On 25 February 2011 17:47, Ed Loach e...@loach.me.uk wrote: I have edited coastlines in Cornwall last summer and they are still not updated on the main map. (Easy to see because the border and coastline share the same location in the data but show up differently on the map.) Can you gave an example location? I had a quick look around the coastline, but the first couple of discrepancies I found are recent edits (one was 6th February, the other in January http://www.openstreetmap.org/browse/way/95126825 - this one I found interesting as the coastline that was based on the boundary has been updated to NPE which is over 50 years old) Ed ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
- Original Message - From: David Paleino da...@debian.org To: talk@openstreetmap.org Sent: Friday, February 25, 2011 5:57 PM Subject: Re: [OSM-talk] Coastline updates David the way you refer to was last edited on 1 Feb 2011, I would not necessarily expect to see the results of those changes reflected yet in the coastline on the Mapnik layer. see http://wiki.openstreetmap.org/wiki/Coastline#Main_Mapnik_layer David ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Fri, 25 Feb 2011 18:35:41 -, David Groom wrote: David the way you refer to was last edited on 1 Feb 2011, [..] You probably haven't read my whole message :) The last changes are just added nodes, there is no change in the shape of the coastline. The last changes in shape happened in January. David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
Hi! Falmouth: http://www.openstreetmap.org/?lat=50.15364lon=-5.0639zoom=17layers=M Looks ok now in this zoom level. Still some errors if you zoom in. I had a look at it again and marked some tile manually as dirty and I get the correct rendering then. So the problem seems not to be the coastline stuff but that there are tiles that haven't been re-rendered for half a year!? Jochen On Fri, Feb 25, 2011 at 05:39:46PM -, David Groom wrote: Date: Fri, 25 Feb 2011 17:39:46 - From: David Groom revi...@pacific-rim.net To: OSM Talk talk@openstreetmap.org Subject: Re: [OSM-talk] Coastline updates - Original Message - From: Jochen Topf joc...@remote.org To: OSM Talk talk@openstreetmap.org Sent: Friday, February 25, 2011 4:03 PM Subject: [OSM-talk] Coastline updates Hi! I have edited coastlines in Cornwall last summer and they are still not updated on the main map. (Easy to see because the border and coastline share the same location in the data but show up differently on the map.) Can you gave an example location? David The coastline error checker says: Last update of coastline errors: Wed Apr 14 13:19:17 UTC 2010 It also says it needs new hosting. I guess thats the problem. Can we get this going again? What exactly is needed? Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Fri, 2011-02-25 at 20:01 +0100, Jochen Topf wrote: Hi! Falmouth: http://www.openstreetmap.org/?lat=50.15364lon=-5.0639zoom=17layers=M Looks ok now in this zoom level. Still some errors if you zoom in. I had a look at it again and marked some tile manually as dirty and I get the correct rendering then. So the problem seems not to be the coastline stuff but that there are tiles that haven't been re-rendered for half a year!? I updated the coastline shapefiles used by the mapnik layer last night. The previous update was about 4 weeks ago. If no one edits any data in an area after the coastline shapefiles are changed then it may be a long time before the tiles are rendered again to pick up the changes (as you are seeing here). Normally I force the zoom 0 - 12 tiles to re-render across the world each time I update the coastline shapefiles but it takes too long to do all zoom levels on each update. Back in January I ran a process to re-rendered all tiles last rendered prior to 1st Oct 2010 across the full 0-18 zoom range. This took a few weeks to complete and should have picked you older changes. I will consider running it again with a more recent cut-off point. Perhaps some of the other discrepancies are due to newer edits to the coastlines? Jon ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On 25-2-2011 17:03, Jochen Topf wrote: The coastline error checker says: Last update of coastline errors: Wed Apr 14 13:19:17 UTC 2010 It also says it needs new hosting. I guess thats the problem. The osm.org tile server generates its own coastline shapefiles. It doesn't use the ones from the coastline error checker. FWIW: curl --head http://tile.openstreetmap.org/processed_p.tar.bz2 Last-Modified: Fri, 25 Feb 2011 09:24:39 GMT curl --head http://tile.openstreetmap.org/shoreline_300.tar.bz2 Last-Modified: Fri, 25 Feb 2011 09:22:31 GMT I don't know if the caching influences these dates. Can we get this going again? What exactly is needed? A server with sufficient storage and bandwidth to process a weekly planet, daily diffs, and many hours of single task processing per coastline run. -- Lennard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On Fri, Feb 25, 2011 at 09:24:19PM +0100, Lennard wrote: Can we get this going again? What exactly is needed? A server with sufficient storage and bandwidth to process a weekly planet, daily diffs, and many hours of single task processing per coastline run. We have a server that has planet file kept current each day for Taginfo. Maybe it can do the coastline check, too. It only has PBF files, though which the coastline checker doesn't understand. But we could work around that or change it. Storage should also not be a problem, but RAM could be. The machine has only 16 GB. Anybody know how much RAM the coastline checker needs? Jochen -- Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline updates
On 25-2-2011 22:02, Jochen Topf wrote: We have a server that has planet file kept current each day for Taginfo. Maybe it can do the coastline check, too. It only has PBF files, though which the coastline checker doesn't understand. But we could work around that or change it. Storage should also not be a problem, but RAM could be. The machine has only 16 GB. Anybody know how much RAM the coastline checker needs? The first stage of the coastline checker tool chain is a modified copy of an old revision of osm2pgsql. It could be adapted for pbf, same as the current osm2pgsql. It does two passes over the data, that's why a simple pbf2osm pipe doesn't work. The rest of the tool chain works on the resulting interim files, and wouldn't need to be adapted for a pbf planet. 16GB should be plenty. Last year I could still do a complete coastline run with a 4GB server, and it probably needs less than that. -- Lennard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline in mapnik
A stupid but working workaround is to go through the .osm file with sed or something and rename coastline to something else before running osm2pgsql. And the more logical solution would be to find the single line in the osm2pgsql code that drops natural=coastline, adapt that, and recompile/reimport. Also remove the natural=coastline 'delete' keyword from default.style. You'll then have the raw natural=coastline ways in planet_osm_line, and you can create a mapnik rule for those. -- Lennard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline in mapnik
On Nov 9, 2010, at 12:30 AM, Lennard wrote: A stupid but working workaround is to go through the .osm file with sed or something and rename coastline to something else before running osm2pgsql. And the more logical solution would be to find the single line in the osm2pgsql code that drops natural=coastline, adapt that, and recompile/reimport. Also remove the natural=coastline 'delete' keyword from default.style. You'll then have the raw natural=coastline ways in planet_osm_line, and you can create a mapnik rule for those. Both of these workarounds will get me a personally useful file, but neither is appropriate for situations where I'm setting up rendering styles for clients or other people and need to help them help themselves. Where would I put in a formal request that those lines be deleted from the osm2pgsql code, or submit a patch? The instructions here suggest that Trac is the right place, but I seem to need a Trac login to file a report: http://wiki.openstreetmap.org/wiki/Osm2pgsql#Bug_reports Jon Burgess is helping me off-list with some interesting intermediate files from the processor that he linked to in a previous mail. I'm interested in seeing those made available at the official URL, http://hypercube.telascience.org/~kleptog/. -mike. michal migurski- m...@stamen.com 415.558.1610 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline in mapnik
On Sun, 2010-11-07 at 23:29 -0800, Michal Migurski wrote: I think we went back to some older shapefiles after reports of a significant problem with one of more recent updates. I just updated the files with coastlines generated from the planet file this week. Thank you Jon! Can I ask if it would be possible to include in those shapefiles a processed coastline that's just the outlines, rather than the tiled land area polygon? osm2pgsql doesn't import natural=coastline (a hardcoded exception) and sometimes it's useful to put lines on coastlines, for which the processed_p data isn't very well suited. There are three intermediate shapefiles produced by the coastcheck utility: # coastline_p - points with errors http://yevaud.openstreetmap.org/coastline_p.tar.bz2 # coastline_i - incomplete sections of coastline http://yevaud.openstreetmap.org/coastline_i.tar.bz2 # coastline_c - complete sections http://yevaud.openstreetmap.org/coastline_c.tar.bz2 They are the input to last step of the processing which creates the closed polygons for each tile in the final 'processed_p' output. At no point is there a file which has fully closed polygons without the tiling. Jon ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline in mapnik
On Nov 8, 2010, at 2:34 PM, Jon Burgess wrote: On Sun, 2010-11-07 at 23:29 -0800, Michal Migurski wrote: I think we went back to some older shapefiles after reports of a significant problem with one of more recent updates. I just updated the files with coastlines generated from the planet file this week. Thank you Jon! Can I ask if it would be possible to include in those shapefiles a processed coastline that's just the outlines, rather than the tiled land area polygon? osm2pgsql doesn't import natural=coastline (a hardcoded exception) and sometimes it's useful to put lines on coastlines, for which the processed_p data isn't very well suited. There are three intermediate shapefiles produced by the coastcheck utility: # coastline_p - points with errors http://yevaud.openstreetmap.org/coastline_p.tar.bz2 # coastline_i - incomplete sections of coastline http://yevaud.openstreetmap.org/coastline_i.tar.bz2 # coastline_c - complete sections http://yevaud.openstreetmap.org/coastline_c.tar.bz2 They are the input to last step of the processing which creates the closed polygons for each tile in the final 'processed_p' output. At no point is there a file which has fully closed polygons without the tiling. I'm not actually looking for closed polygons - quite the opposite. The closest thing from what you describe is coastline_i, or maybe coastline_c. In theory this should be equivalent to just getting the raw ways out of OSM, but osm2pgsql prevents this. Would it be possible to make coastline_i available? -mike. michal migurski- m...@stamen.com 415.558.1610 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline in mapnik
On Sun, 2010-11-07 at 01:05 +0100, Vladimir Vyskocil wrote: I checked the shoreline last modification date with : wget --server-response --spider http://tile.openstreetmap.org/shoreline_300.tar.bz2 and the answer show : Last-Modified: Fri, 24 Sep 2010 23:44:09 GMT It's about 1 month and half ago !! Is this process broken ? Vlad. I think we went back to some older shapefiles after reports of a significant problem with one of more recent updates. I just updated the files with coastlines generated from the planet file this week. Jon ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline in mapnik
On Nov 7, 2010, at 3:57 PM, Jon Burgess wrote: On Sun, 2010-11-07 at 01:05 +0100, Vladimir Vyskocil wrote: I checked the shoreline last modification date with : wget --server-response --spider http://tile.openstreetmap.org/shoreline_300.tar.bz2 and the answer show : Last-Modified: Fri, 24 Sep 2010 23:44:09 GMT It's about 1 month and half ago !! Is this process broken ? Vlad. I think we went back to some older shapefiles after reports of a significant problem with one of more recent updates. I just updated the files with coastlines generated from the planet file this week. Thank you Jon! Can I ask if it would be possible to include in those shapefiles a processed coastline that's just the outlines, rather than the tiled land area polygon? osm2pgsql doesn't import natural=coastline (a hardcoded exception) and sometimes it's useful to put lines on coastlines, for which the processed_p data isn't very well suited. -mike. michal migurski- m...@stamen.com 415.558.1610 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline in mapnik
I checked the shoreline last modification date with : wget --server-response --spider http://tile.openstreetmap.org/shoreline_300.tar.bz2 and the answer show : Last-Modified: Fri, 24 Sep 2010 23:44:09 GMT It's about 1 month and half ago !! Is this process broken ? Vlad. On 5 nov. 2010, at 19:40, Richard Weait wrote: On Fri, Nov 5, 2010 at 2:07 PM, Ulf Mehlig ulf.meh...@gmx.net wrote: I'm waiting for my last week's coastline changes to become visible on the main site's mapnik layer: http://www.openstreetmap.org/?lat=-0.7596lon=-47.049zoom=12layers=M I tried to avoid caching problems, and I triggered re-rendering of the affected tiles by tagging them as dirty ... Osmarender shows the coastline correctly. Does anybody know how to proceed? Hi Ulf, This question is asked fairly often and is very ably answered on the help site. In short, coastline rendering is a relatively expensive process which is run only a few times per month. Details here: http://help.openstreetmap.org/questions/276/why-do-the-changes-i-have-made-to-coastline-not-appear-on-the-map ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] coastline in mapnik
I'm waiting for my last week's coastline changes to become visible on the main site's mapnik layer: http://www.openstreetmap.org/?lat=-0.7596lon=-47.049zoom=12layers=M I tried to avoid caching problems, and I triggered re-rendering of the affected tiles by tagging them as dirty ... Osmarender shows the coastline correctly. Does anybody know how to proceed? Thanks for your help, Ulf -- Ulf Mehlig ulf.meh...@gmx.net -- ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline in mapnik
On Fri, Nov 5, 2010 at 2:07 PM, Ulf Mehlig ulf.meh...@gmx.net wrote: I'm waiting for my last week's coastline changes to become visible on the main site's mapnik layer: http://www.openstreetmap.org/?lat=-0.7596lon=-47.049zoom=12layers=M I tried to avoid caching problems, and I triggered re-rendering of the affected tiles by tagging them as dirty ... Osmarender shows the coastline correctly. Does anybody know how to proceed? Hi Ulf, This question is asked fairly often and is very ably answered on the help site. In short, coastline rendering is a relatively expensive process which is run only a few times per month. Details here: http://help.openstreetmap.org/questions/276/why-do-the-changes-i-have-made-to-coastline-not-appear-on-the-map ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Coastline missing in Lake Superior - in case anyonenotices...
If you are going to delete many miles of coastline data, are you then going to take the responsibility for re-entering this data afterwards, to at least the same level of accuracy as the current data? It seems to me that it would be better to tell your editor program not to display the coastline during your editing session. After all, there are likely to be some people who want to render the coastline, and they won't be able to do so if you have deleted the data. ---Original Email--- Subject :[OSM-talk] Coastline missing in Lake Superior - in case anyonenotices... From :mailto:mi...@carterfamily.ca Date :Tue Aug 10 13:16:11 America/Chicago 2010 I'm currently working on importing CanVec data around Lake Superior... the coast line was really getting in the way, so I'm deleting it. I'm actually joining them to the CanVec water corners... but it's probably creating a coastal hole, not really sure if the join is actually working. My plan is to finish loading all the coastal areas with the canvec data. Then joining the big body of water with a single relation, on the Canadian side. That will become the new coastal waters object, when finished. On the USA side I'll just join the existing coastal waters object across the USA/Canada boarder. I should have the entire lake finished by the end of the week... I hope. I just wanted to post this in case it sent up red flags somewhere. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk -- John F. Eldredge -- j...@jfeldredge.com Reserve your right to think, for even to think wrongly is better than not to think at all. -- Hypatia of Alexandria ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Coastline missing in Lake Superior - in case anyonenotices...
Short answer yes, I'm taking responsibility! I've put in a temporary join on on the US side so it's a complete object while I fix up the Canadian side. At the rate I'm going I should be tomorrow. As for same level of accuracy... that's why I'm deleting it. ;) The coastline data is currently way way out of whack, there's an entire campground under water, chains of islands represented as a small square, and much more... CanVec isn't 100% accurate but it's about 200% more accurate than what's there now. The problem with ignoring the data is we get many duplicate objects and other problem in OSM after upload. (which, in the past, I've already been yelled at for) Since I'm dealing with an area that has about 90 CanVec 25k tiles there's no way to do it at once. So my solution was to just join the coastline to the canvec water grids as I go... In anycase... it will be completed soon, as long as I don't get too distracted replying to peoples e-mails ;-) If you are going to delete many miles of coastline data, are you then going to take the responsibility for re-entering this data afterwards, to at least the same level of accuracy as the current data? It seems to me that it would be better to tell your editor program not to display the coastline during your editing session. After all, there are likely to be some people who want to render the coastline, and they won't be able to do so if you have deleted the data. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [Talk-ca] [OSM-talk] Coastline missing in Lake Superior - in case anyone notices...
I'm perfectly fine killing the coastal tag from the Canadian side on all fresh water lakes... makes more sense to me. Plus it doesn't import very well into my Garmin GPS anyways... you end up pulling half the globe just to get the connecting lines, since it's not a single object. Michael On 10/08/10 02:52 PM, John Smith wrote: On 11 August 2010 04:51, Sam Vekemansacrosscanadatra...@gmail.com wrote: a 'lake' and 'shoreline' are 2 different map features. We don't get the sorts of levels of water as they do in North America so to me a shoreline is only along the sea shore... Where as bodies of fresh water are usually lakes (natural=water)... ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] [OSM-talk] Coastline missing in Lake Superior - in case anyone notices...
As Quick Draw McGraw would say, Whoa! Hold on there Pardners! Please don't just delete and replace a large international body of water without TONS of discussion with the affected community first. There is a very high likelihood that editing an object this large will break in the middle due to a timeout. That will make fixing it ever harder. And it will all take time which is almost certain to cause a ruckus, if the affected community is not involved before the problem occurs. This in not a race. There is no deadline or prize for changing inland seas fastest. Please reconsider this! ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [OSM-talk] coastline error checker
On Fri, 2010-06-04 at 14:42 -0300, Ulf Mehlig wrote: I've the impression that the coastline error checker is not working at the moment (last updated: 14th of April); coastline changes I've made some weeks ago in northern Brazil have not yet been applied to the openstreetmap.org mapnik layer. Is there anything one can do? I don't know about the coastcheck web site but the coastline shapefiles on the main mapnik layer have been updated several times since Apr 14th. The latest update was done from the planet file this Weds. Can you provide a map link to the exact area you modified? Jon ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline error checker
Am Samstag 05. Juni 2010 11:15:16 schrieb Jon Burgess: Can you provide a map link to the exact area you modified? Some weeks ago I fixed this coastline http://www.openstreetmap.org/?way=12193534 but is only in zoom level 14 right rendered, all other levels show the old version... Greetings, Carsten -- Hier ist mein öffentlicher GPG-Schlüssel: http://daswaldhorn.piranho.de/gpg.php = www.stopptdievorratsdatenspeicherung.de signature.asc Description: This is a digitally signed message part. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline error checker
Carsten Gerlach wrote: Am Samstag 05. Juni 2010 11:15:16 schrieb Jon Burgess: Can you provide a map link to the exact area you modified? Some weeks ago I fixed this coastline http://www.openstreetmap.org/?way=12193534 but is only in zoom level 14 right rendered, all other levels show the old version... It just needed to be forced to rerender. Zoom 16 17 look better around Plymouth now. Cheers, Chris ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline error checker
On Sat, 2010-06-05 at 20:30 +0100, Chris Hill wrote: Carsten Gerlach wrote: Am Samstag 05. Juni 2010 11:15:16 schrieb Jon Burgess: Can you provide a map link to the exact area you modified? Some weeks ago I fixed this coastline http://www.openstreetmap.org/?way=12193534 but is only in zoom level 14 right rendered, all other levels show the old version... It just needed to be forced to rerender. Zoom 16 17 look better around Plymouth now. Cheers, Chris Unfortunately the code which does the automatic tile invalidation does not work correctly for the coastline because it has no way to know when the shapefiles are going to be updated and which tiles they effect. The tiles either need to be marked manually or you have to wait until another edit in the area triggers them to render again. Jon ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] coastline error checker
I've the impression that the coastline error checker is not working at the moment (last updated: 14th of April); coastline changes I've made some weeks ago in northern Brazil have not yet been applied to the openstreetmap.org mapnik layer. Is there anything one can do? Thanks, Ulf -- Ulf Mehlig ulf.meh...@gmx.net -- ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
2010/3/6 osm easingwold osm.easingw...@hotmail.co.uk: http://www.openstreetmap.org/?lat=-36.90445lon=174.85045zoom=16layers=B000FTF The renderer is confused by having a park overlapping the sea and it's obviously getting the ordering wrong. Yes. And therefore the problem lies in the rendering rules, not the underlying data, that's why these should be modified, not the data. Actually I can think of no case where water should not be rendered above other nearby polygons. The only situations would be covered underground water bodies, which should be tagged with a layer-tag and probably some yet-to-come-underground-tag, so I think this issue can be solved. (Probably the suggestion to map the water explicitly above and tag it with natural water, tidal=yes is the best hack proposed till now, but of course remains unsatisfactory). You lose the fact that the basin itself is part of the park, but I'm not sure how important that is. IMHO it is important. cheers, Martin ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 6 March 2010 16:01, Apollinaris Schoell ascho...@gmail.com wrote: landuse? no, i didn't use that. i used leisure=park sure. ahh… our messy key,tag combinations for areas natural, landuse, leisure … and it's not a national park, only local council we still use it for parks if it's the type of parks protecting nature and add a admin_level similar to political boundary hierarchy key national_park is also documented that it can be used in a wider range of parks. yeah, i know. precisely why i don't get involved in these discussions/tag admin anymore. everyone's quite happy adding more and more tags to solve their little problem, with no consideration for how it affects the whole. so there are now three methods for tagging parks? good work that man! is it any surprise it's a horrible mess? /out ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 7 March 2010 13:55, Erik Johansson e...@kth.se wrote: Whoa, had a bad day? When things doesn't doesn't work like you want them to, it's not because the world is a horrible mess. no, not a bad day. previous bad experiences on osm around tagging: everyone's so concentrated on their own small problem, they ignore the bigger picture of what osm is/could be for anyway, back to mapping. gotta keep the stress levels down ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 5 March 2010 20:35, simon msr...@gmail.com wrote: In this case your park have to follow the coastline with the tham node (I have correct it to show you) unfortunately the water is part of the park If it was a park with water in the midle you have to use multipolygone relation http://wiki.openstreetmap.org/wiki/Multipolygon right, will do ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 5 March 2010 20:40, Apollinaris Schoell ascho...@gmail.com wrote: Don't use coastline but tag the basin with natural water or any other water type tags like riverbank … hmm, well if we can ignore for a moment the abomination of inconsistency that is water tagging in general and natural=water specifically, then no: the basin is tidal, so it's coastline coastline is also sensitive to direction while water has to be a closed polygon only, direction doesn't matter yes ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 5 March 2010 20:39, John Smith deltafoxtrot...@gmail.com wrote: On 5 March 2010 17:17, Robin Paulson robin.paul...@gmail.com wrote: i've recently mapped a park which contains a basin. when the tiles render, the whole area, including the water, renders green. how would i tag this so the renderer understands the water bit should be treated as water, and rendered blue? The tiles just needed to be marked dirty so they regenerated, try viewing it now. they'd already rendered, but now someone else has drawn it incorrectly. i'll revert, use a polygon relation, and re-render ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
2010/3/5 Robin Paulson robin.paul...@gmail.com: they'd already rendered, but now someone else has drawn it incorrectly. i'll revert, use a polygon relation, and re-render haven't you stated above that the water is part of the park? The multipolygon-relation will exclude the inner from the outer, so IMHO this is not your desired solution... cheers, Martin ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] coastline within a park
I have a related question, which I've let sit for several months hoping to find an answer for. There is a park here http://www.openstreetmap.org/?lat=27.8394lon=-82.5924zoom=14layers=B000FTF that includes wetland islands, wetland mainland, and dry mainland. Initially I could not get any of it to render as park. Somehow I eventually dumbed into something that renders the wetland islands as park, but it required deleting the islands and retracing them--not sure why. Anyway, I don't want to have to retrace the mainland wetland coastline to do this, and I also need to connect that with the dry mainland section. The entire wetland mainland area in the view is part of the park, and I know from visits to the area where the northern boundaries for the dry areas are. Can someone advise how to do this? I've stayed away from doing any further work on the local coastline until I figure this out. Ed Hillsman Date: Fri, 5 Mar 2010 13:41:57 +0100 From: Martin Koppenhoefer dieterdre...@gmail.com Subject: Re: [OSM-talk] coastline within a park To: Robin Paulson robin.paul...@gmail.com Cc: OSM Talk talk@openstreetmap.org Message-ID: 7acdb3651003050441y1a38e833nffead252ca2a4...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 2010/3/5 Robin Paulson robin.paul...@gmail.com: they'd already rendered, but now someone else has drawn it incorrectly. i'll revert, use a polygon relation, and re-render haven't you stated above that the water is part of the park? The multipolygon-relation will exclude the inner from the outer, so IMHO this is not your desired solution... cheers, Martin -- ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk End of talk Digest, Vol 67, Issue 16 ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
Hillsman, Edward hills...@cutr.usf.edu writes: I have a related question, which I've let sit for several months hoping to find an answer for. There is a park here http://www.openstreetmap.org/?lat=27.8394lon=-82.5924zoom=14layers=B000FTF that includes wetland islands, wetland mainland, and dry mainland. Initially I could not get any of it to render as park. Somehow I eventually dumbed into something that renders the wetland islands as park, but it required deleting the islands and retracing them--not sure why. Anyway, I don't want to have to retrace the mainland wetland coastline to do this, and I also need to connect that with the dry mainland section. The entire wetland mainland area in the view is part of the park, and I know from visits to the area where the northern boundaries for the dry areas are. Can someone advise how to do this? I've stayed away from doing any further work on the local coastline until I figure this out. coastline and park should be entirely separate conceptually. Tag it how it is, and if it doesn't render how you think it should look into the rendering rules. Contorting the tagging to make the current rendering incarnation work right seems like not a good plan. I suspect the rendering folks would be interested in a fix; I can easily see this being a case not envisioned and not handled. pgpl39gQi0EFD.pgp Description: PGP signature ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On a related issue, since a way that forms a closed loop is interpreted as the boundary of an area rather than as a way, how does one map a road or trail that forms a closed loop? --Original Message-- From: Robin Paulson Sender: talk-boun...@openstreetmap.org To: OpenStreetMap talk mailing list Subject: [OSM-talk] coastline within a park Sent: Mar 5, 2010 1:17 AM i'm after some advice. i know this is potentially tagging for the renderer, but still i've recently mapped a park which contains a basin. when the tiles render, the whole area, including the water, renders green. how would i tag this so the renderer understands the water bit should be treated as water, and rendered blue? cheers http://www.openstreetmap.org/?lat=-36.90445lon=174.85045zoom=16layers=B000FTF ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk -- John F. Eldredge -- j...@jfeldredge.com Reserve your right to think, for even to think wrongly is better than not to think at all. -- Hypatia of Alexandria ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
John F. Eldredge wrote: On a related issue, since a way that forms a closed loop is interpreted as the boundary of an area rather than as a way, how does one map a road or trail that forms a closed loop? It depends on the context. A closed loop tagged with a highway tag is just a closed highway. Roundabouts are often simple closed loops, but render as a ring not an area. There are exceptions of course (it wouldn't be OSM without them :-)) If you want to draw a piazza draw the closed outline with highway=pedestrian which would normally render as a closed loop, but if you add area=yes the whole space is rendered as a filled piazza. Cheers, Chris ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 5 Mar 2010, at 24:29 , Robin Paulson wrote: On 5 March 2010 20:40, Apollinaris Schoell ascho...@gmail.com wrote: Don't use coastline but tag the basin with natural water or any other water type tags like riverbank … hmm, well if we can ignore for a moment the abomination of inconsistency that is water tagging in general and natural=water specifically, then no: the basin is tidal, so it's coastline Didn't see when zoomed in to your view. clear now from low zoom. you can hack it but that is dirty tagging for the renderer. Osmarender: add layer=-1 to the park Mapnik: add a water polygon and this will render on top of all other area features. If you consider micro mapping in future it's probably better not to use the landuse at all instead add a boundary national_park to render the boundary itself and have landuse polygons for wood,meadow,… for the details coastline is also sensitive to direction while water has to be a closed polygon only, direction doesn't matter yes ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 6 March 2010 01:41, Martin Koppenhoefer dieterdre...@gmail.com wrote: haven't you stated above that the water is part of the park? The multipolygon-relation will exclude the inner from the outer, so IMHO this is not your desired solution... ah, yes. good point. i hadn't understood it fully, thanks for pointing that out ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 6 March 2010 06:23, Apollinaris Schoell ascho...@gmail.com wrote: Didn't see when zoomed in to your view. clear now from low zoom. you can hack it but that is dirty tagging for the renderer. it is indeed. i'll leave it as is, and come up with some bullshit for when a casual map user asks why panmure basin is coloured green Osmarender: add layer=-1 to the park Mapnik: add a water polygon and this will render on top of all other area features. ugh, that's horrible. If you consider micro mapping in future it's probably better not to use the landuse at all instead add a boundary national_park to render the boundary itself and have landuse polygons for wood,meadow,… for the details landuse? no, i didn't use that. i used leisure=park and it's not a national park, only local council ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 5 Mar 2010, at 13:41 , Robin Paulson wrote: landuse? no, i didn't use that. i used leisure=park sure. ahh… our messy key,tag combinations for areas natural, landuse, leisure … and it's not a national park, only local council we still use it for parks if it's the type of parks protecting nature and add a admin_level similar to political boundary hierarchy key national_park is also documented that it can be used in a wider range of parks. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] coastline within a park
i'm after some advice. i know this is potentially tagging for the renderer, but still i've recently mapped a park which contains a basin. when the tiles render, the whole area, including the water, renders green. how would i tag this so the renderer understands the water bit should be treated as water, and rendered blue? cheers http://www.openstreetmap.org/?lat=-36.90445lon=174.85045zoom=16layers=B000FTF ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
On 5 March 2010 17:17, Robin Paulson robin.paul...@gmail.com wrote: i've recently mapped a park which contains a basin. when the tiles render, the whole area, including the water, renders green. how would i tag this so the renderer understands the water bit should be treated as water, and rendered blue? The tiles just needed to be marked dirty so they regenerated, try viewing it now. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline within a park
Don't use coastline but tag the basin with natural water or any other water type tags like riverbank … coastline is also sensitive to direction while water has to be a closed polygon only, direction doesn't matter On 4 Mar 2010, at 23:17 , Robin Paulson wrote: i'm after some advice. i know this is potentially tagging for the renderer, but still i've recently mapped a park which contains a basin. when the tiles render, the whole area, including the water, renders green. how would i tag this so the renderer understands the water bit should be treated as water, and rendered blue? cheers http://www.openstreetmap.org/?lat=-36.90445lon=174.85045zoom=16layers=B000FTF ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline error checker stalled
Interesting, hadn't noticed. I'll see if I can work out what's happening. Have a nice day, On Tue, Jan 19, 2010 at 11:29 PM, Lennard l...@xs4all.nl wrote: David Groom wrote: The date of the last update of the coastline error checker is shown as 27 Dec 2009. That was what I found when looking for new coastline shapefiles for the Haiti map. I'm now running the coastline checker for myself to get new shapefiles. Cc'ing Martijn van Oosterhout, as he's the author of the coastline error checker. -- Lennard -- Martijn van Oosterhout klep...@gmail.com http://svana.org/kleptog/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline error checker stalled
Martijn van Oosterhout wrote: Interesting, hadn't noticed. I'll see if I can work out what's happening. Increase 600M to 700M and you're set for another few months. Also, the MAX_NODES_PER_WAY can now be dropped from 12000 to 2000, now that no 2000+ node ways are left in OSM, and none can be created. Unless avar finds a way around that too, actually. :) -- Lennard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] coastline error checker stalled
Hmm, ok. I've done than we'll see if it helps. Thanks, On Wed, Jan 20, 2010 at 1:48 PM, Lennard l...@xs4all.nl wrote: Martijn van Oosterhout wrote: Interesting, hadn't noticed. I'll see if I can work out what's happening. Increase 600M to 700M and you're set for another few months. Also, the MAX_NODES_PER_WAY can now be dropped from 12000 to 2000, now that no 2000+ node ways are left in OSM, and none can be created. Unless avar finds a way around that too, actually. :) -- Lennard -- Martijn van Oosterhout klep...@gmail.com http://svana.org/kleptog/ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
