Ioannis Filippidis

Hi Devin,

Including the colorbar is not an implemented feature. The axes are included by plotting them in fig2u3d.m with the function plot_axes.

A suggestion would be to plot the colorbar within the axes (not as it is created by default, i.e., as a separate graphics object). An example which can be adapted according to your needs can be found here:

http://marine.rutgers.edu/~nstrands/MATLAB/googleplot/colorbarlegend.m

It looks like it needs some updating, but besides that it has the main idea of a colorbar comprised of patches. Then you can also select its preferred position and orientation.

Thanks for the idea, I will keep it mind for incorporating it in the next release.

Best,
Ioannis

Thank you for this code.

Please note that "close all" is not expected by a user from within a function. Plotting in a specific figure/axes object can be accomplished instead by explicitly opening one and passing the handle to "plot":
fig = figure;
ax = axes('Parent', fig);
plot(ax, ...)

Also "hold on" is interfering with the current settings by the user, if this function is called to add a curve to an existing figure. It would be better to first get the current hold state (if an axes object handle is passed as argument), then change it to "on" in order to add the curve and finally restore it to its original state:
http://www.mathworks.com/matlabcentral/fileexchange/36641-take-restore-hold

The function would benefit if it had arguments, so that the user can plot whichever Cassini curve they prefer.
If arguments are included, then the help text can be more explicit about how the function is used.
Referring to a link for the help text is not the usual practice.

Note also that the provided link is broken.

As a demonstration alternative, the function could plot several curves as it does now, if no arguments are provided, otherwise plot the curve prescribed by the arguments.

Hi Loannis,

This is a great tool and I've gotten it to work on my computer for the example files you provided. Unfortunately, it doesn't seem to work when I apply it to a figure produced by the "vol3d.m" function (by Joe Conti), which produces a volume rendering of 3-D data using the matlab "surface" function. I get a lot of outputs in the command line that say "Empty cdata". I don't get an error with fig2u3d.m but when I convert the u3d result to 3d pdf with acrobat, I get an empty white box. If I use fig2pdf3d.m I get the following error "Undefined function or variable "use_vertex_color". Error in shaders_materials_modifiers (line 49)". Do you know what could be wrong?

Hi Ben,

Thanks for the note, there is an OS X fix I've posted below (04 Dec 2012), but there is something else, please send me the fix. I planned to update the files here when time permitted.

I get an error when I try to load and parse an osm file, I have tried with different file sizes:

Cell contents reference from a non-cell array object.

Error in parse_osm>parse_way (line 61)
ndtemp(1, j) = str2double(waytemp.nd{j}.Attributes.ref);

Error in parse_osm (line 20)
parsed_osm.way = parse_way(osm_xml.way);

Error in parse_openstreetmap (line 43)
parsed_osm = parse_osm(osm_xml);

Error in OSMExample (line 29)
[parsed_osm, osm_xml] = parse_openstreetmap(openstreetmap_filename);

Any suggestions?