geoblacklight_sidecar_images 0.9.1 → 1.1.0

data/spec/fixtures/files/restricted-line.json

@@ -1,37 +0,0 @@
-{
-  "dc_identifier_s": "http://purl.stanford.edu/cg357zz0321",
-  "dc_title_s": "10 Meter Contours: Russian River Basin, California",
-  "dc_description_s": "This line shapefile contains contours that were derived from a mosiac of 10 meter digital elevation models for the extent of the Russian River basin, located in Sonoma and Mendocino Counties, California.This layer can be used for watershed analysis and planning in the Russian River region of California.",
-  "dc_rights_s": "Restricted",
-  "dct_provenance_s": "Stanford",
-  "dct_references_s": "{\"http://schema.org/url\":\"http://purl.stanford.edu/cg357zz0321\",\"http://schema.org/downloadUrl\":\"http://stacks.stanford.edu/file/druid:cg357zz0321/data.zip\",\"http://www.loc.gov/mods/v3\":\"http://purl.stanford.edu/cg357zz0321.mods\",\"http://www.isotc211.org/schemas/2005/gmd/\":\"https://raw.githubusercontent.com/OpenGeoMetadata/edu.stanford.purl/master/cg/357/zz/0321/iso19139.xml\",\"http://www.opengis.net/def/serviceType/ogc/wfs\":\"https://geowebservices-restricted.stanford.edu/geoserver/wfs\",\"http://www.opengis.net/def/serviceType/ogc/wms\":\"https://geowebservices-restricted.stanford.edu/geoserver/wms\"}",
-  "layer_id_s": "druid:cg357zz0321",
-  "layer_slug_s": "stanford-cg357zz0321",
-  "layer_geom_type_s": "Line",
-  "layer_modified_dt": "2016-04-25T17:13:35Z",
-  "dc_format_s": "Shapefile",
-  "dc_language_s": "English",
-  "dc_type_s": "Dataset",
-  "dc_publisher_s": "Circuit Rider Productions",
-  "dc_creator_sm": [
-    "United States. National Oceanic and Atmospheric Administration",
-    "Circuit Rider Productions"
-  ],
-  "dc_subject_sm": [
-    "Contours (Cartography)",
-    "Elevation",
-    "Inland Waters"
-  ],
-  "dct_issued_s": "2002",
-  "dct_temporal_sm": [
-    "2002"
-  ],
-  "dct_spatial_sm": [
-    "Sonoma County (Calif.)",
-    "Mendocino County (Calif.)"
-  ],
-  "solr_geom": "ENVELOPE(-123.387366, -122.52958, 39.398403, 38.302994)",
-  "solr_year_i": 2002,
-  "stanford_rights_metadata_s": "<?xml version=\"1.0\"?>\n<rightsMetadata>\n  <access type=\"discover\">\n    <machine>\n      <world/>\n    </machine>\n  </access>\n  <access type=\"read\">\n    <machine>\n      <group>Stanford</group>\n    </machine>\n  </access>\n  <use>\n    <human type=\"useAndReproduction\">These data are licensed by Stanford Libraries and are available to Stanford University affiliates only. Affiliates are limited to current faculty, staff and students. These data may not be reproduced or used for any purpose without permission. For more information please contact brannerlibrary@stanford.edu.</human>\n    <human type=\"creativeCommons\"/>\n    <machine type=\"creativeCommons\"/>\n  </use>\n  <copyright>\n    <human>Copyright ownership resides with the originator.</human>\n  </copyright>\n</rightsMetadata>\n",
-  "geoblacklight_version": "1.0"
-}

data/spec/fixtures/files/umn_metro_result1.json

