Restructure data I/O chapter? about geocompr HOT 10 CLOSED

Heads-up @eblondel, I've just updated the section, as per the commit above.

Note that the intro now says this:

If you want to put your data 'into production' in web services (or if you want be sure that your data adheres to established standards), geographic metadata is important, as described in Section @ref(geographic-metadata).

Sound good to you? geo metadata is a mysterious world to me so grateful for your input!

from geocompr.

Currently we have:

https://r.geocompx.org/read-write

I wonder if the web services and metadata bits deserve their own chapter, as they're not core to everyday geocomputation tasks.

from geocompr.

Agree re file formats and reading and writing data going earlier in the chapter.

from geocompr.

1. I think that moving File formats before Geographic web services is a good idea.
2. Another option would be to do 8.5 File formats, 8.6 Data input (I), 8.7 Data output (O), 8.8 Geographic metadata, and then the rest.

I think I like option 1 more, but I am open for discussion.

(Note: If the order is changed -- then the introduction should be updated as well)

from geocompr.

Looking at this now..

from geocompr.

Updated structure:

from geocompr.

Thanks @Robinlovelace one comment: Geographic web services should come after Geographic metadata.. Indeed some services deal with the handling of metadata, that is then better to introduce before...

from geocompr.

Great comment and perfect timing as looking to tweak things right now.

from geocompr.

The updated structure looks fine by me.

from geocompr.

👍🏻

from geocompr.