| 00:23:02 | strk: | does anyone have arguments in favor of GeoJSON vs. GML for passing features around ? |
| 00:23:41 | wildintellect: | passing between computers or people |
| 00:24:58 | darkblue_B: | ohh everything is hard in GML, everything just works in GeoJSON |
| 00:25:05 | darkblue_B: | other than that, no ;P |
| 00:26:42 | strk: | wildintellect: between computers |
| 00:26:49 | wildintellect: | GeoJson |
| 00:27:20 | strk: | for the same 'just works' argument ? |
| 00:27:30 | wildintellect: | XML parsing is a royal pain |
| 00:27:41 | strk: | OL does it well it seems |
| 00:27:54 | wildintellect: | yes either works fine with OL |
| 00:28:04 | wildintellect: | however what's the other computer OL is talking to |
| 00:28:14 | strk: | I'm not considering doing it myself. Just had the idea that GeoJSON was smaller, but tests proved me wrong |
| 00:28:38 | wildintellect: | They seem like they'd be similar in size |
| 00:28:40 | strk: | the server side would be mapserver for GML and mapfish for JSON |
| 00:28:50 | strk: | I actually found geojson bigger :! |
| 00:28:51 | strk: | slighly |
| 00:29:02 | strk: | with even less attributes |
| 00:29:04 | wildintellect: | but which is faster to parse |
| 00:29:14 | strk: | how many times would you be parsing ? |
| 00:29:30 | strk: | and what's faster to generate... |
| 00:29:42 | strk: | broad range of variables to consider : ) |
| 00:30:16 | wildintellect: | is this a one way |
| 00:30:24 | wildintellect: | or a two way exchange? |
| 00:30:28 | strk: | good question |
| 00:30:51 | wildintellect: | see if it was 2 way ajax, gml wouldn't even be on the table |
| 00:31:11 | strk: | I might need editing too. |
| 00:31:22 | strk: | haven't experimented with that yet |
| 00:31:40 | strk: | does WFS support editing ? or is that WFS-T ? |
| 00:31:49 | wildintellect: | WFS-T |
| 00:32:04 | wildintellect: | and if you're looking for good support of that I believe that's Geoservers game |
| 00:32:27 | strk: | oh, so mapserver won't be able to do that ? |
| 00:32:49 | darkblue_B: | are you starting from scratch? whats the time to implement.. i dont think WFS-T has been done well by very many |
| 00:33:13 | wildintellect: | I always see mapserver being one way ( might be wrong ) |
| 00:33:14 | darkblue_B: | .. proof of a hard bunch of problems, I guess |
| 00:33:15 | strk: | starting from scratch, no plan yet so its more like a research task for now |
| 00:33:28 | wildintellect: | personally I'm monkeying with mapfish and geodjango |
| 00:33:48 | strk: | I started with a mapserver then played with symfony and now added mapfish to it |
| 00:34:08 | strk: | and was considering "is it worth integrating mapserver in symfony too?" |
| 00:34:12 | wildintellect: | ya I only use mapserver to serve static data |
| 00:34:32 | wildintellect: | probably not |
| 00:34:54 | strk: | unless it's just to get all things closer togheter ( all behind the symfony entrypoint ) |
| 00:35:08 | strk: | but yeah, would make map serving slower |
| 00:35:51 | strk: | the only reason was for WFS to avoid cross-domain issues ( with symfony responding to the root url ) |
| 00:36:01 | wildintellect: | well, whats the goal, if you want people to upload data and turn it into a wms via the web then yes integration |
| 00:36:32 | wildintellect: | but if you just need mapserver to server up some maps to an OL widget in your CMS not integration required |
| 00:37:22 | strk: | I'll want people to upload data ... dunno yet what kind : ) |
| 00:37:30 | strk: | but will surely affect the map |
| 00:37:48 | strk: | what I figured so far is that mapfish is targetted at this situation |
| 00:38:03 | strk: | like featureserver and probably geoserver |
| 00:38:25 | wildintellect: | ah my plan is to take uploads and stick it into postgis |
| 00:39:15 | wildintellect: | so base maps come from mapserver/geoserver - dynamic data is postgis/geojson directly to OL |
| 01:34:00 | strk: | wildintellect: no mapfish for you ? |
| 01:37:28 | wildintellect: | well I haven't decided between mapfish or geodjango but in both cases I plan to use postgis |
| 12:45:55 | sigq: | osgeofeed: Ticket #251 ( defect closed ): Log problems on osgeo.org <http://trac.osgeo.org/osgeo/ticket/251#comment:5> |
| 12:58:45 | sigq: | osgeofeed: Ticket #505 ( task created ): Request for new mailing list: osgeo-women <http://trac.osgeo.org/osgeo/ticket/505> |
| 13:58:46 | sigq: | osgeofeed: Ticket #505 ( task closed ): Request for new mailing list: osgeo-women <http://trac.osgeo.org/osgeo/ticket/505#comment:1> |