<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt"><div><span>I agree - that approach to managing spatial data was last century's one.<br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>I recommend you use a spatially enabled database to manage spatial data . as many geometries/geographies as you want per feature.</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;
background-color: transparent; font-style: normal;"><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>We have polygons with a point label location, linestrings with start finish timestamps as well as start, finish and mid points.</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>From a traditional GIS centric perspective the coords defining the spatial representation of an entity has a special place - they are the
entity, & the other attributes just hang of it. A fundamentally flawed model according to good data management practices.</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>A good RDBMS stores a spatial representation value as just another attribute, you can have as many geometry, date/time, numeric or text fields describing your real world entity as you like... enablind spatial data to be corecvctly modelled & managed. Pretty much all GIS tools these days support connecting to an external spatial database as an alternative to an internal database or file based system.
<br></span></div><div><br></div><div>I prefer Postgis, but MySQL/MariaDB, or even the free versions of SQL Server & Oracle support the OGC SFS standard, which, amongst other things, defines an approach for storing simple spatial features in a RDBMS.</div><div><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;">If you want a cloud based approach - Amazon cloud supports Postgres, you can establish a database, install Postgis & insert your data, configuring the Postgres server to allow access from your systems as you require via IP afddress & user name. <br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0);
font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;">Cheers,</div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"> Brent<br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br></div> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 10pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue,
Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> kilolima <kilolima@imap.cc><br> <b><span style="font-weight: bold;">To:</span></b> qgis-user@lists.osgeo.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Saturday, August 30, 2014 8:39 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> [Qgis-user] How to store spatial information of various geometry types (point, line, polygon) in one place?<br> </font> </div> <div class="y_msg_container"><br>Hi All,<br><br>For work, we use a Google Sheets spreadsheet that is accessible to various<br>people. The spreadsheet is mostly text attribute data with spatial<br>information stored in WKT fields (points and polylines). When it comes time<br>to make a map, I download a csv and import into QGIS. I realized that the<br>csv import process will only allow one
geometry type during the import and<br>discard the others. This results in having to repeat the import process for<br>each geometry type in the csv.<br><br>Is there some better way to do this, ideally that would allow text and<br>spatial data of various geometry types to be stored and read all at once? Is<br>there a way to get around the seemingly archaic separation of vector layers<br>based on geometry types? Is there a native QGIS format that can handle this<br>and import from a spreadsheet?<br><br>Or, ideally, is there some sort of magical connector between Google Sheets<br>and QGIS, so a change online in Sheets would update the map in QGIS?<br><br>cheers,<br><br>kilolima<br><br><br><br>--<br>View this message in context: <a href="http://osgeo-org.1560.x6.nabble.com/How-to-store-spatial-information-of-various-geometry-types-point-line-polygon-in-one-place-tp5159178.html"
target="_blank">http://osgeo-org.1560.x6.nabble.com/How-to-store-spatial-information-of-various-geometry-types-point-line-polygon-in-one-place-tp5159178.html</a><br>Sent from the Quantum GIS - User mailing list archive at Nabble.com.<br>_______________________________________________<br>Qgis-user mailing list<br><a ymailto="mailto:Qgis-user@lists.osgeo.org" href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br><br><br></div> </div> </div> </div></body></html>