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
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
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
