My presentation from the June New Jersey Geospatial Forum meeting on the NJDOT PArk & Ride viewer built that has become a template for other State agencies to stand up mapping applications quickly using a business table with no geometry as the source.
10. Useful Avoid This Area Aim Here Ugly Pretty Avoid This Area Avoid This Area Useless
11. Useful Avoid This Area Aim Here Ugly Pretty Avoid This Area Avoid This Area Useless
Editor's Notes
What is it?It is a table managed in SQL Server by NJDOT.It has X/Y coordinates and the characteristics of the Park & Ride facility, but no geometry.DOT provide a read-only user for us to access the view to bring it into ArcMap.
Get it in the MapThis is pretty straight-forward.Create a connection to the databaseAdd the table and create an event theme in ArcMap…nothing fancy
Get it on the webThis is where it gets cool.By placing the MXD and the SQL Server connection file in a directory the ArcGIS Server SOM user can access, we can publish it as a map service.There were a couple of things we learned along the way, you can not create a Map Service Definition file, so when putting the map document together, be aware of what layers you put in the map service You are connecting to SQL server for your dataset, you will need to open the SQL Server port, not the SDE port The ArcMap database connection file is portable, make sure you bring it along with your MXD when escalating it up the stack
The whole goal of this application was to create a small embeddable widget that can be used in a DOT managed page.Some of the other requirements were: had to work in IE7, so no HTML5, CSS3 data to be managed by the data steward in its native environment w/ no additional data management steps by either DOT or OGIS take advantage of our eGIS existing stack
The whole goal of this application was to create a small embeddable widget that can be used in a DOT managed page.Some of the other requirements were: had to work in IE7, so no HTML5, CSS3 data to be managed by the data steward in its native environment w/ no additional data management steps by either DOT or OGIS take advantage of our eGIS existing stack
One of the bonuses was we now have a framework that can be used by other agencies to embed into their applications.The framework includes the ability to: configure the application from a single JavaScript file including: map services id layers output fields visible page components layer visibility and base map control
populate dropdowns from layers in the map service to zoom to a location
The final mark we look at an application with is to see where it falls within matrix. I’d say we did alright with this one…