On 15/11/2012 09:42, Paul Norman wrote:
Deploying the P2 instance is what I'll have problems with - are there any
guides on how to deploy P2 with a custom vectors.xml (or imagery.xml) with
minimal pain?
http://wiki.openstreetmap.org/wiki/Potlatch_2/Deploying_Potlatch_2
http://wiki.openstreetmap.org/wiki/Potlatch_2_merging_tool
but, that said, the random.dev.osm.org is (I think) no longer current so
you're probably better off pulling down the resources directory from
github, and potlatch2.swf from OSM.
That would be good, but is one URL enough information or do you also need
the crossdomain.xml file location? I suppose you could take multiple fields.
Flash Player automatically looks at the root level of the domain for
crossdomain.xml - it's not something that P2 specifies.
Another issue that impacts on this is the lack of support for polygon
bounds. There is a huge overlap between the Canada and lower-48 states US
bboxes.
I'm not against adding polygon bounds support, but would need someone to
point me to some pseudocode for the implementation (geometry always
makes my head hurt), and a nice test case.
cheers
Richard
_______________________________________________
Potlatch-dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/potlatch-dev