@@ -1,41 +0,0 @@
-{
-  "dc_identifier_s": "02236876-9c21-42f6-9870-d2562da8e44f",
-  "dc_title_s": "2030 Regional Development Framework Planning Areas: Metro Twin Cities, Minnesota, 2011",
-  "dc_description_s": "The 2030 Regional Development Framework Planning Areas - 2011 updates the 2030 Regional Development Framework Planning Areas initially adopted on January 14, 2004 and ammended in 2006. This dataset reflect the agreed upon planning areas between a community and the Metropolitan Council and defined in the communities' 2030 Comprehensive Plan Update and is intended to supplement the 2030 Regional Development Framework - the planning guide for the 7-county Twin Cities metropolitan area of Minneapolis and Saint Paul, Minnesota.   Planning area definitions and strategies for the planning areas are available in the 2030 Regional Development Framework document at http://www.metrocouncil.org/Planning/Planning/2030-Regional-Development-Framework.aspx  (See Chapter 3). For questions about how decisions were made regarding individual communities' geographic planning areas, please contact the Metropolitan Council Regional Framework Development staff, Dan Marckel, 651-602-1548.  See Currentness Reference and Lineage in Data Quality Section of this metadata for more information.",
-  "dc_rights_s": "Public",
-  "dc_format_s": "Shapefile",
-  "dc_language_sm": [
-    "English"
-  ],
-  "dc_type_sm": [
-    "Dataset",
-    "Service"
-  ],
-  "dc_publisher_sm": [
-    "Metropolitan Council"
-  ],
-  "dc_creator_sm": [
-    "Metropolitan Council"
-  ],
-  "dc_subject_sm": [
-    "Planning and Cadastral"
-  ],
-  "dct_provenance_s": "Minnesota",
-  "dct_references_s": "{\"http://schema.org/url\":\"https://gisdata.mn.gov/dataset/02236876-9c21-42f6-9870-d2562da8e44f\",\"http://schema.org/downloadUrl\":\"ftp://ftp.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/plan_frmwrk2030dev_plan_ar2011/shp_plan_frmwrk2030dev_plan_ar2011.zip\",\"urn:x-esri:serviceType:ArcGIS#DynamicMapLayer\":\"https://gis2.metc.state.mn.us/arcgis/rest/services/MetroGIS/Planning/MapServer/3\",\"http://www.opengis.net/cat/csw/csdgm\":\"https://btaagdp.org/metadata/05a-01/pub/gdrs/data/pub/us_mn_state_metc/plan_frmwrk2030dev_plan_ar2011/metadata/metadata.xml\"}",
-  "dct_isPartOf_sm": [
-    "Minnesota Geospatial Commons"
-  ],
-  "dct_issued_s": "2015-10-01T10:01:54.499443",
-  "dct_temporal_sm": [
-    "2014"
-  ],
-  "dct_spatial_sm": [
-    "Minnesota, United States"
-  ],
-  "layer_slug_s": "02236876-9c21-42f6-9870-d2562da8e44f",
-  "layer_geom_type_s": "Polygon",
-  "layer_modified_dt": "2018-08-02T17:42:57Z",
-  "solr_geom": "ENVELOPE(-94.012, -92.732, 45.415, 44.471)",
-  "solr_year_i": 2014,
-  "geoblacklight_version": "1.0"
-}

data/spec/fixtures/files/umn_metro_result2.json

@@ -1,35 +0,0 @@
-{
-  "layer_geom_type_s": "Mixed",
-  "layer_modified_dt": "2017-01-20T18:39:22Z",
-  "solr_geom": "ENVELOPE(-94.012, -92.732, 45.415, 44.471)",
-  "dct_references_s": "{\"http://schema.org/downloadUrl\":\"ftp://ftp.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/society_census_trt_comb1990_2000/shp_society_census_trt_comb1990_2000.zip\",\"http://schema.org/url\":\"https://gisdata.mn.gov/dataset/us-mn-state-metc-society-census-trt-comb1990-2000\",\"http://www.isotc211.org/schemas/2005/gmd/\":\"https://opengeometadata.github.io/edu.umn/e9/71/49/88c3074135b7a7a1d521949f5d/iso19139.xml\"}",
-  "dc_rights_s": "Public",
-  "dct_provenance_s": "Minnesota",
-  "dc_subject_sm": [
-    "Society"
-  ],
-  "dc_format_s": "Shapefile",
-  "dc_description_s": "This dataset consists of a correspondence table and shape file of the combined 1990 and 2000 Census tracts. Note: Census tracts from 1990 and 2000 do not match in all areas. This dataset is an attempt to match them. Some combining and splitting of tracts was necessary. See the Lineage in Section 2 of the metadata for more information.",
-  "dct_issued_s": "2003-01-27",
-  "dct_temporal_sm": [
-    "1990-2000"
-  ],
-  "dc_creator_sm": [
-    "Metropolitan Council"
-  ],
-  "dc_identifier_s": "e9714988-c307-4135-b7a7-a1d521949f5d",
-  "solr_year_i": 1990,
-  "dct_spatial_sm": [
-    "Minnesota, United States",
-    "Minneapolis-St. Paul-Bloomington, United States"
-  ],
-  "dc_publisher_sm": [
-    "Metropolitan Council"
-  ],
-  "layer_id_s": "e9714988-c307-4135-b7a7-a1d521949f5d",
-  "dc_title_s": "1990 to 2000 Census Tract Correspondence and Combined Tracts: Twin Cities Metro, Minnesota, 2003",
-  "layer_slug_s": "e9714988-c307-4135-b7a7-a1d521949f5d",
-  "dct_isPartOf_sm": [
-    "Minnesota Geospatial Commons"
-  ]
-}

