Not able to publish new datasets on Production

[aidanmazur]

I have created 2 new datasets and I am unable to publish them. When I click on the publish button the message "Success. Your dataset is processing. you will be emailed at amazur@wisc.edu when your dataset is ready". I then get an email telling me that my dataset has failed to publish.

The datasets I created are "Effects of Aphid damage on Soy Plants" (http://data.ecosis.org/dataset/effects-of-aphid-damage-on-soy-plants) and "Aphids destroy soy part 2" (http://data.ecosis.org/dataset/aphids-destroy-soy-part-2)

I am able to republish existing datasets.

[jrmerz]

@aidanmazur (@ckingdon FYI) There are two issues here, but I don't think they are critical and can be fixed in next release.

The first issue is why the dataset didn't push. The reason for that is you have bad geometry. This appears to be caused my LeafletJS map (the JavaScript map library I used) having wrapping turned on, so once you just hit the edge of the map, the map continues on. Well the Longitude appears to continue on as well, because your geometry has a longitude of 270.... well past the old 180 mark. So I scrolled left one, 'earth' on the map (recreated your dataset on my dev machine) and remarked the bounding box. Then pushed and all worked fine. The fix will be to turn of wrapping in leaflet.

The second issue is the amount of information you get back from a failed push. This is a problem that has not had enough attention. Right now, if there is just a single catch for all errors and the failed email is sent. This should be improved, but will take time... like everything else.

[aidanmazur]

Ok that makes sense. When I was drawing the bounding box, I first zoomed out a lot on accident and then zoomed back in, must have zoomed in on the wrong earth! I Made the second dataset using a template from the first, so problem carried over. I will continue testing now.

Is there anything specific you want me to do to address these at this point? I will continue general testing

[jrmerz]

Just general testing is fine. You already discovered one new bug :)