Dear all,<div><br></div><div>Thanks very much for all the swift replies. Apologies for any unwanted cross-postings, but I thought the resolution of this discussion might be of broader interest.</div><div><br></div><div>So Tan, it seems the GPlates format is naturally v_colat, v_long so no switch of the velocities required.</div>
<div><br></div><div>Thanks very much for the link Mark.</div><div><br></div><div>I encountered a similar wall to Rene, that only global mesh caps could be exported. I actually wrote my own 'regional' gpml mesh cap file, but it was not recognized as a mesh as such by GPlates (imported the gpml as velocities or something).</div>
<div><br></div><div>The workaround I used was to construct a perl script which uses some GMT calls, to grid the "global" exported velocity files, then re-sample them at the desired regional grid points. </div><div>
<br></div><div>I've posted it here for those interested:</div><div><a href="http://www.gemoc.mq.edu.au/~coneill/software/gpml2citcomR.pl">http://www.gemoc.mq.edu.au/~coneill/software/gpml2citcomR.pl</a></div><div><br>
</div><div>This seems to be working for me. <br>Any comments or corrections welcome!</div><div><br></div><div>cheers</div><div><br></div><div>-Craig.</div><div><br></div><div><br></div><div><br><div class="gmail_quote">On 29 June 2011 19:24, Mark Turner <span dir="ltr"><<a href="mailto:mturner@gps.caltech.edu">mturner@gps.caltech.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
hi,<br>
<br>
The format is the same for both the regional and global<br>
citcoms mesh input files if you are using .gpml.<br>
<br>
You can use GPlates to generate a set of global cap files<br>
with a small number of nodes per side of the cap,<br>
something like 3.<br>
<br>
Examine those files to see the .gpml format,<br>
and the ordering of the xml tags and such.<br>
<br>
Then create a .gpml citcoms input mesh file<br>
with your own regional mesh coordinates<br>
using the values in latitude and longitude.<br>
<br>
GPlates will read this data in as a single regular feature,<br>
with a multi-point geometry with your coordinates.<br>
<br>
<br>
Then the velocity generation process with in GPlates<br>
is the same for the global case.<br>
<br>
<br>
Yet, I'm not sure if that python script will work with<br>
a regional case. I'll check on that tomorrow.<br>
<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
is there any gplates version, that can create a regional mesh? In my version this checkbox is unselectable and gplates is referring to possible future versions.<br>
</blockquote>
<br>
yes, possibly ...<br>
but, I'm not sure if we fixed that in the next public release 1.1.1 ... ?<br>
<br>
For the last few years our focus has been with global model runs,<br>
so there are still gaps in the regional processing we need to fix up.<br>
Thanks for helping me figure out what needs work!<br><font color="#888888">
<br>
Mark<br>
<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Dr Craig O'Neill<div>ARC Future Fellow/Senior Lecturer<br>CCFS - Core to Crust Fluid Systems ARC Centre of Excellence</div><div>GEMOC ARC National Key Centre<br>
Department of Earth & Planetary Science<br>Macquarie University, E7A, Rm 515<br>Sydney, NSW, 2109, Australia<br><br>Phone: +61 2 9850 9673<br><a href="http://www.gemoc.mq.edu.au/~coneill/" target="_blank">http://www.gemoc.mq.edu.au/~coneill/</a><br>
</div><br>
</div>