Document a views geojson use case

Thanks for your interest, dasjo!

My original use for this was on site where I use OL for maps on the front-end, but needed to get all of the locative data out into something to make maps for print, (which ended up being Tilemill.) That's still my primary use of the module, but my hope is that it can become a/the primary data delivery mechanism for the OpenLayers module. I'd expect it could serve Leaflet, Modest Maps, Polymaps similarly, and the Mapping module yet to-be.

Yes, Geofield is my preferred option for storage, but Location and basic Lat/Lon work just as well. There's WKT support, too, though I've only tested it through Geofield.

I'd be glad for your help here in whatever direction you see fit. Yes, #1370448: Provide GeoJSON Layers from Views (integrating with views_geojson) is definitely high priority, and working out the kinks of #1333324: Bounding Box filtering (for OL in particular.) I'd be very interested whether this module works well with Leaflet, too, as I haven't yet tried that route.

Glad to hear your further ideas. Thanks!

Hey @dasjo, now that #1370448: Provide GeoJSON Layers from Views (integrating with views_geojson) and #1333324: Bounding Box filtering are in, what do you think about this? Your help in documenting use cases would be greatly appreciated. :)

Where would these go? On the project page, in the README, in d.o. docs?

BTW, I opened up a new issue for #1516906: Leaflet integration.

Maybe we should work on getting Views GeoJSON into OpenLayers Locator?

One thing that could be better documented, (and fairly easily,) is why use this module.

Part of the purpose (the why) is to get rid of the clunky OpenLayers Data Overlay paradigm. We could also document how to re-make OpenLayers Data Overlay views as Views GeoJSON views... or better yet, create a utility, (a sub-module, probably,) to convert them.

Use case of Druplicon blog activity
Documentation page: http://drupal.org/node/1637324
This issue is closed.

Thanks @idevit and @batigolix! And thanks again @dasjo for organizing the sprint.

This is a great start. I've added a link to the use case from the project page, (under Usage,) and made a few revisions.

The ending could use some more attention. I'm going to leave this issue open in case we can get some more eyes on this, and until we can get it into a fairly complete and polished form.

Thanks a lot for you work!

I am using the GeoJSON module to limit the number of points on the map using Bounding Box, and it just works, which I think is just Fantastic. Thank you very much!

The documentation is getting better, I think adding step number 6 to the README.txt would help along a little as well. Point 1 to 5 is already included:

USAGE
-----

1. Create a View with a Page display on content with geospatial data.
2. Add fields to output a Geofield, longitude & latitude or WKT.
3. Optionally add fields for name and description.
4. Set Format for the display to "GeoJSON Feed".
5. In the "Style options" for this format:
  * Choose Map Data Source (Other: Lat/Lon Point, Geofield, etc.)
  * Assign the fields that represent Latitude and Longitude.
  * Optionally choose fields representing name and description for each point.
  * Optionally set a JSONP prefix, (see http://en.wikipedia.org/wiki/JSONP).
  * Set the Content-type header to be sent. The default is "application/json",
    the standard MIME type for JSON, per http://www.ietf.org/rfc/rfc4627.txt.
  * Optionally enable "Views API mode". By default the plugins stop Drupal from
    doing any additional processing when a view is rendered, allowing the
    content to be output without normal page markup. If you are calling a view
    programatically, enable "Views API mode" to avoid early termination of
    Drupal execution.
6. If used with for example the Openlayers module, activate your new layer under 'Structure' -> 'Openlayers' -> 'Layers & Styles'

@ressa: good idea.

I committed this addition:

6. If using with the OpenLayers module, your new GeoJSON layer will be available as an Overlay layer on the "Layers & Styles" tab when editing your map.

Thanks!