Closed garnertb closed 10 years ago
Tyler happy to discuss. Broken in mainline too.
Note for danpalumbo when testing: When this is fixed, we need to test all of the types of imports that GeoNode supports
After talking this over with Ian and Jeff it seems like the best approach is updating the GeoNode side.
Notes: If we should still support Geoserver 2.3 then I could use these url routes to detect the importer version.
I've ported over the importer work from Mapstory to my GeoNode fork (https://github.com/garnertb/geonode/tree/importer_fix) until we can get everything tested. Below are the results of my tests.
GIS Data tests:
Other Tests:
For ROGUE, I think we can press ahead with GeoServer 2.4 without worrying about supporting GeoServer 2.3 as well.
Tyler,
Scott asked me to coordinate with you about doing some testing on this fix. I have a few questions, so it may be better to just wait until you are in the office. When will you be there next?
Thx, Dan
Dan Palumbo Systems Engineer LMN Solutions
On Wed, Mar 5, 2014 at 10:47 AM, Tyler Garner notifications@github.comwrote:
I've ported over the importer work from Mapstory to my GeoNode fork ( https://github.com/garnertb/geonode/tree/importer_fix) until we can get everything tested. Below are the results of my tests.
GIS Data tests:
- san_andres_y_providencia_administrative
- san_andres_y_providencia_coastline
- san_andres_y_providencia_highway
- san_andres_y_providencia_location -> Failed from Importer gui import as well
- san_andres_y_providencia_natural
- san_andres_y_providencia_poi
- san_andres_y_providencia_water
- single_point
- relief_san_andres.tif
- test_grid.tif
Other Tests:
- KML import
- Import with metadata
- Import with an SLD
Reply to this email directly or view it on GitHubhttps://github.com/ROGUE-JCTD/rogue_geonode/issues/40#issuecomment-36755906 .
This is fixed in ROGUE, closing.
Per https://github.com/GeoNode/geonode/issues/1312, the Geoserver importer no longer works with Geoserver 2.4.