- Messages
- 203
- Country
I've been attempting to create shp files to import into Google Earth to produce kml files from which to accurately create water masks/blends in FSET.
I downloaded free data from Ordnance Survey for the UK, containing full coastline data (Opendata Meridian)
There is a shp file called coast_ln_polyline which is exactly as described - a full coastline shp file made up of many numerous polylines.
Now, importing that shp file into GE works fine, but it creates it as geometry rather than a polygon, so when I try to use a kml file incorporating that data in FSET, FSET doesn't recognise it
SO, I tried to manipulate the polyline in QGIS, by selecting all the constituent polylines in the shp file and using the vector>geoprocessing tools>dissolve menu command. It appears to result in one wholly enclosed polygon, but importing that into GE results in it being displayed again as geometry rather than a whole polygon :s
Am I using the wrong options in QGIS and therefore not creating the right data in the shp file that I'm importing into GE?
Or is there just some arcane problem with GE in that it can't properly import shp files as true polygons so they can be understood by FSET?
Or something else?
Any pointers of gems of information very very gratefully received...
Thanks K
I downloaded free data from Ordnance Survey for the UK, containing full coastline data (Opendata Meridian)
There is a shp file called coast_ln_polyline which is exactly as described - a full coastline shp file made up of many numerous polylines.
Now, importing that shp file into GE works fine, but it creates it as geometry rather than a polygon, so when I try to use a kml file incorporating that data in FSET, FSET doesn't recognise it

SO, I tried to manipulate the polyline in QGIS, by selecting all the constituent polylines in the shp file and using the vector>geoprocessing tools>dissolve menu command. It appears to result in one wholly enclosed polygon, but importing that into GE results in it being displayed again as geometry rather than a whole polygon :s
Am I using the wrong options in QGIS and therefore not creating the right data in the shp file that I'm importing into GE?
Or is there just some arcane problem with GE in that it can't properly import shp files as true polygons so they can be understood by FSET?
Or something else?

Any pointers of gems of information very very gratefully received...
Thanks K