@chris-little's feedback from CesiumGS/3d-tiles#405:

Can tilesets be nested hierarchically? I'm not sure from the text.
Can a tile can be "in" more than one tileset? I'm not sure how, but presumbly URIs allow this.

The answers are "yes" and "yes" but they could be clarified in the reference card.

The Crime Mapping sample (https://github.com/Esri/arcgis-python-api/blob/master/samples/04_gis_analysts_data_scientists/crime_mapping_visualization_and_analysis.ipynb) shows some nice data cleanup and wrangling functionality. The sample data that it points to cleans up to a CSV file with 886605 rows.

The next section involves creating a spatial data frame. (Note: It uses the syntax "from arcgi

Revamp/reorganize Manual towards 3.x and procedures

• Delete Index Provider Content

• List Procedures (manual)

• Output from tests

• Copy over uDig content from http://oss.infoscience.co.jp/neo4j/wiki.neo4j.org/content/Neo4j_Spatial_in_uDig.html

• Deprioritize uDig and GeoServer

• GeoServer Version number -> Support Case

Instead focus on examples for

It would be important to have a single intro Vignette for both Python and R, or at least a Vignette that is very similar in both languages. This is the current intro Vignette in R. I

Essentially this vignette is a single overview of stack and crop_image.
It's missing a clean description of stack and how stack works with the parameter options.
It's also missing crop_all.

We should decide whether to have 2 vignettes - or just organize this one to show all three functions:

• crop_image
• crop_all
• stack

https://earthpy.readthedocs.io/en/latest/gallery_vign

As a general rule, we should avoid print in final user-facing code.

It's normally used in 3 ways I think:

1. Indicate the current interpretation of inputs or current status a function. This is normally better served with (i) a warning if something is provided that is not as expected (more explicit, highlighted in the console/notebook, can be filtered when running in batch, contains inform

It is unclear if data should be added and what is going on with the NEON site mentioned. Remove the excessive details and be explicit about the fact that there is no data being entered.

Currently the marker is drawn first with additional geometries as layer being drawn on top of the marker.

This isn't great.

See https://docs.ropensci.org/USAboundaries/ and this comment from Hadley: ropensci/rotemplate#19 (comment)

You can also have a look where other packages store readme.md figures:

• https://github.com/ropensci/tidyhydat/
• https://github.com/ropensci/drake/

https://github.com/mstrimas/smoothr

Apply this to arcs and recompose for topological-aware smoothing

Additional information should be:

1. Managed by: < name of organisation >
2. Logo: PNG or SVG
3. Contact person: name + email
4. Custom Terms of Use that complement the ones from MapX