This is very good news my friend :)
I already posted something on the mail list about this. However a
stackoverflowish system will
benefit much more in the long run, for a dev mail list.
It will be like following, since i really do not require places like
laundries (actually only cafe's and
bar's) i will take them from your database, sync them everyday (look
for changes etc.) and in the
opposite site, will also sync unmatched places from my database back
to yours and link them
on my site with the hyperpublic_place_id so i know if they matched
correctly and stuff.
What i want to ask you is, and probably more developers will ask is,
what is the proper database
layout for keeping such data?
For example, will a location have multiple addresses, locations and
pictures? ( for example my places,
have at least 3 pictures each )
What to do then?
I dont want to keep you busy all the time, this are my final questions
my friend, so if you would
provide a example db layout, that would be very very professional.
I also noticed some errors maybe in the documentation
http://developer.hyperpublic.com/places/find-places/
if you look at the example and the table, the /places and /things url
tags have a mismatch.