This content has been marked as final. Show 6 replies
what's the problem? you generally would decide how much of your map you want to display on-stage at one time. you would then scale the data to fit your stage.
the hardest part is often deciding how much data you should display on-stage at one time because you don't want to overcrowd the display and you want to include as much as you can. but that's not a coding problem.
The lat and long numbers I gave are only example, theere will be more than one set of numbers and they will load dynamically via xml...
and again, what's the problem?
Sorry I hadn't gotten back to your post in the other thread, but I am kind of with kglad in this. I guess I didn't quite understand what you were asking. Do you not know how to read the lat and long from the XML?
As I had suggested, I advocate for storing the locations in decimal form.
You would then pull out the node. The values are bound to not be numbers, so you should use parseInt() to change them to numbers.
Of course, depending upon the projection of your map, you may find that there isn't a direct 1 to 1 kind of relationship. Mapping round surfaces onto a flat map/screen can be quite complex. For far more than you wanted to know:
But for most purposes here, there are probably ways of faking it. Just try it out and then maybe fudge it a little bit to make it look right?
I am gonna just try to start coding a script and see how it goes, maybe once I get a little more done I can post it, and then it will make more sense.
Thanks for all the input though.