[OSM-dev] API/XAPI caching proxy server

Ian Dees ian.dees at gmail.com
Mon Dec 20 01:11:49 GMT 2010


On Thu, Dec 16, 2010 at 3:17 PM, Ian Dees <ian.dees at gmail.com> wrote:

> On Thu, Dec 16, 2010 at 3:10 PM, Peter Körner <osm-lists at mazdermind.de>wrote:
>
>>
>>
>> Am 16.12.2010 22:05, schrieb Stefan Keller:
>>
>>> Rewriting xapi on the other hand is an excellent idea.
>>>>
>>>
>>> Yes, good idea.
>>>
>>> I would probably start with osm2pgsql and setup a mirror (incuding
>>> hstore). Since osm2pgsql uses the PostGIS database I think it
>>> should'nt be too hard to turn predicates to WHERE clauses and bbox to
>>> a ST_Within query in PostGIS.
>>>
>>
>> The osm2pgsql scheme does not store meta information (version, creator,
>> timestamp), which are required to create valid .osm files.
>>
>> The osmosis simple schema would be a better start. It also supports hstore
>> and an geometry column but stores full meta information.
>>
>>
> I'm working on this exact setup as we speak. I wrote an XAPI querystring
> parser in ANTLR (https://github.com/iandees/xapi-antlr) and plan on
> writing the rest of the server piece tonight while I wait for a planet to
> import into an EC2 instance. I'd be happy to have help -- if you're
> interested let me know before I pick a language to use in the next 6 hours
> or so.
>

For those of you interested, I decided to use Java (so I could use Osmosis's
classes to do the heavy-lifting) and started a bare-bones project here:
https://github.com/iandees/xapi-servlet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20101219/be6d6d2d/attachment.html>


More information about the dev mailing list