data/spec/fixtures/files/umn_state_result1.json

@@ -1,38 +0,0 @@
-{
-  "dc_identifier_s": "2eddde2f-c222-41ca-bd07-2fd74a21f4de",
-  "dc_title_s": "1:100k Digital Raster Graphic - Collars Removed: Minnesota",
-  "dc_description_s": "A digital raster graphic (DRG) is a scanned image of an U.S. Geological Survey (USGS) standard series topographic map, including all map collar information. The image inside the map neatline is georeferenced to the surface of the earth and fit to the Universal Transverse Mercator projection. The horizontal positional accuracy and datum of the DRG matches the accuracy and datum of the source map. The map is scanned at a minimum resolution of 250 dots per inch.  DRG's are created by scanning published paper maps on high-resolution scanners.  The raster image is georeferenced and fit to the UTM projection.  Colors are standardized to remove scanner limitations and artifacts.  The average data set size is about 6 megabytes in Tagged Image File Format (TIFF) with PackBits compression. DRG's can be easily combined with other digital cartographic products such as digital elevation models (DEM) and digital orthophoto quadrangles (DOQ).  DRG's are stored as rectified TIFF files in geoTIFF format. GeoTIFF is a relatively new TIFF image storage format that incorporates georeferencing information in the header. This allows software, such as ArcView, ARC/INFO, or EPPL7 to reference the image without an additional header or world file.  Within the Minnesota Department of Natural Resources Core GIS data set the DRG's have been processed to be in compliance with departmental data standards (UTM Extended Zone 15, NAD83 datum) and the map collar information has been removed to facilitate the display of the DRG's in a seamless fashion.  These DRG's were clipped and transformed to UTM Zone 15 using EPPL7 Raster GIS.",
-  "dc_rights_s": "Public",
-  "dc_format_s": "ArcGRID",
-  "dc_language_sm": "English",
-  "dc_type_sm": [
-    "Dataset"
-  ],
-  "dc_publisher_sm": [
-    "Minnesota Department of Natural Resources (DNR)"
-  ],
-  "dc_creator_sm": [
-    "U.S. Geological Survey (USGS) and Minnesota Department of Natural Resources (DNR)"
-  ],
-  "dc_subject_sm": [
-    "Imagery and Base Maps"
-  ],
-  "dct_provenance_s": "Minnesota",
-  "dct_references_s": "{\"http://schema.org/url\":\"https://gisdata.mn.gov/dataset/2eddde2f-c222-41ca-bd07-2fd74a21f4de\",\"http://schema.org/downloadUrl\":\"ftp://gdrs.dnr.state.mn.us/gdrs/data/pub/us_mn_state_dnr/fgdb_base_usgs_scanned_topo_100k_drg.zip\",\"http://schema.org/image\":\"https://btaagdp.org/thumbnails/05a-01/pub/gdrs/data/pub/us_mn_state_dnr/base_usgs_scanned_topo_100k_drg/metadata/preview.jpg\",\"http://www.opengis.net/cat/csw/csdgm\":\"https://btaagdp.org/metadata/05a-01/pub/gdrs/data/pub/us_mn_state_dnr/base_usgs_scanned_topo_100k_drg/metadata/metadata.xml\"}",
-  "dct_isPartOf_sm": [
-    "Minnesota Geospatial Commons"
-  ],
-  "dct_issued_s": "2015-11-18T11:02:15.705119",
-  "dct_temporal_sm": [
-    "2015"
-  ],
-  "dct_spatial_sm": [
-    "Minnesota, United States"
-  ],
-  "layer_slug_s": "2eddde2f-c222-41ca-bd07-2fd74a21f4de",
-  "layer_geom_type_s": "Raster",
-  "layer_modified_dt": "2018-08-02T17:47:58Z",
-  "solr_geom": "ENVELOPE(-97.612501, -88.842351, 49.464145, 42.906949)",
-  "solr_year_i": 2015,
-  "geoblacklight_version": "1.0"
-}

