Hey all,
I'm starting this thread as a place for people to be able to ask for features for the upcoming/planned DojoX Geo project, which is where all of the mapping and geocoding functionality in the Dojo Toolkit will probably go.
This project will be the home of what was the GoogleMap and YahooMap widgets.
What I'm looking for is:
1. A list of features people would love to have.
2. Possibly a list of people who would be willing to work on the project with me.
Have at it :)
I can pitch in.
I can pitch in.
Thanks!
That'd be great. Now if we can just figure out what we would want out of it...
I was planning on writing
I was planning on writing some gMap stuff.... I could possibly pitch in on the google side of it... One thing I'd like to see... route sorting for multiple way points...
start with A B C D and find that the shortest (or quickest - I would want both options) way is through A C B D (or sort the entire thing to find the shortest possible route is B D A C -- this one is less likely to happen.... but if its an easy thing... it would be awesome :))
-Karl
I'm up for helping
I would love to help out with some code on this project. I have several in house map projects that I have already created by wrapping the google maps API in custom dojo widgets. They are not complete enough for anybody else's use but I would be glad to contribute. Most of the features I have are basic, but I would love to add more functions to them over time.
Cool.
It will be a little bit before the project kicks off, but in the meantime if you could file a CLA with us (http://dojotoolkit.org/cla), that would be great.
CLA filed via email.
CLA filed via email.
Great, thanks!
...when some of us come up for air, and start kicking around ideas, I'll be posting in this thread to begin with. Keep your eyes peeled, should be within the next month or so (charting comes first for me, then this and Crypto).
This is what I'm working on... :)
thanks to all the help from the great people building Dojo.
I am currently working on a complete mapping API built on Dojo. (http://events.esri.com/uc/QandA/index.cfm?ConferenceID=51AD3E9D-D566-ED8... -> #8). We will be presenting our work at AjaxWorld (http://www.ajaxworld.com/general/sessiondetail0907.htm?id=62) later this year. The Dojo user base will definitely increase once this API of ours ships.
You work for ESRI?
Really...we'd love part of this concept to be a baseline API for writing real GIS applications. Feel free to throw up *any* suggestions at all as to what you'd want out of this, and we'll definitely talk.
I would like to pitch in
I would like to pitch in too.
Have you started working on something?
Not yet.
But if you have any thoughts or specific requests, post them here.
Yes I do work for ESRI
And actually we are just getting ready to go into beta for our new JavaScript API (http://blogs.esri.com/Dev/blogs/arcgisserver/archive/2008/02/06/ArcGIS-J...). Its fully built on dojo and MAN has it been a good decision. Dojo ROCKS!
Multiple Map Providers
What I'd really like to see is a way to switch between mapping services on the fly. That way if the imagery from one provider is not detailed enough a programmer could provide a simple control to change to another service.
From a practical standpoint...
...that will be hard to do. Most of the AJAX-based services rely on using document.write to load up code, and doing that after the fact with a doc may prove difficult.
On top of that, most of the services force a large payload down the pipe, so I'd be a bit leery of trying to load Google Maps, Yahoo Maps and say Mapquest all on the same page.
Suggestions on how to overcome that would be welcome.
Take a look at OpenLayers
to see how they do exactly this
http://www.openlayers.org/
Yes, I've seen it.
...but they don't address the issue of forcing large applications down the pipe. One of the things I'd prefer to avoid is to force someone to load the base Google, Yahoo and MapQuest APIs just for the ability (probably not used by the end user) to switch map services.
Apparently Google (the main offender in terms of using doc.write) has released a script tag based version of loading a map, which is awesome (though it's still subject to the whole directory-based API key lockdown); it would seem that as we move forward, the providers are actually listening and providing good solutions :)
script tag based gmaps?
Tom: do you mean the Google AJAX APIs/google.load() stuff? Or something else entirely?
It would be good (and somewhat realistic) for Google et al to release a 'minimal' JS script which handles the very core stuff (tiles, copyrights, auth). Openlayers and others could then utilise this low-level API rather than repeating masses of code and interfacing via the high-level APIs which aren't designed for it.
Rob :)
Yes, the Google APIs.
...the Map API (what you use to include GMaps) used to use document.write to get all of the required code loaded; Dylan recently pointed me at an example where it is loaded on the fly using the script append method (though I don't remember the link off the top of my head).
what about this
What about what the mapstraction api is trying to do?
http://mapstraction.com
This is one of the aims of the project, yes.
...it's the direction I was heading when I'd written the original two GoogleMap and YahooMap widgets (back with 0.4.x), and would be considered one of the main aims of the project. But I'd like to hear other suggestions/needs as well.
possible participation
I am developing an application based on Dojo/Dijit and OpenLayers to visualize numerical data (e.g. sales) on the map. Pictures, simple geometric object and pie charts are used for numerical data visualization. An area loaded from any supported vector format can be colored in a particular way to visualize a number connected with the area.
The application can be run both online and offline. In the case of offline scenario map tiles generated from VMAP set can be used.
Some remarks from my expirience. Openlayers does work with multiple map providers. Unlike Google Maps it is possible to use Openlayers in offline applications. So my suggestion would be to create a Dijit wrapper for Openlayers. I found Openlayers's popup feature to primitive. Connection of Openlayers and Dijit popup is another direction of work.
I will follow the discussion here and might also contribute to development.
OpenLayers popups
The upcoming OL 2.6 release will feature improved (Google-style) popups.
http://trac.openlayers.org/ticket/926
I modified the OL popup class (it's not too difficult).
See the result here:
http://hosted.slippymap.com/wafflehouse/#1