Rob Atkinson ha scritto:
evil man!
Actually, you've pretty much described the extension to app-schema Ben
and I have discussed, and I was going to have a play with once I'd
gort a coupel of other jobs out of the way...Our idea was to create an "inverse mapping" using substitution
parameters - which is pretty much what you have discussed, with the
ability to allow a user defined one, or a well-known one such as
geometryless.This will also solve another ugly problem - querying against
manufactured string values - for example a internal database ID being
append to a data-set-specific URN to create a globally unique
identifier. At the moment this is inefficiently queried.Our goal, as you have suggested yourself is to remove sql-datastore
and geometryless as separate modules, and app-schema already has the
capabilties to do the forward-transform.
Ok, so that is "plan a)", having a wrapping datastore that
can do two way translations.
Should we ditch "plan b" (custom {bbox} templating) and wait for
your datastore to be able to do the same, and more?
What is your timeline?
It's not like I am in a hurry, I just see a "plan b" as
long hanging fruit that would address a problem we're asked about
humm... once a month lately? (mapping x/y to a geometry, assuming
you have a spatial database that can build a point out of them)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.