Map Size too large

Hi @tantares,

Thanks for reaching out and I am sorry to hear you are having issues.

It seems that you are still hitting an upload limit on your server end, so you will need to figure this out for your environment.

If you still believe this to be an issue with a recent Waymark update could you downgrade to confirm and provide extra details.

Apologies I can’t be of further help at this time.

Joe

Hi @joe,

As the same error message (“Request Entity Too Large The requested resource does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.”) appears, when I try to export and DOWNLOAD the GPX data from the Waymark map and I’ve increased all max limit parameters, wouldn’t it be possible, that the message is somewhere else?

Hi @tantares,

error message […] when I try to export and DOWNLOAD

I see how that is confusing! However at the moment the Export feature does indeed need to pass the Map data from the client to the server in order to facilitate the download.

There have been other feature requests surrounding Exporting and linking to Map data via URL, so I do plan on improving this at some point… ideally removing the need for this extra request all together.

Request Entity Too Large The requested resource does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.

This error message is coming from your server and is pretty clear, so ensuring limits have been set correctly is a good first step. This often requires environment/server configuration, requiring administration privileges and sometimes more than one value needs to be changed.

Using something like phpinfo can be helpful to ensure your changes are taking affect.

I hope this helps and please do let me know how you get on.

Cheers,

Joe

Hi Joe,

Tried everything without success including contacting the web-server provider. the PHP parameters post_max_size and upload_max_filesize were increased from 64M to 256M.

Any further idea, where the limit might come from or if the message might be misleading?

Cheers

Tantares

Hi @tantares,

I am sorry to hear you are still having issues with this. Honestly I can not think of anything else to resolve this at the moment.

I plan on doing a complete overhaul of the Export feature in the future because I know it needs improvement, however it may take some time before this gets to the top of my list.

In the mean time, the only suggestion I can make is try enabling the Advanced > Editor Options > Store Read Files feature. This should store Imported files on the WordPress media library, which you could then link to in order to provide a download option. This does not seem to work for everyone however and it only supports the original file format Imported.

I plan on updating here once I get the time to work on improving the Export feature. I appreciate the patience!

Cheers,

Joe

Hello @joe

Thank you for your reply. I’ve tested the upload of the latest GPX file via the media library as suggested by you. The upload itself works as expected and shows on the map but as soon as I want to publish the new map the same error occurs. Hence I believe, that the error is not caused by the upload itself but later during the publishing process. As this error has only started after many previous successful updates, I assume that the total size of the accumulated map must be the problem. Is there any method of removing some of the previous GPX uploads to test that?

Cheers

Tantares

Hi @tantares,

Sorry to hear this. Could you provide a link to the original GPX file you are uploading and ideally a link to the Map Details page for a Map with this Track imported (… if possible).

Cheers,

Joe

Hi @joe,

Sorry, I was away. Can I upload or send the GPX file (1MB) to you, because it is on a private computer and the site with the map is a private site not available to public.

Tantares

Hi @joe,

After some more testing I’m pretty sure, that the error occurs, when the aggregated map exceeds some limit in size. So the problem is not the upload but the posting of the complete map. Would you know, where such limits are defined and whether there is a way of checking the overall map data size. It would be helpful to know that and if possible to remove some data.

Happy New Year!

Tantares

Hi @tantares,

Happy New Year also! It’s a little hard to comment further without seeing the files in question, or a link to your site showing the issue.

• Are you uploading one or multiple GPX files (~1Mb) per Map?
• Are you grouping Maps together using Collections?
• When Exporting (on the front-end), are you attempting to download a single Map, or a Collection of Maps?

Waymark converts any uploaded Overlays into GeoJSON and stores all Overlays for that Map in a single GeoJSON Feature Collection. This Feature Collection is stored as text in the WordPress post meta database table and is associated to that Map.

At the moment Waymark does not track the total amount of data you have uploaded. Aside from looking at the original file size, If you are comfortable exploring your database then you may be able to dig around and discover more… but this is probably too much work.

I hope this was of some help to you.

Joe

Hi @joe,

Thank you for the additional information. I have 15 tracks, which form one trip. I uploaded them individually into one single map, not using collections, since they all are adjacent. Initially I used directly the exported GPX files from the Viking application, which turned out to cause the error after loading the last track.
Then I simplified the GPX tracks using GPSBabel, which reduced their size to less 500kB. This allowed me to publish the map. But for the download it’s still to large and causes the above mentioned error.
My next test now was to do the same on my local computer acting as server. I was able to reproduce the errors in trying to publish and download the large data, but instead of an error message, the page was changed to https://mylaptop.local/?waymark_http=1 without further action or messages.
Maybe this helps to isolate the error. Please let me know, if I can do something else.

Thanks a lot

Tantares

Hi @tantares,

Thank you for the extra detail. I have spent some time on this and also experience issues when Exporting large Maps.

instead of an error message, the page was changed to https://mylaptop.local/?waymark_http=1 without further action or messages.

It is worth ensuring that PHP error reporting is set correctly and WP_DEBUG is enabled. Also check the post_max_size on localhost, I just ran into this myself.

Then I simplified the GPX tracks using GPSBabel, which reduced their size to less 500kB.

Good idea. Could you simplify any further?

In all honesty the Export feature was a bit of a nightmare to get working and round-tripping to the server to facilitate the download was a necessary work-around that I am surprised works as well as it does! :0)

So I am hesitant to go too much further into this. Hitting these kinds of server limits is an absolute nightmare to diagnose/fix so I think time is best spent on overhauling the Export feature in the future to be a client-only implementation. However it might be some time before I have the time to dedicate to this.

I will have a poke-around the code and have a think if there any tweaks I can make, or if I can think of a work-around. You are happy with how Waymark is working aside from this Export issue?

Thanks again for your efforts!

Joe

Hey Joe,
Thanks for your support and for the moment I can live without the export. By reducing my tracks to the minimum possible I can provide the intended information to the readers and I’m very happy with the functionality of Waymark not least because I remain independent from Google. This year I will try to use collections for my tracks in order to have more flexibility of modifying them individually.

Thanks

Tantares

Hi Tantares,

Thanks for the update.

I’m very happy with the functionality of Waymark not least because I remain independent from Google

Nice to hear!

Cheers,

Joe