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
