Tagged with KML - Visokio Forums http://forums.visokio.com/discussions/tagged/KML/feed.rss Mon, 30 Oct 17 16:31:45 -0400 Tagged with KML - Visokio Forums en-CA GIS: Geometric buffer operation http://forums.visokio.com/discussion/2638/gis-geometric-buffer-operation Mon, 07 Jul 2014 12:28:04 -0400 richard 2638@/discussions
Geometric buffers can be applied to 3 types of shape data in Omniscope;
  • Point - A dataset containing pairs of latitude/longitude coordinates, e.g. a shop location.
  • Line - A dataset containing connected, and unfilled/unclosed, chains of points, e.g. a hurricane path or road.
  • Area - A dataset containing connected, and filled/closed, chains of points, e.g. a post code area or country border.


Below are instructions for buffering these 3 types of shape data. Please download and extract the contents of the ".zip" file:

POINT
  1. Create a new file in Omniscope and go to DataManager.
  2. Drag "United Kingdom cities.csv" onto the DataManager workspace. This contains 5 major cities in the United Kingdom with latitude/longitude coordinates.
  3. Connect a "Geometric buffer" operation to the workflow.
  4. Choose "Point" as the "Input data type". (For KML and Shapefile sources, this will be configured for you.)
  5. Enter a distance (km) to buffer around each input point. By reducing the "Quality" you will increase the speed of this block but the output dataset will contain less records and the buffered outline will not be as smooth.
  6. Check 'Include metadata' if you would like the output dataset to contain all other fields found in the input, i.e. "Country name".
  7. Execute the block, load the data into Omniscope and then drag a Map View into Omniscope to see the buffered points.

    image

    image


LINE
  1. Create a new file in Omniscope and go to DataManager.
  2. Drag "Hurricane Katrina.csv" onto the DataManager workspace. This contains coordinates for the path of Hurricane Katrina in 2005.
  3. Connect a "Geometric buffer" operation to the workflow.
  4. Choose "Line" as the "Input data type". (For KML and Shapefile sources, this will be configured for you.)
  5. Enter a distance (km) to buffer around the line (hurricane path). By reducing the "Quality" you will increase the speed of this block but the output dataset will contain less records and the buffered outline will not be as smooth.
  6. Execute the block, load the data into Omniscope and then drag a Map View into Omniscope to see the buffered line.

    image

    image


AREA
  1. Create a new file in Omniscope and go to DataManager.
  2. Drag "United Kingdom.kml" onto the DataManager workspace. This contains coordinates defining a simplified boundary of the United Kingdom..
  3. Connect a "Geometric buffer" operation to the workflow.
  4. Ensure "Area" is selected as the "Input data type". (For KML and Shapefile sources, this will be configured for you.)
  5. Choose your method of buffering:
    • Expand area - The original area plus an outside perimeter.
    • Contract area - The original area less an inside perimeter.
    • Outside perimeter - The area within a certain distance outside of the perimeter.
    • Inside perimeter - The area within a certain distance inside of the perimeter.
    • Outside + inside perimeter - The area within a certain distance either side of the perimeter.

  6. Enter a distance (km) to buffer around the United Kingdom. By reducing the "Quality" you will increase the speed of this block but the output dataset will contain less records and the buffered outline will not be as smooth.
  7. Execute the block, load the data into Omniscope and then drag a Map View into Omniscope to see the buffered line.

    image

    image



ADVANCED
The "Geometric buffer" block also contains additional controls for configuring which fields contain the latitude/longitude values and the fields for identifying individual features (shapes) in the input dataset. If you are using KML or Shapefile sources then these fields will be configured automatically. Below are explanations for each option:

  • Overlay identifier - Field containing unique identifiers for each point, line or area in the input dataset, e.g. a field containing country names or postal area codes.
  • Overlay sub-path identifier - This is used internally within Omniscope to identify nested geometries within each shape. For example a shape for the United Kingdom could not be drawn with one continuous line. We use this field to breakdown the records into numerous islands which make up the country.
  • Longitude - Field containing WGS84 longitude values.
  • Latitude - Field containing WGS84 latitude values.
]]> GIS: Importing a KML (Keyhole Markup Language) file http://forums.visokio.com/discussion/2634/gis-importing-a-kml-keyhole-markup-language-file Mon, 07 Jul 2014 07:49:27 -0400 richard 2634@/discussions
ATTACHED FILE
  • "postcode areas.kml" (inside ZIP) Contains geometries and meta-data for each feature (shape)


INSTRUCTIONS
  1. Download the attached ".zip" file and extract the ".kml" file.
  2. Create a new file in Omniscope and go to DataManager.
  3. Drag the "postcode areas.kml" file onto the DataManager workspace (or drag a "Data file" block onto the workspace and browse to the "postcode areas.kml" file).
  4. The KML DataManager block contains 3 configurable options:
    • "Overlay identifier" - The field which contains unique identifiers for each feature (shape) in the file. In our KML file this would be the names of the postal areas, e.g. AB for Aberdeen, SW6 for South West London. If your data does not include such a field then selecting "Create new field" will allow Omniscope to generate internal unique identifiers using a field named "Overlay ID".
    • "Meta data fields included" - The names of all fields which will be loaded from the KML file into the block.
    • "Shape types included" - KML files can contain a combination of points, lines and areas. Use this option to filter which shape types you want to load.

  5. Load the data into Omniscope then drag a Map View into Omniscope to see the postcode areas.


image

image

ADVANCED
You will notice a field has also been created named "Overlay sub-path ID". This is used internally within Omniscope to identify nested geometries within each shape. For example a shape for the United Kingdom could not be drawn with one continuous line. We use this field to breakdown the records into numerous islands which make up the country.]]> Map View: New GIS data files - Shapefiles, KML (2.8+) http://forums.visokio.com/discussion/2132/map-view-new-gis-data-files-shapefiles-kml-2.8- Fri, 10 May 2013 12:13:13 -0400 steve 2132@/discussions Omniscope 2.8 Beta, you can now import data from ESRI Shapefiles (.shp) and Google Earth (.kml) files.

These files typically contain geographic data, such as points, polygons and polylines, with additional metadata.

Omniscope allows you to import this data as a flat table of fields and records, take advantage of the powerful ETL DataManager merging and transforming operations, and/or open in Omniscope for exploring and analysing in the Map and other views.

When imported into Omniscope, the data is treated no differently to non-geo data. You can filter and aggregate, for example. Typically two fields will contain the lat/lon coordinates of each point or vertex, and other fields might exist for metadata or path ID purposes.]]>