QGIS is very useful and open source (as in free). Nothing specific for fiber mapping in it but it could pretty easily be used for it if I was ambitious enough to put all the info in.
Mark > On Jun 1, 2018, at 5:06 PM, Eric Kuhnke <[email protected]> wrote: > > For basic needs, the advantage of doing mapping using Google Earth Pro is > that most "serious" GIS packages support import and export to/from the XML > format Google Earth uses. A line on the map on Google Earth or a > multi-segmented line is just a collection of vector placemarks in a XML file > with lat/long coordinates, with metadata describing the thickness of the > line, the color of the line, how many intermediate points are on the line, > and so forth. > > The best organizational advice I can give is to use folders and subfolders in > Google Earth Pro appropriately to sort projects, so that you don't end up > with a single folder that contains 500 unnamed lines. Might look fine when > viewed on a map but can become an organization nightmare. > > On Fri, Jun 1, 2018 at 1:34 PM, Cassidy B. Larson <[email protected] > <mailto:[email protected]>> wrote: > Last topic I see on this was from 2014. So maybe it’s time to review and ask > again? What are you guys using for fiber mapping, now in 2018? > > In 2014 I read: > Craig was doing google earth and excel sheets. > Chuck Hogg was using Manifold (kinda), and some Google Maps Engine. > Mike H was using ArcMap for his clients. > A few other google sheets. > > What’s changed, what’s new, what’re you using today? Same as before? > Something different? Why? > > -c > >
