From thomas.schaap at utas.edu.au Tue Feb 18 12:07:51 2020 From: thomas.schaap at utas.edu.au (Thomas Schaap) Date: Tue, 18 Feb 2020 01:07:51 +0000 Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters Message-ID: Hi everyone, I am trying to export a high-resolution (0.0005 degree cellsize) numerical raster which I have reconstructed using GPlates. I would ideally like to keep this resolution, but the GPlates console gives me this: ERROR 2: Cannot allocate 1036800000000 bytes on this platform. [Warning] Unable to create in-memory dataset for writing rasters. Now please correct me if I misunderstand what's going on here, but the original TIF file was only 43 megabytes, yet GPlates is asking for 1 terabyte of memory? The lowest cellsize I have been allowed to export is 0.01 degrees. Is there something I am misunderstanding about the raster export process? Is there some way around this? Thanks in advance! Tom Thomas Schaap PhD Candidate | Casual Academic Staff CODES | Earth Sciences | Rm. 460 School of Natural Sciences University of Tasmania [cid:61edcbe5-98cd-4e87-bdbb-923fb84c13bf] University of Tasmania Electronic Communications Policy (December, 2014). This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-dco5vyy1.gif Type: image/gif Size: 7449 bytes Desc: Outlook-dco5vyy1.gif URL: From john.cannon at sydney.edu.au Wed Feb 19 11:53:36 2020 From: john.cannon at sydney.edu.au (John Cannon) Date: Wed, 19 Feb 2020 00:53:36 +0000 Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters In-Reply-To: References: Message-ID: Hi Tom, Wow, that's a big raster! I'm surprised GPlates didn't trip up reconstructing that. When exporting rasters we currently pass raster data to the image drivers as a single 'uncompressed' memory buffer. Hence the terabyte. Whereas the original tiff is highly compressed. Maybe with some of the 'tiled' image formats we could export differently in GPlates in the future, but that would involve some rearranging of things and would be quite low priority. The 0.01 degree you successfully exported is near the 32-bit limit. You might be able to go higher with a 64-bit Windows build (assuming you're using a 32-bit build; Mac and Linux are already 64-bit). Regards, John Sent while away from keyboard ________________________________ From: GPlates-discuss on behalf of Thomas Schaap Sent: Tuesday, 18 February 2020, 9:08 am To: GPlates general discussion mailing list Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi everyone, I am trying to export a high-resolution (0.0005 degree cellsize) numerical raster which I have reconstructed using GPlates. I would ideally like to keep this resolution, but the GPlates console gives me this: ERROR 2: Cannot allocate 1036800000000 bytes on this platform. [Warning] Unable to create in-memory dataset for writing rasters. Now please correct me if I misunderstand what's going on here, but the original TIF file was only 43 megabytes, yet GPlates is asking for 1 terabyte of memory? The lowest cellsize I have been allowed to export is 0.01 degrees. Is there something I am misunderstanding about the raster export process? Is there some way around this? Thanks in advance! Tom Thomas Schaap PhD Candidate | Casual Academic Staff CODES | Earth Sciences | Rm. 460 School of Natural Sciences University of Tasmania [cid:61edcbe5-98cd-4e87-bdbb-923fb84c13bf] University of Tasmania Electronic Communications Policy (December, 2014). This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-dco5vyy1.gif Type: image/gif Size: 7449 bytes Desc: Outlook-dco5vyy1.gif URL: From michael.chin at sydney.edu.au Wed Feb 19 13:24:42 2020 From: michael.chin at sydney.edu.au (Michael Chin) Date: Wed, 19 Feb 2020 02:24:42 +0000 Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters In-Reply-To: References: , Message-ID: Hi Tom, Could you please double check the resolution of your original raster? If the tif file is only 43M, it is unlikely the resolution can be so high as 0.0005 degree, which is a 720000x360000 raster, unless the raster contains very sparse data. If the resolution of the original raster is not that high, it is not necessary to export it as 0.0005 degree. The export can only be as good as the original one. ________________________________ From: GPlates-discuss on behalf of John Cannon Sent: Wednesday, 19 February 2020 11:53 AM To: GPlates general discussion mailing list Subject: Re: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi Tom, Wow, that's a big raster! I'm surprised GPlates didn't trip up reconstructing that. When exporting rasters we currently pass raster data to the image drivers as a single 'uncompressed' memory buffer. Hence the terabyte. Whereas the original tiff is highly compressed. Maybe with some of the 'tiled' image formats we could export differently in GPlates in the future, but that would involve some rearranging of things and would be quite low priority. The 0.01 degree you successfully exported is near the 32-bit limit. You might be able to go higher with a 64-bit Windows build (assuming you're using a 32-bit build; Mac and Linux are already 64-bit). Regards, John Sent while away from keyboard ________________________________ From: GPlates-discuss on behalf of Thomas Schaap Sent: Tuesday, 18 February 2020, 9:08 am To: GPlates general discussion mailing list Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi everyone, I am trying to export a high-resolution (0.0005 degree cellsize) numerical raster which I have reconstructed using GPlates. I would ideally like to keep this resolution, but the GPlates console gives me this: ERROR 2: Cannot allocate 1036800000000 bytes on this platform. [Warning] Unable to create in-memory dataset for writing rasters. Now please correct me if I misunderstand what's going on here, but the original TIF file was only 43 megabytes, yet GPlates is asking for 1 terabyte of memory? The lowest cellsize I have been allowed to export is 0.01 degrees. Is there something I am misunderstanding about the raster export process? Is there some way around this? Thanks in advance! Tom Thomas Schaap PhD Candidate | Casual Academic Staff CODES | Earth Sciences | Rm. 460 School of Natural Sciences University of Tasmania [cid:61edcbe5-98cd-4e87-bdbb-923fb84c13bf] University of Tasmania Electronic Communications Policy (December, 2014). This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-dco5vyy1.gif Type: image/gif Size: 7449 bytes Desc: Outlook-dco5vyy1.gif URL: From thomas.schaap at utas.edu.au Wed Feb 19 13:55:26 2020 From: thomas.schaap at utas.edu.au (Thomas Schaap) Date: Wed, 19 Feb 2020 02:55:26 +0000 Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters In-Reply-To: References: , , Message-ID: Hi again, Thank you for your inputs. As always when I ask for help on these problems I found that I hadn't been doing it properly. I wasn't properly setting the exported region (it's not a global dataset). This significantly cut down the size of the export to the point where GPlates will now allow me to export the data at its original resolution. The trouble I'm having now is that the exported raster looks to contain only certain parts of the data, as if the export process has cut the raster into segments and then left some of them out. It's hard to describe so I've attached a screenshot to describe what I'm talking about. The grayscale area is the reconstructed raster I'm trying to export as displayed in GPlates, and the green areas are the exported raster when I import it back in (it's the same result when I look at it in other GIS packages). This doesn't happen for lower resolution exports. Has anyone seen this behaviour before? Any advice? Thanks, Tom Thomas Schaap PhD Candidate | Casual Academic Staff CODES | Earth Sciences | Rm. 460 School of Natural Sciences University of Tasmania [cid:f7f6a15c-069a-473e-aa7f-9f4af8f99027] ________________________________ From: GPlates-discuss on behalf of Michael Chin Sent: 19 February 2020 13:24 To: John Cannon ; GPlates general discussion mailing list Subject: Re: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi Tom, Could you please double check the resolution of your original raster? If the tif file is only 43M, it is unlikely the resolution can be so high as 0.0005 degree, which is a 720000x360000 raster, unless the raster contains very sparse data. If the resolution of the original raster is not that high, it is not necessary to export it as 0.0005 degree. The export can only be as good as the original one. ________________________________ From: GPlates-discuss on behalf of John Cannon Sent: Wednesday, 19 February 2020 11:53 AM To: GPlates general discussion mailing list Subject: Re: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi Tom, Wow, that's a big raster! I'm surprised GPlates didn't trip up reconstructing that. When exporting rasters we currently pass raster data to the image drivers as a single 'uncompressed' memory buffer. Hence the terabyte. Whereas the original tiff is highly compressed. Maybe with some of the 'tiled' image formats we could export differently in GPlates in the future, but that would involve some rearranging of things and would be quite low priority. The 0.01 degree you successfully exported is near the 32-bit limit. You might be able to go higher with a 64-bit Windows build (assuming you're using a 32-bit build; Mac and Linux are already 64-bit). Regards, John Sent while away from keyboard ________________________________ From: GPlates-discuss on behalf of Thomas Schaap Sent: Tuesday, 18 February 2020, 9:08 am To: GPlates general discussion mailing list Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi everyone, I am trying to export a high-resolution (0.0005 degree cellsize) numerical raster which I have reconstructed using GPlates. I would ideally like to keep this resolution, but the GPlates console gives me this: ERROR 2: Cannot allocate 1036800000000 bytes on this platform. [Warning] Unable to create in-memory dataset for writing rasters. Now please correct me if I misunderstand what's going on here, but the original TIF file was only 43 megabytes, yet GPlates is asking for 1 terabyte of memory? The lowest cellsize I have been allowed to export is 0.01 degrees. Is there something I am misunderstanding about the raster export process? Is there some way around this? Thanks in advance! Tom Thomas Schaap PhD Candidate | Casual Academic Staff CODES | Earth Sciences | Rm. 460 School of Natural Sciences University of Tasmania [cid:61edcbe5-98cd-4e87-bdbb-923fb84c13bf] University of Tasmania Electronic Communications Policy (December, 2014). This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-dco5vyy1.gif Type: image/gif Size: 7449 bytes Desc: Outlook-dco5vyy1.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-0bxoziaj.gif Type: image/gif Size: 7449 bytes Desc: Outlook-0bxoziaj.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Gplates_raster.PNG Type: image/png Size: 20022 bytes Desc: Gplates_raster.PNG URL: From john.cannon at sydney.edu.au Thu Feb 20 20:15:28 2020 From: john.cannon at sydney.edu.au (John Cannon) Date: Thu, 20 Feb 2020 09:15:28 +0000 Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters In-Reply-To: References: , , , Message-ID: Might be graphics driver related. Can you send me a repro privately (the original raster, export bounds, etc; and your OS version and graphics card model)? I can look into it next week when back from hols, just to be sure it's not a GPlates bug. Sent while away from keyboard ________________________________ From: Thomas Schaap Sent: Wednesday, 19 February 2020, 10:55 am To: John Cannon; GPlates general discussion mailing list Subject: Re: Exporting high-resolution reconstructed rasters Hi again, Thank you for your inputs. As always when I ask for help on these problems I found that I hadn't been doing it properly. I wasn't properly setting the exported region (it's not a global dataset). This significantly cut down the size of the export to the point where GPlates will now allow me to export the data at its original resolution. The trouble I'm having now is that the exported raster looks to contain only certain parts of the data, as if the export process has cut the raster into segments and then left some of them out. It's hard to describe so I've attached a screenshot to describe what I'm talking about. The grayscale area is the reconstructed raster I'm trying to export as displayed in GPlates, and the green areas are the exported raster when I import it back in (it's the same result when I look at it in other GIS packages). This doesn't happen for lower resolution exports. Has anyone seen this behaviour before? Any advice? Thanks, Tom Thomas Schaap PhD Candidate | Casual Academic Staff CODES | Earth Sciences | Rm. 460 School of Natural Sciences University of Tasmania [cid:f7f6a15c-069a-473e-aa7f-9f4af8f99027] ________________________________ From: GPlates-discuss on behalf of Michael Chin Sent: 19 February 2020 13:24 To: John Cannon ; GPlates general discussion mailing list Subject: Re: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi Tom, Could you please double check the resolution of your original raster? If the tif file is only 43M, it is unlikely the resolution can be so high as 0.0005 degree, which is a 720000x360000 raster, unless the raster contains very sparse data. If the resolution of the original raster is not that high, it is not necessary to export it as 0.0005 degree. The export can only be as good as the original one. ________________________________ From: GPlates-discuss on behalf of John Cannon Sent: Wednesday, 19 February 2020 11:53 AM To: GPlates general discussion mailing list Subject: Re: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi Tom, Wow, that's a big raster! I'm surprised GPlates didn't trip up reconstructing that. When exporting rasters we currently pass raster data to the image drivers as a single 'uncompressed' memory buffer. Hence the terabyte. Whereas the original tiff is highly compressed. Maybe with some of the 'tiled' image formats we could export differently in GPlates in the future, but that would involve some rearranging of things and would be quite low priority. The 0.01 degree you successfully exported is near the 32-bit limit. You might be able to go higher with a 64-bit Windows build (assuming you're using a 32-bit build; Mac and Linux are already 64-bit). Regards, John Sent while away from keyboard ________________________________ From: GPlates-discuss on behalf of Thomas Schaap Sent: Tuesday, 18 February 2020, 9:08 am To: GPlates general discussion mailing list Subject: [GPlates-discuss] Exporting high-resolution reconstructed rasters Hi everyone, I am trying to export a high-resolution (0.0005 degree cellsize) numerical raster which I have reconstructed using GPlates. I would ideally like to keep this resolution, but the GPlates console gives me this: ERROR 2: Cannot allocate 1036800000000 bytes on this platform. [Warning] Unable to create in-memory dataset for writing rasters. Now please correct me if I misunderstand what's going on here, but the original TIF file was only 43 megabytes, yet GPlates is asking for 1 terabyte of memory? The lowest cellsize I have been allowed to export is 0.01 degrees. Is there something I am misunderstanding about the raster export process? Is there some way around this? Thanks in advance! Tom Thomas Schaap PhD Candidate | Casual Academic Staff CODES | Earth Sciences | Rm. 460 School of Natural Sciences University of Tasmania [cid:61edcbe5-98cd-4e87-bdbb-923fb84c13bf] University of Tasmania Electronic Communications Policy (December, 2014). This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-dco5vyy1.gif Type: image/gif Size: 7449 bytes Desc: Outlook-dco5vyy1.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-0bxoziaj.gif Type: image/gif Size: 7449 bytes Desc: Outlook-0bxoziaj.gif URL: From t.j.m.vanderlinden at uu.nl Sat Feb 29 02:01:13 2020 From: t.j.m.vanderlinden at uu.nl (Linden, T.J.M. van der (Thomas)) Date: Fri, 28 Feb 2020 15:01:13 +0000 Subject: [GPlates-discuss] See which features constitute a topology Message-ID: Hi, I have been trying to find which features constitute topologies in a downloaded GPlates model (in this case Matthews et al. GPC 2016, available from https://protect-au.mimecast.com/s/0wlvCMwvLQTqqLlN0Iwjbxc?domain=doi.org). I would like to know which parts of the topology are subduction zone, mid ocean ridge or passive margin. So far my efforts were not successful. Methods tried: * Select the topology and delete it, this results in the deletion of all features constituting the topology. * Disabling or deleting the layer with topologies * Selecting the topology and look in Query feature What works for some features is to select the Topology and then click on individual features constituting the topology. However not all features react to clicking in this mode (for instance the subduction zone of the Andes does not). Also the list shown in Topology Boundary Sections, cannot be used to highlight individual features on the map. Does anyone know a solution? I can imagine writing a pyGPlates script to create a new file with only features, but would like to have a direct graphical method. I use GPlates 2.2.0 in Windows10. Cheers from Berlin, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: