This page needs more details.

Examples of cool map stuff we'd want to be able to do

here is an advanced wiki map type function: to see how districts evolved over time - how they changed shape. for instance, you could add a new point to the timeline of a page about a district and then draw a map region of what the district looked like then -- and then you could view the evolution on the timeline

yeah couple of ways to implement it, depends on usage

but could serve for discussing future alternatives, i.e. set of pages of possible boundaries, possible locations for something, etct-- that have maps not as static images but embedded and versioned data this domes map should be totally possible in our new mapping system.

Filter Locations

It would be awesome to be able to be able to filter by article type or tag on the map page. So if I am in a specific area on a map I choose to only see parks, or businesses, or history, or some tag.

Address lookup (geocoding and reverse-geocoding)

Summary: It is critical for LocalWiki to improve map-based interactions by allowing users to find locations based on addresses and intersections. Additionally, since geodata in LocalWiki is functionally accessible through the primary interface, and now the LocalWiki API, the opportunity to integrate and successfully utilize address data may be valuable improvements to the data model. A simple consideration:

  • It may make sense to add "address" simply as a page-based semantic field as a component of the "infobox" model in development. A proper geomanager must be used.

However, there is a major use case for address lookup: allowing users editing maps to drop points based on addresses and intersections. There are several steps to implementing

  1. Utilize an open (or publicly available without throttling) geocoding service. Combine with an ajax human-reviewed search to refine multiple responses to a single correct result (e.g. 200 Main St, Oakland, CA --> 200 E. Main St and 200 W. Main St?? ==> 200 W. Main St, Oakland, CA).
    • What services are available? Which are open? Which work?
    • Consider Open Street Map's API service: Nominatim unfortunately, this does not support intersection searches
  2. Import some geospatial data for a local neighorhood (specifically blocks, address numbers and intersections) for quick, localized, roughly complete geolocation.
    • Could constitute a primary option in the future, and use 1. above as a "fall back" for geolocations and reverse geolocations out of range.
  3. Build or partner with a full-service geocoder.


" ... One thing I didn't see immediately was a way to change the color of the overall map or the individual polygons. On my original map I used different colors to make the different neighborhoods easier to see, but an additional use would be to differentiate the different types of neighborhood classification, whether unofficial like Oaksterdam, historical like Jingletown, or 'official' like Rockridge. For that matter, it would be nice to be able to group the different types in folders or something so that they could be turned off and on as layers." - Gene from re: