Hexagon Geospatial
MENU

M.App Enterprise

Discuss topics with other M.App Enterprise Product pioneers and experts to get the most out of it.
Showing results for 
Search instead for 
Do you mean 
Reply
Highlighted
Frequent Contributor
Posts: 145
Registered: ‎02-17-2016

Adding Imagery fails: could not parse CRS:1

I am trying to add some imagery to Content/Imagery. The data is GeoTIFF, at a path of \\swi-sgiv-lic01\Common_Data_Store. I have received an error 'Could not parse CRS: CRS1'. The images use EPSG:27700.

 

Moving one image to a local drive on the M.App Enterprise server, then I get a 501 error.

 

Any suggestions? I can share the images. 

 

Thanks

Staff
Posts: 982
Registered: ‎10-19-2015

Re: Adding Imagery fails: could not parse CRS:1

Hi,

 

is the image a GeoTIFF or a tiff with external world file? If a GeoTIFF is there the EPSG code defined in the header?

 

Stefano

Stefano Turcato
Presale Engineer
Hexagon Geospatial
Frequent Contributor
Posts: 145
Registered: ‎02-17-2016

Re: Adding Imagery fails: could not parse CRS:1

Hi Stefano

 

The images are GeoTIFF, and do have the EPSG referenced (27700, British National Grid) in them - see below from ISRU Display Header - 

 

Output from Display Header
File Name: \\swi-sgiv-lic01\Common_Data_Store\OS OpenMap Local\omlras_gtfc_sx\OS OpenMap Local (Full Colour Raster) SX\data\SX04NE.tif
File Information:
Standard : : TIFF File
Format : : LZW : Compressed 8 bit data
Pixels per Line : 5000
Number of Lines : 5000
Samples per pixel : 1
File bits per sample : 8
Actual bits per sample : 8
Untiled file
Number of overviews : 0
Scanning device resolution : 254 : lines/inch
Orientation : 4 : Row major order, origin at top left
NO scan line headers : non-scannable file
Standard color table - type: 2
Color Table Size - Num entries: 256
Packet size (16-bit words) : 0
Free vlt space (16-bit words) : 2000000000
Free packet space (16-bit words) : 2000000000
Raster to UOR matrix:
Unspecified or All Zero Matrix
Raster to World Matrix:
Units: Meters
amx[ 0]= 1, amx[ 1]= 0, amx[ 2]= 205000
amx[ 3]= 0, amx[ 4]= -1, amx[ 5]= 50000
205000 , 50000
210000 , 50000
210000 , 45000
205000 , 45000
Geotiff_Information:
Version: 1
Key_Revision: 1.0
Tagged_Information:
ModelTiepointTag (2,3):
0 0 0
205000 50000 0
ModelPixelScaleTag (1,3):
1 1 0
End_Of_Tags.
Keyed_Information:
GTModelTypeGeoKey (Short,1): ModelTypeProjected
GTRasterTypeGeoKey (Short,1): RasterPixelIsArea
GTCitationGeoKey (Ascii,34): "OSGB 1936 / British National Grid"
GeogCitationGeoKey (Ascii,10): "OSGB 1936"
GeogAngularUnitsGeoKey (Short,1): Angular_Degree
Unknown-2062 (Double,7): 446.448 -125.157 542.06
0.15 0.247 0.842
-20.489
ProjectedCSTypeGeoKey (Short,1): PCS_British_National_Grid
ProjLinearUnitsGeoKey (Short,1): Linear_Meter
End_Of_Keys.
End_Of_Geotiff.
PCS = 27700 (OSGB 1936 / British National Grid)
Projection = 19916 (British National Grid)
Projection Method: CT_TransverseMercator
ProjNatOriginLatGeoKey: 49.000000 ( 49d 0' 0.00"N)
ProjNatOriginLongGeoKey: -2.000000 ( 2d 0' 0.00"W)
ProjScaleAtNatOriginGeoKey: 0.999601
ProjFalseEastingGeoKey: 400000.000000 m
ProjFalseNorthingGeoKey: -100000.000000 m
GCS: 4277/OSGB 1936
Datum: 6277/OSGB 1936
Ellipsoid: 7001/Airy 1830 (6377563.40,6356256.91)
Prime Meridian: 8901/Greenwich (0.000000/ 0d 0' 0.00"E)
Projection Linear Units: 9001/metre (1.000000m)
Corner Coordinates:
Upper Left ( 205000.000, 50000.000)
Lower Left ( 205000.000, 45000.000)
Upper Right ( 210000.000, 50000.000)
Lower Right ( 210000.000, 45000.000)
Center ( 207500.000, 47500.000)

Staff
Posts: 982
Registered: ‎10-19-2015

Re: Adding Imagery fails: could not parse CRS:1

Hi Richard,

 

could you please check if the image has been anyway registered in Apollo Core? You know with M.App Enterprise we have an instance of Apollo deployed, but there is not an external console to administer it. What you can do is to check the sqllite database where the configuration is stored that it should be in the M.App warehouse folder. 

If you see the dataset registered there you might check if it is correctly handled by Apollo using the WMS or WMTS service. It should be something like this:

 

https://[SERVER_NAME]/erdas-iws/ogc/wmts/[TENANT_NAME]?service=WMTS&service=WMTS&request=Getcapabilities

 

ciao,

Stefano

Stefano Turcato
Presale Engineer
Hexagon Geospatial
Frequent Contributor
Posts: 145
Registered: ‎02-17-2016

Re: Adding Imagery fails: could not parse CRS:1

Hi Stefano

From looking in IWS.db (using Notepad++), there are references to the images I have been trying to add as Imagery in M.App Ent. So has the load partially worked and now there is no user interface to remove this data?

 

The WMTS GetCapailities also does list the imagery as available, adn I can view it on a direct call to the WMTS.

Thanks

Richard

Staff
Posts: 982
Registered: ‎10-19-2015

Re: Adding Imagery fails: could not parse CRS:1

Hi Richard,

 

yes, guess so. What you can do as a workaround is to insert the dataset in the tenant config database. There are 2 tables MAPP_DATASET and then MAPP_IMAGERY. I the second one you have to upload the whole getcapabilites response in the corresponding field.

 

HTH,

Stefano

Stefano Turcato
Presale Engineer
Hexagon Geospatial
Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Development Ticket through our Development Ticket Portal.