Package nz.org.riskscape.engine

Interface OutputProblems

All Superinterfaces:

ProblemFactory

public interface OutputProblems
extends ProblemFactory

Method Summary

Modifier and Type	Method	Description
Problem	cannotWriteManifest(PipelineOutputStore outputStore, URI location)	A parent problem to use when the manifest cannot be written.
Problem	checksumNotSupported(PipelineOutputStore outputStore)	When the user has asked for checksumming of results but the output store does not support this.
Problem	errorWriting(String tupleContent, String format)
static OutputProblems	get()
Problem	outputLocationNotSupported(URI location)	None of the configured output stores support this uri
Problem	outputTypeAsText(String attribute, Type type, PipelineOutputStore outputStore)	When the output has no specific mapping for the given type, so will fall-back to writing it as text.
Problem	unsupportedCrs(org.geotools.api.referencing.crs.CoordinateReferenceSystem crs)	A fallback problem when an Output format is unable to handle a non EPSG defined CRS.
Problem	userSpecifiedFormatIgnored(Format format, PipelineOutputStore outputStore)	The user has specified that outputs should be saved in the given format, but this will be ignored.

Method Details

get

static OutputProblems get()

unsupportedCrs

Problem unsupportedCrs(org.geotools.api.referencing.crs.CoordinateReferenceSystem crs)

A fallback problem when an Output format is unable to handle a non EPSG defined CRS.

This could be because non EPSG defined CRS's would need to be registered in an output specific format and this has not been implemented.

In practice it's unlikely that a non EPSG defined CRS would be used. Partly this is because: - CRS.lookupEpsgCode(org.geotools.api.referencing.crs.CoordinateReferenceSystem, boolean) will recognize CRS's from WKT as the correct EPSG code. - EPSG is the de facto standard

This problem exists in the hopefully rear case that the above assumptions prove incorrect. Or data has been used which does in fact use a custom defined CRS. Refer to GL729 for any potential future support of non EPSG CRSs.

Parameters:

crs - the CRS that is unsupported

outputLocationNotSupported

Problem outputLocationNotSupported(URI location)

None of the configured output stores support this uri

userSpecifiedFormatIgnored

Problem userSpecifiedFormatIgnored(Format format,
 PipelineOutputStore outputStore)

The user has specified that outputs should be saved in the given format, but this will be ignored.

Parameters:

format - the format being ignored

outputStore - the output store (PostGIS, GeoPackage) that is ignoring the format

cannotWriteManifest

Problem cannotWriteManifest(PipelineOutputStore outputStore,
 URI location)

A parent problem to use when the manifest cannot be written. The reasons should be added as child problems.

checksumNotSupported

Problem checksumNotSupported(PipelineOutputStore outputStore)

When the user has asked for checksumming of results but the output store does not support this.

outputTypeAsText

Problem outputTypeAsText(String attribute,
 Type type,
 PipelineOutputStore outputStore)

When the output has no specific mapping for the given type, so will fall-back to writing it as text.

errorWriting

Problem errorWriting(String tupleContent,
 String format)