hi Chris,
> Not entirely true. There was an API, a way of interacting with it, and a
> catalog,
> before we started putting any real amount of data in. The problem was, nobody
> cared, because the only size of data that people care about for aerial imagery
> is 'everything!' (Thank you, Google.)
Yes, sorry for misrepresenting. I guess I meant an API for dealing with the
imagery import itself.
If I recall, that was a major headache, require a lot of manual work.
If there was an API for interacting with the catalog, etc, then that seems like
a perfect place to start
.. start by disengaging that piece from the imagery processing piece.
> Tiles are one way of thinking about it, but I think that everything else
> you say actually doesn't speak to 'tiles', but instead to 'data OpenLayers
> can read'. If a service can provide a WMS layer, why do you need tiles? You
> just need something that OpenLayers can read; preferably with no user
> knowledge
> other than 'I want that one!'
>
> Tiles are fine for developers, but for users, they don't care about tiles.
> They just want a map. (This is just my experience/opinion, anyway.)
Right, same here. I'm only thinking about developers here .. users shouldn't
need to know.
I think it's going to be easier going to look just at Tiles, both on the server
and client sides,
but if WMS can be accomodated as well, well I guess let's see.
> I think this is less important than a lot of people seem to think.
> ("Governance
> first" seems to sink many well intentioned projects...)
Governance is an overblown word here, sure. Schuyler's point was that we just
need to empower someone to get shit done.
> But I could hardly expect to have any other opinion based on my approach to
> projects in general :)
Glad your opinion is here!
Mikel_______________________________________________
talk mailing list
[email protected]
http://openaerialmap.org/mailman/listinfo/talk_openaerialmap.org
