>Hello, I am trying to figure out the best way to import RPF data. I have RPF >data with A.TOC (10+GB for one A.TOC) that I can put into GeoServer, but as >I have read A.TOC is not the best way to do this as the A.TOC is slow for >WMS. So I have learned I can point directly to the *.I22 Data file from the >RPF Data folder using NIFT to import the map tile. Problem is I have 3,500 >*.I22 files that the A.TOC references. doing all those, creating a >Datastore for each would be very time consuming. > >So What is the best way to import all this data? Convert all the data to >another Raster Format to make it quicker? > >is there a Bulk import into GeoServer for the NIFT format?
I'm not super-familiar with what you're up to, but if you put in a few dozen of the .i22-files "by hand," do they have decent performance for your purposes? If so, (and you're happy just importing these things as separate datastores) I would use Geoserver's administrative REST API to get them all in without having to sit through the GUI-steps every time. Otherwise, merging them together as you said might be the answer, especially if these data are going to be pretty static. Whether you'll get a performance hit/boost from doing that probably depends on your usecase. - Patrick O'Toole Application Developer Wyoming Natural Diversity Database UW Berry Biodiversity Conservation Center Department 3381, 1000 E. University Av. Laramie, WY 82071 P: 307-766-3018 ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