data/spec/fixtures/files/umn_state_result2.json

@@ -1,38 +0,0 @@
-{
-  "dc_identifier_s": "e9c71086-6b25-4950-8e1c-84c2794e3382",
-  "dc_title_s": "1:250k Digital Raster Graphic - Collars Removed: Minnesota",
-  "dc_description_s": "A digital raster graphic (DRG) is a scanned image of an U.S. Geological Survey (USGS) standard series topographic map, including all map collar information. The image inside the map neatline is georeferenced to the surface of the earth and fit to the Universal Transverse Mercator projection. The horizontal positional accuracy and datum of the DRG matches the accuracy and datum of the source map. The map is scanned at a minimum resolution of 250 dots per inch.  DRG's are created by scanning published paper maps on high-resolution scanners.  The raster image is georeferenced and fit to the UTM projection.  Colors are standardized to remove scanner limitations and artifacts.  The average data set size is about 6 megabytes in Tagged Image File Format (TIFF) with PackBits compression. DRG's can be easily combined with other digital cartographic products such as digital elevation models (DEM) and digital orthophoto quadrangles (DOQ).  DRG's are stored as rectified TIFF files in geoTIFF format. GeoTIFF is a relatively new TIFF image storage format that incorporates georeferencing information in the header. This allows software, such as ArcView, ARC/INFO, or EPPL7 to reference the image without an additional header or world file.  Within the Minnesota Department of Natural Resources Core GIS data set the DRG's have been processed to be in compliance with departmental data standards (UTM Extended Zone 15, NAD83 datum) and the map collar information has been removed to facilitate the display of the DRG's in a seamless fashion.  These DRG's were clipped and transformed to UTM Zone 15 using EPPL7 Raster GIS.",
-  "dc_rights_s": "Public",
-  "dc_format_s": "GeoTIFF",
-  "dc_language_sm": "English",
-  "dc_type_sm": [
-    "Dataset"
-  ],
-  "dc_publisher_sm": [
-    "Minnesota Department of Natural Resources (DNR)"
-  ],
-  "dc_creator_sm": [
-    "U.S. Geological Survey and Minnesota DNR"
-  ],
-  "dc_subject_sm": [
-    "Imagery and Base Maps"
-  ],
-  "dct_provenance_s": "Minnesota",
-  "dct_references_s": "{\"http://schema.org/url\":\"https://gisdata.mn.gov/dataset/e9c71086-6b25-4950-8e1c-84c2794e3382\",\"http://schema.org/downloadUrl\":\"ftp://ftp.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_dnr/base_usgs_scanned_topo_250k_drg/fgdb_base_usgs_scanned_topo_250k_drg.zip\",\"http://schema.org/image\":\"https://btaagdp.org/thumbnails/05a-01/pub/gdrs/data/pub/us_mn_state_dnr/base_usgs_scanned_topo_250k_drg/metadata/preview.jpg\",\"http://www.opengis.net/cat/csw/csdgm\":\"https://btaagdp.org/metadata/05a-01/pub/gdrs/data/pub/us_mn_state_dnr/base_usgs_scanned_topo_250k_drg/metadata/metadata.xml\"}",
-  "dct_isPartOf_sm": [
-    "Minnesota Geospatial Commons"
-  ],
-  "dct_issued_s": "2015-11-18T11:02:15.187331",
-  "dct_temporal_sm": [
-    "1998"
-  ],
-  "dct_spatial_sm": [
-    "Minnesota, United States"
-  ],
-  "layer_slug_s": "e9c71086-6b25-4950-8e1c-84c2794e3382",
-  "layer_geom_type_s": "Raster",
-  "layer_modified_dt": "2018-08-02T17:49:48Z",
-  "solr_geom": "ENVELOPE(-97.991522, -87.177541, 49.892443, 42.891013)",
-  "solr_year_i": 1998,
-  "geoblacklight_version": "1.0"
-}

