markersDB per map

[LeadMagnet]

(Feature Request)
Currently all POI data is stored in a single markersDB.js file at the root of the site.

I am building a user console to add/edit/remove markers from this file, powered by ASP.Net and MSSQL with the data translated using Newtonsoft.JSON libraries.

It would be much easier to deal with if each map had it's own markerDB.js file or similar.

OR, even better, the ability to store this info in a database from the start.

[CounterPillow]

This sort of touches three different things we want to rewrite.

1. genPOI, see genPOI rewrite discussion #1090
2. the web output, see Alternatives to Google Maps? #494
3. the way different worlds, dimensions and rotations are treated, see Rotate maps with ease #1100

OR, even better, the ability to store this info in a database from the start.

A full database is overblown for what markers are for. Overviewer generates static maps, and unless you write a JS client for your favourite database and open it up for everyone to read, you'd have to go for a server-side script to return markers. This breaks many setups which do not wish to be powered by ASP.Net and MSSQL or whatever else one might choose.

What I want to do is come up with a new structure of storing the markers to make them more easily cachable and allow for partial fetching of marker data.

Either way, it all points towards a more well-defined interface to supply marker data, which means that people can write their custom dynamic marker stores if they so choose.

[LeadMagnet]

Sounds like a plan!

I know google maps support KML and now FusionTables for data storage. A native option is always better. I just happen to know how to build external control systems, hence the direction I'm going.