matt on 24 May, 2019 01:52 AM
Lets' break this down into the two separate but possibly related issues.
1) Pulling additional data into your maps. When I look at FKE2 in the database, it looks like all those objects were added in one pass on 12/8/17. It also looks like the map itself was created in 2017. How often have you accessed that map / do you have a sense of when this happened? I know you're not a rookie user, so sorry for asking, but are you absolutely sure that you didn't accidentally import that data in 2017, and are now confusing it with another similar map like 23BH?
2) On the browser CPU usage, does this happen for every saved map, including small ones like AR1F? Does it also happen when viewing the page in an incognito window (which would take any saved cookie settings out of the picture)?
Things are looking far better today. I'm not sure if something changed on your end or mine. I had several maps yesterday that were taking a long time to load, were not showing all of the mark-ups, and were opening in the center of the United States. Today they look fine ON MY COMPUTER. For example, this map of the bypass route of the (very) dangerous PCT/JMT crossing of the S Fork of the Kings River which I've been posting annually ever since Rika Morita's death there in 2017. https://caltopo.com/m/LL0B
Looked crazy yesterday. Looks great today on my computer. Still opens to the center of the US on my iPhone, but that could just be an outdated version issue on my software on my iPhone.
Re the FKE2 map. I may have indeed imported that data although I thought it was to a different map. That looks like the "Half Mile" PCT data from Lon Cooper. Not sure why I would add the whole 9 yards from Mex to Canada for a trip to Cedar Spring, but perhaps I did.
In any event, it looks like CalTopo doesn't have a problem although something was up with respect to point #1 yesterday. It either self resolved or maybe something was funny on my computer yesterday. I did a full shut down last night which might have cleared something.
It looks like I unnecessarily "cried wolf" and took up your time for which I apologize.
matt on 24 May, 2019 11:28 PM
No problem. Nothing's changed on my end - no new code deployments and the server hasn't been taxed CPU-wise - but all maps are initially loaded centered on the US, and then once the map's data is parsed, re-centering to fit that data. So if something is bogging down, it doesn't surprise me that a saved map would center on the US - if it's not properly loading.