Don't swallow error messages

[wilhelmberg]

Debugging a Mapbox Studio Classic and a KML problem, I came across this error message

which led me to believe the data was faulty and investigate in that direction, when in reality it seems that in the context of Mapbox Studio Classic and KMLs mapnik-omnivore/node-srs/node-gdal are not able to find the gdal support files:

May I suggest to augment the custom error message with the original error message?
e.g. change

return invalid('OGR source missing extent');

to

return invalid('OGR source missing extent: ' + err);

mapnik-omnivore/lib/ogr.js

Line 55 in ce7f47a

} catch (err) { return invalid('OGR source missing extent'); }

/cc @GretaCB

[wilhelmberg]

I haven't looked through the whole code, but it would be really great, if all similar error handling routines could be changed (if there are any others 😏)

[springmeyer]

The error message suppression is intentional. My understanding is that @rclark and @GretaCB decided to do this in order to sanitize/collapse all Mapnik and GDAL errors down to very simple messages that are also "Safe" and do not expose user info. But I definitely agree with you @BergWerkGIS that this adds an annoying friction and slowness to debugging for us - the developers trying to figure out where the generic error message is coming from. I think we should revisit this overall. One idea would be to add a verbose mode to mapnik-om such that all the raw Mapnik and GDAL errors that are suppressed are printed to stderr along with the err.stack.

[mannylopez]

I don't know if this is related but when trying to upload run.gpx I also get Error: OGR source missing extent.

I was able to upload the same file via the uploads page so the data is good.

[mannylopez]

Digging a bit deeper it looks like mapbox/mapbox-studio-classic#1473 is a better place to post this. Sorry for the noise!

[GretaCB]

Thanks @mannylopez , I can use run.gpx as a test-case to clean this up a bit. Happen to have any other files you know that run into this error?

hey @BergWerkGIS , what file were you using to run into this error? I can take a look at some test-cases and roll something new out with the original error (if it doesn't reveal sensitive server info).

[GretaCB]

@springmeyer This could be great:

I think we should revisit this overall. One idea would be to add a verbose mode to mapnik-om such that all the raw Mapnik and GDAL errors that are suppressed are printed to stderr along with the err.stack.

I can play around with this.