Export Text or Text Nodes to KMZ

From what I've seen of the export options and doing some basic testing, MicroStation can't give you what you seek aside from the line geometry. I think the only way to achieve those pin marks is:

1. Export the cell insertion point coordinates (unsure if using Export Coordinates and a GCS will export to Lat/Long instead of XYZ. If not, you'd need to convert them.
2. Manually editing a KML file, pasting each coordinate and the desired name. Probably simplest to open Google Earth, place a single placemark, name it and export that to KML. Then open the file in Notepad++ , copy the lines pertaining to your test placemark for every required placemark, and paste the Lat/Long coordinates and the name you wish for each.
3. Import the KML into Google Earth

There might be a way to do some of the work in Excel, perhaps somehow being able to import data from a CSV. Its just conjecture on my part as I don't do anything with Google Earth.

Hi Ron

Thanks for the suggestion. I tried to create a new property filter, but I could not find a Text Node/Content/Text String property to add to the filter. Text/Text String does not seem to work on Text Nodes but only Text Elements.

What I'm getting and what I'm looking for are illustrated in the figure below.

The top text nodes have been exported to Google Earth KMZ and they are big and slow because the Arial letters are converted into shapes.

What I would like to export is shown below - the next nodes are exported as pins instead, with the text as the name of the pin.

Any ideas?

how do you get rid of place marks generally.. Also I have custom line styles for line making and it comes across but lots of place marks and  DGN StyleNo  as Big white text.. Tried dropping  linestyles helped a little  but these DoT linestyles are very complex...?

Hi Warren,

In the Google Earth Tools Settings Dialog you can choose to Include Properties. This data will be displayed as placemarks in Google Earth.

I don't know if this will do what you want, but it is worth a try.

Regards,
Ron