This of course messes things up and prevents you from saving or updating. Not awesome. The field is output in the display_tablenav() function in the base list_table class. It looks like there has been a fix submitted, lets hope it gets into an upcoming version.

Until then, you can simply override the display_tablenav() function with a blank function or one that provides similar functionality.

http://server/v2/layer_name.json

Now look for the template variable and add it into the TileJSON you define in your javascript file. Mine is:

template: ‘{{#__location__}}{{/__location__}}{{#__teaser__}}{{{name}}} </br>\n{{{address}}}{{/__teaser__}}{{#__full__}}{{{permit_id}}}{{/__full__}}’,

However after fixing my URLs, it still wasn’t working. Turns out I also needed to switch the mapping scheme from TMS to XYZ in the tilejson. Definitely not a seamless upgrade and I didn’t really see this change documented anywhere. I am still trying to figure out what I need to change to make interactivity work.

http://support.mapbox.com/discussions/tilestream/59-tiles-not-displaying-on-map

In your tilejson object, try changing the scheme to xyz instead of tms and let me know if that fixes the problem.

Very annoying!

https://github.com/visionmedia/express/issues/711

GitHub to the rescue:https://github.com/astro/node-xmpp/issues/33

1. I  just wanted a selected number of fields (name, address, longitude, latitude) so I used mongoexport to put it into a JSON Array:
   ./mongoexport -d cookography -c places -f name,address,longitude,latitude -o test.json –jsonArray
2. Both CouchDB & MongoDB use _ID and MongoExport insists on adding it. However it does it in a way the CouchDB hates so I munge it:
   sed ‘s/_id/id/g’ test.json > tested.json
3. Now you have to format your JSON Array so you can feed it the the REST interface of CouchDB. First add this to the beginning:
   (echo ‘{“docs”:’; cat tested.json) > output.json
   And then this to the end:
   echo “}” >> output.json
4. Now send this to REST API for CouchDB:DB=”http://127.0.0.1:5984/places”

   curl -d @output.json -X POST $DB/_bulk_docs  -H “Content-Type: application/json”

Well then, take this sample HTML:

<li>
<div class="inspection">
<div class="date"><a href="/report/1430/9115/">9-16-2010</a></div>
<div class="inspection-type">License Renewal </div>
<div class="violations">0 Violations</div>
</div>
</li>

And apply this CSS:

.inspection {

overflow: hidden;

vertical-align: middle;

display: inline-block;

}

li {

margin-left: 15px;

list-style-type: disc;

list-style-position: inside;

}

On the off chance I can save someone time, I will recap what I did… and some of the misstep.

My big misstep was trying to use the precompiled binaries from KyngChaos. While they work fine, the OSM importer for PostGIS always SegFaulted when I tried running it against these versions. I even tried compiling the importer from source code and couldn’t get it work.

Here is what to do:

1. Use Homebrew. It makes it easy to download and compile source code. You may need to get rid of old cruft you have previously downloaded. I had to remove MacPython and some old Frameworks. If you run “brew doctor” it will give you hints.
2. Install Homebrew
3. Install PostGres, PostGIS and all dependancies: ‘brew install postgis’
4. Initialize the database. This will create a Database structure and a database user (“role”) that is the same as user Mac user name: ‘initdb /usr/local/var/postgres/’
5. Create a database for GIS stuff (Instead of Luke, use your OSX username): ‘createdb -U Luke -E utf8 gis’
6. Start the PostGres server – for some reason I needed to specify that it is running on localhost: ‘postgres -D /usr/local/var/postgres/ -h localhost’
7. Add the PostGIS stuff to the DB: ‘psql -d gis -U Luke -f /usr/local/share/postgis/postgis.sql’ and also ‘psql -d gis -U Luke -f /usr/local/share/postgis/spatial_ref_sys.sql’
8. Awesome! Now you should have a PostGIS DB loaded up. Now time to install the importer: ‘brew install osm2pgsql’
9. It is going to fail. This is because you need to apply a patch to fix some inconsistency. Big pain in the ass. To do that, download the patch from here: http://trac.openstreetmap.org/raw-attachment/ticket/3299/patch-build_geometry.cpp
10. To apply the patch, use the patch command: ‘cd ~/Library/Caches/Homebrew/osm2pgsql–svn/’ and then ‘patch -p0 < ~/Downloads/patch-build_geometry.cpp’
11. Now try it again and it should work: ’brew install osm2pgsql’
12. Awesome, almost there. Next step is to download some OSM data. Cloudmade makes it pretty easy. I grabbed the DC data from here: http://downloads.cloudmade.com/americas/northern_america/united_states/district_of_columbia#downloads_breadcrumbs
13. Goto where ever you downloaded your files to and run (replacing it with your OSM file): ‘osm2pgsql -U Luke -H localhost -d gis  district_of_columbia.osm’
14. TADA! All that wonderful data should be loaded into your PostGIS DB. Now open up QGIS and add in a PostGIS layer. Make sure you use your OSX Username as the username (Luke) and the PostGIS DB you just created (DB).

From the google groups:

I’m basically doing this:

var jsdom = require(‘jsdom’);
var document = jsdom.jsdom(‘<html><body>’);
var window = document.createWindow();

var JQUERY_URL = ‘http://localhost/js/jquery-1.4.4.min.js’;

function foo(text) {
document.innerHTML = ‘<html><body>’ + text;
jsdom.jQueryify(window, JQUERY_URL, function() {
var $ = window.$;
console.log(document.innerHTML);
});

setInterval(function() {
foo(“Text”);

And the process’ memory increases and eventually terminates. How do
you suggest I should reuse the DOM?

I am trying this for now:

function foo(text) {
document.innerHTML = ‘<html><body>’ + text;
if (!window.$) {
jsdom.jQueryify(window, JQUERY_URL, function() {
var $ = window.$;
console.log(document.innerHTML);
});
} else {
var $ = window.$;
console.log(document.innerHTML);
}

}

Figuring out how to do this was a little tricky. Luckily it is very easy to do:

<body>
  <div></div>
  <div></div>
  <div></div>

  <div></div>
  <div></div>
  <div></div>
<script>

    $(“body”).find(“div”).eq(2).addClass(“blue”);
</script>

Simply use .eq(index) to access a particular element in the jQuery object.