data/spec/fixtures/files/uva_slug_colon.json

@@ -1,25 +0,0 @@
-{
-  "dc_description_s": "Police stations for Norfolk, Virginia.",
-  "dc_format_s": "Shapefile",
-  "dc_identifier_s": "315fc8ee-3b57-4ebb-aa24-4300f1c42dc9-13",
-  "dc_language_s": "eng",
-  "dc_rights_s": "Public",
-  "dc_subject_sm": [
-    "Location"
-  ],
-  "dc_title_s": "Norfolk 2005 Police Stations",
-  "dct_issued_s": "2008-10-17",
-  "dct_provenance_s": "UVa",
-  "dct_references_s": "{\"http://www.opengis.net/def/serviceType/ogc/wms\":\"http://gis.lib.virginia.edu/geoserver/wms\",\"http://www.opengis.net/def/serviceType/ogc/wfs\":\"http://gis.lib.virginia.edu/geoserver/wfs\",\"http://www.opengis.net/def/serviceType/ogc/wcs\":\"http://gis.lib.virginia.edu/geoserver/wcs\",\"http://schema.org/downloadUrl\":\"http://gis.lib.virginia.edu/geoserver/ows?service=WFS\\u0026typeName=Norfolk:police_point\\u0026request=GetFeature\\u0026outputFormat=shape-zip\",\"http://www.isotc211.org/schemas/2005/gmd/\":\"https://opengeometadata.github.io/edu.virginia/382/13/iso19139.xml\"}",
-  "dct_temporal_sm": [
-    "2005-2005"
-  ],
-  "georss_polygon_s": "36.82 -76.346 36.971 -76.346 36.971 -76.176 36.82 -76.176 36.82 -76.346",
-  "layer_geom_type_s": "MultiPoint",
-  "layer_id_s": "Norfolk:police_point",
-  "layer_modified_dt": "2008-11-12T15:29:47Z",
-  "layer_slug_s": "uva-Norfolk:police_point",
-  "solr_geom": "ENVELOPE(-76.346, -76.176, 36.971, 36.82)",
-  "solr_year_i": 2005,
-  "geoblacklight_version": "1.0"
-}

data/spec/rails_helper.rb

@@ -1,59 +0,0 @@
-# frozen_string_literal: true
-
-ENV["RAILS_ENV"] ||= "test"
-
-require "spec_helper"
-require "database_cleaner"
-require "engine_cart"
-EngineCart.load_application!
-
-require "rspec/rails"
-# Add additional requires below this line. Rails is not loaded until this point!
-
-require "geoblacklight_sidecar_images"
-
-# Requires supporting ruby files with custom matchers and macros, etc, in
-# spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are
-# run as spec files by default. This means that files in spec/support that end
-# in _spec.rb will both be required and run as specs, causing the specs to be
-# run twice. It is recommended that you do not name files matching this glob to
-# end with _spec.rb. You can configure this pattern with the --pattern
-# option on the command line or in ~/.rspec, .rspec or `.rspec-local`.
-#
-# The following line is provided for convenience purposes. It has the downside
-# of increasing the boot-up time by auto-requiring all files in the support
-# directory. Alternatively, in the individual `*_spec.rb` files, manually
-# require only the support files necessary.
-#
-# Dir[Rails.root.join("spec/support/**/*.rb")].each { |f| require f }
-
-# require 'capybara/poltergeist'
-# Capybara.javascript_driver = :poltergeist
-
-RSpec.configure do |config|
-  # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
-  config.fixture_path = "#{::Rails.root}/spec/fixtures"
-
-  config.before(:suite) do
-    DatabaseCleaner.clean_with :truncation
-  end
-
-  config.before do
-    DatabaseCleaner.strategy = if Capybara.current_driver == :rack_test
-      :transaction
-    else
-      :truncation
-    end
-    DatabaseCleaner.start
-  end
-
-  config.after do
-    DatabaseCleaner.clean
-  end
-
-  config.infer_spec_type_from_file_location!
-end
-
-def main_app
-  Rails.application.class.routes.url_helpers
-end